895 karma · joined October 10, 2021
This is changing, and picking the right manufacturer can make all the difference.
In all seriousness though, everything you pointed out is literally inconsequential to the question asked. It would 100% be more secure, requiring a state issued id card to reset your password. Plenty of people lose all forms of identification at some point in their lives, and while it sucks and take a bit of time, it's not an insurmountable obstacle, and will eventually be resolved.
Why are you acting like you don't understand? You seem like a smart person.
Why don't you leave the thinking for the ones better at it.
Also, reading the privacy policy, it looks lacking. I'm not a lawyer, but https://www.nolo.com/legal-encyclopedia/what-to-include-in-y... clearly states that if your service sends text messages, you should make a statement about retaining that data indefinitely.
After reviewing the privacy policy, and seeing who else is involved in the company, no thanks. Seems very non professional.
Theres plenty of resources out there around this idea.
When you enable encryption, they derive an encryption key off the passcode you provide, encrypt the tokens, then store them on authy's cloud storage. The encrypption key is never sent to authy's servers, and only stored on device. When you add a new device, you're prompted to enter the passcode, which generates an encryption key and decrypts the tokens.
How is support going to decrypt the tokens for you? They need the password, which they don't have.
You use support to add a device to your account, and then you use the password to decrypt your tokens.
Granted, an attacker could gain access to your authy account and then delete all your tokens, but that's different from being able to log in and start using your TOTP 2fa codes. You should also have recovery codes written down somewhere in the case this happens for all your services.
I literally just restarted everything from my previous post with more words.
https://support.authy.com/hc/en-us/articles/360036077534-Wha...
>If you lose your Backup Password, you will not be able to decrypt your 2FA tokens from Twilio Authy servers and access them within the Authy app on any other device (Eg: If you bought a new phone to replace an old or lost device). If you still have access to the original device on which you set up the Authy app with your 2FA account tokens for the first time, you can follow these steps to re-configure your Authy app on a new device.
Authy admins cannot reset this password. It looks like they can disable encrypted backups, but not decrypt your shit.
So basically all an attacker should be able to do is gain control of your account, delete your old 2fa codes and then add his own.
That being said, docker blows. Docker desktop blows more. Docker desktop on Windows blows the most. I always get stuck with a bind mount misbehaving, or some other issue that requires me to wipe the docker desktop data to fix it. Just use docker compose for simple stuff, and stay away from docker for Windows if possible.
Better headline: 'Breaking news: CNN cutting back on over-hyping everything as “breaking news”'
Not saying I agree, but thats my interpretation.
It sounds like you are the 'rockstar' on your team honestly.