If your phone has biometrics, you can set that up, much quicker than typing password each time.
Ohhhh snap you're right! Thankfully my phone has a fingerprint reader. Never used it but it looks like I finally have an excuse to!
Guess I just need to stop being lazy now. 😅
You can use biometrics instead of a password. Also, Google Authenticator not having a password requirement is a massive security risk to me. A 2FA app, just like a password manager should ABSOLUTELY be protected with passwords/biometrics.
I got biometrics turned out, ty!
You can disable encryption and use Aegis without a password, just like Google authenticator.
I didn't realize that. I should do a better job at reading all the settings. Ty!
I use a self-hosted bitwarden, it keeps both my passwords and generates TOTP authentication codes
This is the only way, saving tons of credentials centralised isn't the way to go, if you're able to do it yourself and mantain it.
Not everybody should selfhost
instructions unclear, everyone should be @selfhosted
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !selfhosted@lemmy.world
I'v been trying to self host bitwarden but I keep running into error after error. Mostly with nginx 😑
I use bitwarden_rs with docker-compose, behind nginx. I can share my config if anyone is interested.
I self host on my Synology and getting the reverse proxy with the webhook setup properly was such a PITA it took me giving up for a couple months and coming back to it to finally get set up. Turns out I was looking in the wrong place for security certs the whole time 🤦
Seems badtio keep both forms of auth in the same place.
Btw OP, you can export from Google Auth. and it will give you a big QR code that you can just snap with Aegis, in case you didn't know already.
No need to transfer one-by-one.
You just need to get the code off your phone first.
Doesn’t that defeat the whole purpose though? I would regenerate each OTP “string”, for lack of a better way to say it, rather than bringing them over as Google already has that data.
Err.. how do I get it off my phone tho?
A marker and steady hands.
🤣
Err… how do I get it off my phone tho?
There are several ways! First, take a screenshot (power + vol. ~~up~~ down is the shortcut for me, not sure if this is an Android default).
Then email it to yourself, or plug in your phone with UTP to a computer and move it out of the picture folder, or print from your phone to a wifi-enabled printer, or use something like Google Keep and sync it to your computer, etc.
Not sure if you're joking but thankfully you can't take a screenshot of Google Auth.
And emailing it would completely defeat the purpose of 2FA
Oh goodness, why didn't I think of emailing it to myself. 🤣 Thank you for the tip, I'll do that in the morning after I wake up.
The mental image of me looking at a qr code on my phone screen, and only then wondering how I would catch that on the phone's camera did make me laugh.
😂
What I did was take a screenshot and then scan the photo via Aegis
Everyone has already mentioned the biometrics, but I think even without that you still should have to suck it up if you want to improve your security.
Also, I think it's worth the hassle of changing to Aegis since you can make backups of your vault pretty easily, something which Google authenticator doesn't provide.
The only option in that app is cloud sync which IIRC isn't encrypted in any way, so your keys are being sent to you-don't-no-where via you-don't-know-how in plain text.
Aegis gives you the option to sync your vault with an encrypted file which you can then import into other Aegis install (I don't know if it has the option to sync an unencrypted version).
Apparently you can use biometrics instead of a password each time you require access. Not sure if that still seems like a bother or not, I personally do not mind.
𝐄𝐝𝐢𝐭: Some one else already beat me to this answer, haha.
But I don't reccomend it. I may be too paranoid, but recover a fingerprint (physically, non from the OS) from a lost/stolen phone is pretty easy and this is why I never suggest to use fingerprints to login to banks app and authenticate transactions. At least use a 6 digit pin for Aegis.
I use a yubi key to do my static passwords for otp apps like this.
I think it's 38 characters long.
I wish ageis uses keys or webauth but that requires online functionality.
Ah yea just noticed that; my phone has a fingerprint reader. Didn't even occur to me to use it because I never have. 😂
I remember losing Google Authenticator data when I had to format my phone. This was years back and didn't have too many accounts setup. With Aegis I have an offline encrypted backup of all my 2FA codes so this is no longer a possibility. Before Aegis I was tempted to use Authy before I had to wait 24hrs to gain my access back after I reset my phone.
2FA on Android has always sucked (lazily created; app data CANNOT constitute and/or subsitute device trust). I wish I had got on to Aegis earlier.
I've already made my first backup with Aegis. =)
You can also check out 2FAS, which recently got open-sourced. It comes with browser plugins to autofill 2FA pushed from the phone on request. Makes it a lot more convenient if you need another reason to switch.
You can also check out 2FAS, which recently got open-sourced.
I happened to be comparing this and Aegis so I'll add the biggest differences I noticed. Maybe it helps someone:
Oh neat, ty ty!
I use aegis as the otp for bitwarden and keepassxc. Currently trying to migrate bitwarden and just use keepassxc while syncing the db to my nextcloud and backup onedrive.
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
Additional Resources: