searchable
| web | https://n2vi.com/ |
| web | https://n2vi.com/ |
Yes, "anonymity" was a poor word choice. What I meant was there are domestic abuse scenarios in which avoiding a monthly payment trail helps in staying low profile, and I'm glad to subsidize that. But Signal does not protect perfectly against metadata analysis by law enforcement. Building such a system is challenging, not least because of unintended consequences.
I don't agree with all Signal's choices, but I think we do all agree that (as far as we know) they're not egregiously wasting their donations and that among the widely available communication channels, they're relatively good.
The Signal Foundation at signal.org/donate also makes it easy to contribute from Donor Advised Funds.
By keeping the service free of charge, those of us who don't need to hide enable anonymity for the vulnerable.
Google Security has a great Leaving Tradition, which I commend to other orgs aspiring to excellence: https://bughunters.google.com/blog/6355265783201792/the-great-google-password-heist-15-years-of-hacking-passwords-to-test-our-security-and-build-team-culture
(I don't post often, and am not sure whether mastodon or @n2vi.bsky.social is best for it. But their nice blog post deserves the extra pointer.)
The Leaving Tradition in Google's security team, which could be described as a type of small-scale offensive security exercise, is a great (and fun) example of team culture. Curious? See this blog post for details.
@mat @matthew_d_green If you keep one on your person with house and car keys, and one in your safe deposit box, then loss is a very rare event. And you don't need security-key-2FA for every website, only the ones of substantial value like email bank github.
I grant that "keep on person" is harder for some people than others. For example, my pants have pockets, but a woman I know carries hers on a necklace.
Just describing the one auth I've seen that stops cold state actors' phishing. Everyone can make their own risk/reward choices.
@matthew_d_green The best Yubikey backup strategy is for the auth server to allow registering multiple security keys. This has been the canonical solution since the dawn of time, i.e. when security keys existed only inside Google and Yubico.
Also, the auth server needs to allow revoking individual security keys in case of loss, so be sure to give them names at time of registration.