Feed aggregator

Apple Might Use Google Servers To Store Data For Its Upgraded AI Siri

Slashdot.org - Mon, 03/02/2026 - 18:00
Apple has reportedly asked Google to look into "seting up servers" for a Gemini-powered upgrade to Siri that meets Apple's privacy standards. The Verge reports: Apple had already announced in January that Google's Gemini AI models would help power the upgraded version of Siri it delayed last year, but The Information's report indicates Apple might lean even more on Google so it can catch up in AI. The original partnership announcement said that "the next generation of Apple Foundation Models will be based on Google's Gemini models and cloud technology," and that the models would "help power future Apple Intelligence features," including "a more personalized Siri." While the announcement noted that Apple Intelligence would "continue to run on Apple devices and Private Cloud Compute," it didn't specify if the new Siri would run on Google's cloud. Apple's Private Cloud Compute is not only underpowered but it's also underutilized in its current state, notes 9to5Mac, "with the company only using about 10% of its capacity on average, leading to some already-manufactured Apple servers to be sitting dormant on warehouse shelves."

Read more of this story at Slashdot.

SSH Agent Forwarding – An Underutilized Essential Tool

BrandonChecketts.com - Mon, 03/02/2026 - 17:22
span.code { font-family:monospace; background-color: #F1F1F1; }

SSH Agent Forwarding is a magical feature of SSH that I see too many people don’t understand or know how it works.

Using an SSH Key for authentication is superior to a password for many reasons. But it gets more complicated when you SSH from one machine, and then want to SSH from that machine to another, including for something like cloning a GitHub repository. I very frequently have this situation where I SSH from my machine to a remote server, then want to perform a git pull on that remote machine.

If attempting to do this without agent forwarding, you would have to copy your private key to the remote machine. Then from that machine, you can authenticate to GitHub since your keys are in place there. That’s cumbersome and not a great idea to put your private key on a machine that could be exploited. You should always keep your private key private!

Agent Forwarding allows you to bypass putting your private key on the intermediate machine. It essentially opens a tunnel between the remote machine and your local machine, so that authentications requests can talk to an SSH agent running on your local machine to perform the cryptographic authentication.

You create an SSH key as you normally would using the ssh-keygen command. Your private key is stored in ~/.ssh/id_ed25519 by default. You then turn on your SSH Agent using the ssh-add command like:

ssh-add ~/.ssh/id_ed25519

That will prompt for your passphrase if you have one. If successful, the agent stays in memory and keeps your private key unencrypted in memory. You can run ssh-add -l command (-l for “list”) to see the keys that it has loaded:

14:15 $ ssh-add -l 256 SHA256:3W+i4HXlwABCdefgHIJKLMNPQRSTtRjynjRcmbgO2Jk brandon+2023@mymachine (ED25519) 256 SHA256:abcDEFghiJKLmnoPQRstuVWX/cPz2mYZZZe+xU78Ins brandon+2025@mymachine (ED25519)

Then when you want to connect to a remote machine and forward your SSH-Agent, you use the -A command-line argument

ssh brandon@remote-machine -A

You can confirm that this is working on the remote machine with ssh-add -l again. If working properly, it will list the same SSH keys as when you ran it locally. When working, you can there ssh to other machines or use SSH to authenticate to GitHub to check out packages. You can even forward from a remote machine to another machine beyond it, tunneling the agent through multiple intermediaries

One Warning

Don’t use agent forwarding to remote machines that you don’t control or that may be compromised. Someone who can log in as you, or root, on a remote machine could potentially use your forwarded agent to authenticate as you to other machines

The post SSH Agent Forwarding – An Underutilized Essential Tool appeared first on Brandon Checketts.

Categories: Web

HBO Max and Paramount+ To Merge Into One Streaming Service

Slashdot.org - Mon, 03/02/2026 - 17:00
Paramount Skydance plans to combine HBO Max and Paramount+ into a single streaming platform following its acquisition of Warner Bros. Discovery. "As we said, we do plan to put the two services together, which today gives us a little over 200 million direct-to-consumer subscribers," said David Ellison, the company's CEO. "We think that really positions us to compete with the leaders in the space." The deal still needs regulatory approval. The Washington Post reports: He added that Paramount didn't want to make changes to the HBO brand. "Our viewpoint is HBO should stay HBO," Ellison said, noting that his favorite HBO product is "Game of Thrones." If Justice Department regulators allow the deal to go through, it would place recent HBO Max hits, such as "The Pitt" and "A Knight of the Seven Kingdoms," alongside Paramount offerings including "South Park" and "Yellowstone." "They built a phenomenal brand," he said. "They are a leader in the space, and we just want them to continue doing more of it." The deal to buy Warner Bros., valued at about $110 billion, will almost surely attract regulatory scrutiny from the Justice Department because -- without divestments -- it places major swaths of the film, television and news industries under one roof: Warner Bros. and Paramount studios, HBO Max and Paramount+, and CBS and CNN would all have the same parent company. Ellison expressed confidence on the call that the deal wouldn't face hurdles with regulators.

Read more of this story at Slashdot.

Syndicate content
Comment