- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
As I updated the version to 1.4.0 , adding the ‘import’ feature I am sharing this here.
I made this extension because I couldn’t find one that wouldn’t ask for too much permissions (such as accessing all websites data).
Eventually I found it nice to have a TOTP that can really be audited, the code is 649 lines of JS, 214 CSS and 52 HTML. Feel free to fork, copy part of it, contribute or just request fix/features.
I have used it for more than a year every day and it works nicely.
Hell no, having OTP in the browser kinda defeats all 2FA and makes it 1FA again.
If the thread model involve physical device access, then yes. However, consider that the attacker might not have access to the device with this 2FA.
It’s enough if they have access to the browser.
You’re gonna need to access the device for that
It’s probably sufficient to be able to take over the browser remotely.
Can you elaborate on that? Any source?
RCE CVEs are a thing.
You don’t know what you’re talking about, do you?
Many/most password managers do TOTP in their browser extensions already - at least on paid tiers. (Bitwarden, Lastpass for sure).
It’s the only way a team can effectively use TOTP, which still offers a lot of protection.
Lol, “the only way a team can effectively use TOTP”, really? Many paid PWMs doing it already isn’t a good excuse.
If you have any concern I would gladly hear technical insight about the threat model involved. The cross-post on the Privacy communities sparked more conversation if you want to follow up on that point : https://lemmy.ml/post/12744864.
Extension “authenticator” has been around for more than a decade now. I am sharing something that is small, simple, auditable and secure (no permission to do anything but past on clipboard).
I don’t have much to add to the edited version of that comment in that topic there: https://lemmy.ml/comment/8930011