I had Tchap in mind.
tor.defcon.org is considered a guard node, and your browser likely chose to prefer that one to bootstrap itself.
For more details https://browser.mt/
The firmware is indeed closed-source, so it’s hard to audit. But they’re popular, and a security flaw wouldn’t go unnoticed for long.
There are other vendors such as NitroKey offers an alternative that offers both open source and audited hardware and software.
https://www.traccar.org/ could be a good starting point.
And some TOTP apps don’t interpret the algorithm
parameter correctly, which makes it safer to go with the default SHA-1.
Lemmy in fact was using SHA-256 for its earlier TOTP implementation and reverted back to SHA-1 since some people locked themselves out due to poor support in some TOTP app (among other issues, another was that the activation workflow never asked you to confirm the code you enrolled was working and generating the correct code…).
A strong and unique passphrase is indeed really important here, but you need to keep in mind that once the kdbx file is in the attacker’s hand, that’s the only thing that keep them out.
There’s no 2FA, and no throttling on the bruteforce process. So it’s really important to use a strong password there to avoid it being the weakest link.
One trick is that you can enroll your TOTP codes on more than one device, the only thing the device need is the clock to be synced to provide the correct code.
You can store your TOTP codes in many places:
That way you don’t get caught your pants down if one of your device dies, get stolen, etc. Also, keep the recovery keys / backup keys in a safe place just in case of a worst case scenario.
Keep in mind that your TOTP backup and Password Manager files like KeePassXC can be the weakest link in your OPsec if you’re not careful.
Initially the software wasn’t very stable, but that was fixed over time. Overall I liked it a lot, and the available “apps” for it all filled a niche I looked for.
I switched because I wanted to go back to a more classic watch I can simply wear and forget about. I don’t have all the bells and whistles from the BangleJS2, but now I have a watch to see my notifications and step counter that I don’t need to recharge every week, the battery (CR2032) is said to last about 2 years in the GBD-200.
I would suggest to look at the models supported by Gadgetbridge and pick one from there. I know I can trust Gadgetbridge not to leak my data since it doesn’t ask for network permission.
https://gadgetbridge.org/gadgets/
I used it for several years, through multiple gadgets (in chronological order)
That’s the point of digitally signing the app, to ensure its authenticity and integrity. TM and others wouldn’t be able to resign the modified app with the Signal Foundation signature.
EDIT: Yeah after thinking more about it it’s not a trivial problem, as you need to assume that the endpoint is inherently untrusted.