Hello! I’m in the process of slowly de-googling my life and taking my privacy more seriously.

I currently use Google Authenticator for 2fa at the moment.

I am currently dreading swapping those to Aegis, which requires a password every time I want to use it (that’s very inconvenient, to be honest) while with Google’s I can just open the app and get the necessary code right away; no password required.

Should I just stop being lazy, suck it up, and make the switch? I know I’m being a bit of a baby.

Edit: Okay, apparently I can use my fingerprint scanner instead, which is a LOT better, so I’ll stop being a lazy shit and do the swap tomorrow. Cheers!

Final Edit: I made the switch to Aegis. Already made a backup, and I have Biometrics setup. Ty everyone!

22 points

If your phone has biometrics, you can set that up, much quicker than typing password each time.

permalink
report
reply
3 points

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. 😅

permalink
report
parent
reply
16 points

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.

permalink
report
reply
2 points

I got biometrics turned out, ty!

permalink
report
parent
reply
12 points

You can disable encryption and use Aegis without a password, just like Google authenticator.

permalink
report
reply
1 point

I didn’t realize that. I should do a better job at reading all the settings. Ty!

permalink
report
parent
reply
10 points

I use a self-hosted bitwarden, it keeps both my passwords and generates TOTP authentication codes

permalink
report
reply
3 points
*

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

permalink
report
parent
reply
4 points

instructions unclear, everyone should be @selfhosted

permalink
report
parent
reply

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

permalink
report
parent
reply
2 points

I’v been trying to self host bitwarden but I keep running into error after error. Mostly with nginx 😑

permalink
report
parent
reply
3 points
*

I use bitwarden_rs with docker-compose, behind nginx. I can share my config if anyone is interested.

permalink
report
parent
reply
2 points

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 🤦

permalink
report
parent
reply
1 point

Seems badtio keep both forms of auth in the same place.

permalink
report
parent
reply
8 points
*

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.

permalink
report
reply
1 point

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.

permalink
report
parent
reply
1 point

Err… how do I get it off my phone tho?

permalink
report
parent
reply
18 points

A marker and steady hands.

permalink
report
parent
reply
2 points

🤣

permalink
report
parent
reply
5 points
*

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.

permalink
report
parent
reply
6 points

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

permalink
report
parent
reply
2 points

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.

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply
1 point

😂

permalink
report
parent
reply
1 point

What I did was take a screenshot and then scan the photo via Aegis

permalink
report
parent
reply

Privacy Guides

!privacyguides@lemmy.one

Create post

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:

Learn more…


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:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don’t ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don’t repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

Community stats

  • 845

    Monthly active users

  • 626

    Posts

  • 10K

    Comments