technical possibilities aside, do you presume your grandchildren will be technically apt?
I am pretty sure 99% of people would halt at 'gpg' , and that's now -- not 60 years from now.
I know reading the docs is considered uncool for some reason, but it really does work.
First result with simple command. I went from KeePassXC to `pass` & back to KeePassXC. But I question the integrity and/or motive of people like you.
The AI model will be of certified provenance and run on attested hardware [0] so this won't be as much of a security issue as you might expect. Naturally the various three letter agencies will have full hardware access including query history.
Periodically, hardware zero days will drop and all hell will break loose.
Alright that's enough speculative dystopian fiction for me for today.
Since ChatGPT? ~all of them except maybe my grandparents.
Don't take security advice from an AI.
In fact, if you consider the impact fully, the best way of managing passwords still seems to be writing them down on a post-it note and keeping it in your wallet - hell, even sticking it to your screen doesn't look so bad these days, compared to alternatives.
Modern infosecurity is absurdly counter-intuitive at high level. Consider that your Google account or your WhatsApp (or Signal) chats are much more secured than your medical data or bank accounts or anything that predates Google. For anything in the real world, there is always a recovery procedure, no matter how much bad luck you had or how badly you screwed up. In the worst case, you might end up needing to chase some documents to authorize or notarize other documents, or show up in court, but you can get your access back. It's insane to imagine the world, in which a single fuckup could wipe out your medical history, your bank account, or any proof of your existence in government systems - and yet, this is exactly what is the case with any modern SaaS that follows "best security practices".
There's literally nothing else in this world that's so easy to mishandle as security in commercial software services.
It's kinda ludicrous to think we'll lose the ability for something so simple.
Sorry, but I already have to google each time I want to figure out how to open various file formats.
"Google, what ffmpeg flags do I use to convert this .flv file to .mp4", "what are the flags to losetup or kpartx to mount 'disk.img' as a loopback device?", "how do I extract an '.ab' backup from 'adb backup'?"
These are all things I googled before llm.
LLM entities have bills to pay too.
Please do not mock gpg.
I have been using gpg for 25 years now (and PGP before that). It works. It encrypts. It decrypts.
It is in vogue to mock gpg on HN and recommend more modern solutions. As an experiment, I tried adding one of those modern tools (rage) to my ansible configurations, just so that they get regularly installed and maintained on my servers (without actually being used). The setup broke within less a year.
Are the modern tools more cryptographically secure? Undoubtedly. Does it matter in practice for me? Not at all.
Longevity is a big deal and is under-appreciated.
Filippo nailed it with this piece: https://words.filippo.io/giving-up-on-long-term-pgp/
My kids? I really am not so sure at all. Still too early to tell for sure but so far I don't think any will be as technically savvy as I am. I really doubt they'd know what GPG (or PGP) are and how to use it.
The apathy is real and I don't see it getting better.