Half of the IT team I am on is seemingly incapable of understanding using a public/private keypair for SSH logins.
Can I use yours? How to copy them? Should they be unique per user? Should I email the private key? Etc?
My favorite is when someone posts their private key to a Slack or Teams channel, then says "I'll just delete it after it is received..."
No. Just no. That key is forever unclean.
I seem to remember real bullies would do it to your face before the internet. Not just anyone behind a keyboard.
I have calibre set up to just email books to my Kindle, but that's an extra layer of indirection that I really don't need. I'll have to check that out.
> "It is a big enough OEM that there is good chance you may have owned a device from them in the past."
I think this takes Nothing out of contention.
I'd love for it to be Framework.
We do in the US. I was kind of surprised when my now 2 and 4 year olds were vaccinated against Chickenpox, since I remember doing the Chickenpox party thing myself when I was younger (staying home with some friends over, playing Daytona USA on my Sega Saturn, I think?).
It was like a badge of honor.
phew
> any engineering role where security matters that is -not- using PGP smartcards to sign and push their commits, sign code reviews, sign build reproductions of container images, encrypt their passwords, etc.
I agree. Even without smartcards, at the very least sign your commits, among other things. Absolute minimum. Very low bar.
They do not get their credentials until they do so. And once they do, our security posture gets better and better.