Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The killer feature for me is a way to quickly access tokens in my (cloud-side, encrypted) vault from a desktop (or web) app in case of emergency.

It's not clear to me if Aegis allows this somehow?

The other day I broke my phone. I was traveling and needed to do some 2FA level changes to a GH repo asap.

I didn't even know there was an Authy desktop app until then. It saved my ass, literally.



Aegis has two automatic encrypted backup options.

The first lets you back up your data to any folder on your device or to any storage provider (e.g. Nextcloud and other cloud storage providers) linked to your device. Turn this on at Settings > Backups > Automatically back up the vault. The storage provider's app needs to be installed. Changes are saved to the backup location automatically.

The second uses the OS's built-in backup feature. For Android devices with Google Play Services, the backup is saved on Google Drive. Some other Android distributions such as LineageOS use Seedvault, which can save the backup to any WebDAV provider or an external USB drive. This option is at Settings > Backups > Participate in Android's backup system.

Either or both options can be used in Aegis.


Yubikeys store everything on the key. I can lose my phone and use your phone to see my 2FA codes. It's honestly one of the only way MFA make sense - otherwise you lock yourself out of your entire digital life when you lose your phone and need to rely on storing your backup codes (which opens up a storage security wormhole).

It's also a lot easier to wear around your neck.


So you've moved the worry from losing/breaking your phone to losing/breaking your YubiKey?


I keep a second key as backup for this reason, which honestly is overkill and I only do because I got a second one for free at a conference. Easier solution (which I also use in case I someday need the second one only to discover that the blue smoke leaked out) is to just print out the TOTP secrets and keep them somewhere. I'm usually printing out recovery codes when I get a new TOTP secret so this has never felt like a big deal.

Also easy enough to maintain a keepass[xc] vault for totp secrets, you could keep a separate one from your passwords if you were feeling paranoid. Great support on mobile and desktop for using a keepass db as a TOTP source - and easy to sync with dropbox/email/ssh/your web server/whatever


Everyone should read this risk mitigation solution for loosing 2FA. I always think about printing recovery codes, but having keepass vault with those codes also sounds great. You may even have some random password there and store it printed out in some locations just for emergency.

Anyways, people should think about these risks when dealing with 2FA: flood, fire, stolen, lost, (I) broke (Smartphone, yubikey, usb, etc), broke (itself), software bug, kids, washing machines, etc.


And also something we usually don’t consider: loss of memory, which can occur in combination with a traumatic event like your house burning. Then you can loose your smartphone, your Yubikey, your printed copy, and your memory all at the same time if everything is stored in one place. And this is exactly when you will need those the most. Not easy to defend against such a nightmarish scenario.


Sure. I have a backup key but yes, you can't get MFA without adding a device that you may lose; whether that's your phone or a key. Like I said I prefer a key because I can't put my phone on a chain around my neck or on my keychain.


who says you only have one or no other backup?

anyway I wouldn't but s Yubikey for TOTP. OTP sucks. Sure it's better than no 2FA and TOTP is better than SMS OTP still it's not grate.

WebAuthn-like auth can provide all the benefits of TOTP while being way more secure and in some cases even not convenient.

The main drawback is how to backup your 2FA which makes it less of a choice for a "casual" user.


The only downside is limited space on Yubikey.

I am currently carrying 2 tokens :(


Up to 32, for those reading who (like me) didn’t know about this limitation.

https://support.yubico.com/hc/en-us/articles/4404456942738-F...


Good luck finding 32 places that accept Yubikey.


They don't have to accept Yubikey, they have to accept TOTP. Which ~everything does.


except eBay


Or Google, very user hostile because it makes me choose between giving them my phone number or installing their spyware app on my phone.


Google's authenticator is just a standard TOTP app. You can use any app, including Aegis.


Google hides TOTP option until you create a method that uses your mobile number or google app. Only after that you can change it to TOTP.


I use Yubikey USB to authenticate with Google.


My Yubikey always loses its credentials. (If anyone else knows about it and have a fix I'm all ears.)

I guess I need a new one, but what I want to say is don't rely on a single Yubikey or even two. Do have backups.


Which model do you own and how does the loss manifest?

The single-tap and long-tap don't produce expected output? Can you share more info on it?

I own many Yubikeys (due to research I've been doing in 2017.) and I had many Yubikeys to play with, for TOTP/HOTP/U2F purposes, even using it to unlock Windows and I haven't had a case of a Yubikey basically deprogram itself. I washed them in the washing machine, ran them over with my car, thew them in mud piles and they always worked without a fault so your case is a surprising one.

Judging by what you wrote, unless there's some weird NFC communication going on between your phone and Yubikey (are they in proximity?), I'd say it's faulty and you need a new one.


Classic USB. Plastic. (I don't know the exact model, I got it from work.)

After adding a site or a computer it works a few days and then suddenly when I try to use it with my phone or computer I just get an error about no <something>.

So yes, probably defective.


Not enough info to even guess what might be wrong, but I'd assume it's defective and I'd try with another key as well. I wish you good luck with the next Yubkey you get! :)

Btw. this is the first time I've read on a public forum that someones Yubikey is defective, they are really well made and I didn't manage to break one via regular use and bad maintenance.


"I didn't even know there was an Authy desktop app until then. It saved my ass, literally."

That's a really unexpected outcome - can you provide any details ?


> [...] can you provide any details ?

I installed Authy desktop, logged in and it retrieved my tokens form the cloud. Not anything else to it.


Pretty sure they're referring to the word 'literally'. Especially since it's by itself after a comma, looks like there's emphasis on it.

That word changes the meaning of the phrase in front of it quite a bit.


I am literally never going to stop misusing this word.



Aegis is fully offline and doesn't have an official desktop application. You could of course create an export of your Aegis vault and import it in a third-party desktop application, like GNOME's Authenticator or OTPClient.


This is what I do. Two "live" authenticators with my phone and laptop and a secure offsite backup.

I don't add new keys particularily often, so it isn't that big of a hassle two manually sync the authenticators.


What app do you use on the laptop?


I can’t believe this is a tech forum. The answer is simple. 2FA has a url. All you have to do is store the url in your password manager. Then you can import it into any new app at a moment’s notice (as long as you have access to the vault) and generate a 2fa code.

In fact, KeePassium on iOS works on this concept. I use it as my primary otp url storage app and then put limited stuff into aegis on my android tablet for anything I may need there. If a keepass based app with an otp generator (like KeePassium) existed for android, I wouldn’t even need that.


AEGIS has this killer feature, with the encrypted database, which I could sync to my local Nextcloud instance. Otherwise, loosing the phone would always mean loosing all your OTPs. Aegis is a direct (better) replacement for Google Authenticator.


Don't know if it exists for Android, but for iPhone users there is OTP Auth, which can make encrypted backups to a destination of your choice.


Bitwarden can store and then copy/paste TOTPs. I'm not sure if it's the best security practice to have your password and TOTP key saved together like that. But I tend to use it for sites that I don't consider critical. I then use Google Authenticator for everything else. I might try Aegis next time I get a new phone though.


There's a python script to decrypt the vault which you can use from a desktop with a little bit of code.

https://github.com/beemdevelopment/Aegis/blob/master/docs/de...


The answer you're looking for is Aegis vault backup + Syncthing or Nextcloud. Seriously.

I once lost my Authy app data and didn't have it installed on any other of my devices (silly requirement tbh). I don't know whether cloud or 2FA is the joke here but Authy slapped me with a 24hr wait time for a "device reset".



You can export the vault (encrypted or not) to a cloud provider (like Google Drive). It's a manual process, but it's simple and quick. Besides, how often do you add new 2FA tokens anyway?


You can export it to file whenever you add a new key. Then, use SyncThing to sync the copy to a remote location.

The exported file can be encrypted when you make it.


Yeah, that's a UX problem.

I need to do that every time and remember.

From my experience, you loose access when the last backup you made and synced was made before the key you need now was added.

I.e. this doesn't work in practice.


If you enable automatic backups in the Aegis settings it will create a backup after every change. If you set the output directory to a location synced by Syncthing, there's nothing to remember.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: