Looks like I'll have to turn off Facebook's encrypted messages. @protonmail appears to be wrapping the PGP-encrypted messages Facebook sends with another layer of PGP, causing this error.
Also fun: /pol/ has discovered a list of printers in New Zealand and some Arab countries that expose telnet on port 9100. You know, the same port used by @hackergiraffe
Those of you who had "political memefare" in the what-will-unsecured-printers-do-next pool, come collect your winnings!
So, this looks like one of the first steps towards "Encrypted Facebook"... You can add a PGP public key in your profile. After doing so, you can ask that Facebook encrypts all email sent to you ***including password reset emails***
Gave them the public key for the relevant ProtonMail address, and there was no extra work.
If they're going to build end-to-end encrypted services on top of PGP, this could be super interesting.
If you search for "docusign legally binding", the Assistant answer, the top three web results, and the top three video results are all *from* DocuSign.
The fourth web result is a story about a bankruptcy attorney that was sanctioned for exclusively using DocuSign, with no live signature on paper to go with it.
While it's refreshing to see many firms offering U2F keys, this *is* a security product, with inherent concerns to match.
When you race to the bottom with security products, you quickly run into slap-dash efforts, missing functionality, and even vulnerabilities like sharing random seeds, or using poor entropy sources.
Better than nothing, sure, but an end user's one bad first experience will turn them, and everyone they talk to about it, away from multifactor.
#5OclockCharlie Manages 10.57% CPU utilization, still thinks he can take out IRIS.
Skids will be skids.
Hacker, comedian, RED Scout fan, gold Ekko one-trick. Watching them sorting debris.
A Mastodon instance for info/cyber security-minded people.