@dalias Very fair! (though there are also security properties for not being able to read a backup, that's kinda a different animal.) Though I'd also argue that there's a fuzzy demarc of immutability for which "disconnected and in a drawer" buys additional insurance. YTMMV as always!
The CopyFail folks shouldn't have routed stderr to /dev/null in their workaround guidance. For some platforms, where it's not a module ... that mitigation is a no-op:
$ rmmod algif_aead rmmod: ERROR: Module algif_aead is builtin.
So if there's no kernel patch available yet, you can't use that workaround. Instead, use AppArmor / seccomp / SELinux to block unprivileged AF_ALG socket creation if you can (but don't just turn these hardening layers up if they''re not already in place - they can be tricky)
Not all unexpected additional project work is "scope creep". Sometimes it's"we now better understand how we have to meet original scope, and it's gonna take more effort".
@roytam1@nina_kali_nina@mirabilos I wonder if MyDefrag / JkDefrag would also work! Dramatically more features than the stock defrag, but is just a wrapper and uses stamdard system calls for the defragmentation of each file. Not affiliated, just a long-time favorite. (And I wonder whatever happened to its author, Jeroen Kessels?)
So if you initiate the phone-to-phone Signal account transfer process, and it almost completes, such that the account is transferred, but the data isn't, and then errors out ... and if you didn't have backups enabled ... then your entire chat history just vanishes into thin air with zero recourse. In other words, Signal nukes your history from orbit on the old phone before validating that it actually successfully transferred to the new phone.
I am indescribably angry right now.
(The extra insurance you need, that I didn't have, was to enable general backups on the old phone first, and make sure that a backup completes on the old phone before initiating the transfer.)
"Let us be the repository of your passkeys" and "We may terminate your account at any time and permanently refuse to communicate with you" ... seems like a bad combination?
Just doing my undue diligence.ISP vet (was AS7782, now AS8047), password cracker (Team Hashcat), security demi-boffin, YubiKey stan, public-interest technologist, AK license plate geek. Husband to a philosopher, father to a llama fanatic. Views his.Day job: Enterprise Security Architect for an Alaskan ISP.Obsessed with security keys:techsolvency.com/mfa/security-keysMy 2017 #BSidesLV talk "Password Cracking 201: Beyond the Basics":youtube.com/watch?v=-uiMQGICeQY&t=20260sFollowed = probably stole you from someone I respect.Blocked inadvertently? Ask!Am I following a dirtbag? Tell me!Suggestions welcome!Photo: White 50-ish man w/big forehead, short beard, & glasses, grinning by a display of Alaskan license plates.Boosts not about security ... usually are.Banner: 5 rows of security keys in a wall case.#NonAIContent#hashcat #Alaska #YubiKeys #LicensePlatesP.S. I hate advance-fee scammers w/heat of 400B suns❤️:⚛👨👩👧🛡🙊🌻🗽💻✏🎥🍦🌶???