A lot of people just want a browser that works. They don’t care at all about anything else in the OS. For them, Linux can be perfect. So if they’re disgruntled that Windows keeps shoving ads and AI bullshit in their eyeballs, when all they want to do is check their email and watch YouTube, a preinstalled Linux laptop is a great answer.
Oh come on! I could get through that in just over four days.
I like that one guy’s drug trip from 2000 years ago has caused this hilarious internet meme.
Basically, in public key cryptography, you can generate a set of two big numbers that are mathematically related, one called the private key and one called the public key, collectively called a key pair.
Through a lot of fancy math, you, with your private key, can take a number I give you and give me back another number called a signature. I, with your public key, can do even more fancy math to prove that you do, in fact, have the corresponding private key to the public key I have, based on this signature.
If you give me the wrong signature, I can’t trust that you have the private key, and you don’t get authenticated, but if you give me the right signature, I can trust that you’re you, and you get authenticated.
A number of things. The key is stored on and accessed by a separate coprocessor from the CPU, so the CPU doesn’t even know the private key. That takes its own protocol, over i2c, usb, Bluetooth, etc. Then the browser has to coordinate that protocol to communicate with the web protocol from the frontend JS. There’s also the concept of server verification, so it’s a more complicated handshake than just one signature going one way. Then, of course, there’s the inherent complexity of public key cryptography in general, but you only need to worry about that if you’re writing it from scratch with no library.
From a basic web dev perspective, it’s not much more complex than a password, but that’s because the complexity of the protocols is hidden behind the libraries. A password actually isn’t complex, even when you remove the libraries.
(The private key does not have to live in a separate coprocessor, but that’s the most secure method, and the one covered by the protocol.)
Here, these specs are what they’re based on:
Yes, kind of. You’re still giving them your password every time you log in. And it’s on them whether they store it hashed or in plain text. With a passkey, you know that even if they’re hacked, they’ll never get your actual private key.
But, if they’re hacked, your key is probably the least of your concerns.
A passkey is a key pair where you keep the private key and give the public one to the service. Then you can log in by proving you have the private key. Fairly simple in theory. Horribly complex in practice.
That’s cool. AI can do art and writing and video games for me. It can watch all my shows. All I have to do is work and maybe sleep. Sounds fun.
I don’t think a year old base is bad. Unless there’s an absolutely devastating CVE in something like the network stack or a particular shared library, any vulnerabilities in it will probably be just privilege escalations that wouldn’t have any effect unless you were allowing people shell access to the container. Obviously, the application itself can have a vulnerability, but that would be the case regardless of base image.
What’s even better is the source code. It’s just true, but false.
If you plug a power strip into each one of those empty plugs, you could power the whole house!
It seems like we could make this a lot more efficient by using pistons and having the sunlight push the pistons, turning a generator.
A superb image will have a health check endpoint set up in the dockerfile.
A good image will have a health check endpoint on either the service or another port that you can set up manually.
Most images will require you to manually devise some convoluted health check procedure using automated auth tokens.
All of my images fall into that latter category. You’re welcome.
(Ok, ok, I’m sorry. But you did just remind me that I need to code a health check endpoint and put it in the dockerfile.)
The bicycle has changed quite a bit in the last hundred years. The modern derailleur was introduced in the 1930s. Moving the shifters to the handles was more recent. Clipless pedals and disc brakes were both introduced in the 70s. Carbon fiber frames reduced their weight substantially.
Their basic shape hasn’t changed much, but everything else has.
It’s a pretty nice custom designed PC that is guaranteed to work well with Linux. The only downside, really, is that you can’t upgrade it beyond storage and RAM.
Next you’re gonna tell me he doesn’t even run blades.
Giving them the benefit of the doubt, I would think it’s to resist corrosion, but there are plenty of cheaper metals to plate with that don’t corrode, so even that’s a stretch.
Or, you know, plastic.