• 0 Posts
  • 603 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • A lot of what you list is built into the emulation cores and are not just UI features.

    For games that don’t use their emulation cores:

    • They would need to come up with a steam-like injected overlay approach
    • CRT shaders are probably a no go without engine injection (similar to reshade)
    • Bezels could maybe work with stacked borderless windows, but again it would be an entirely new approach compared to what they have now
    • Netplay would also need something new and Hamachi-like and would only work with games that already have LAN support, patching support for online service based multiplayer would likely need per-game implementations
    • The customisable interface would probably not need any changes at least

    Basically they would be building all the tough bits from scratch to do everything you’re suggesting










  • Well yes, the most secure way would be a single source of OTPs, however I’m happy to compromise that slightly for convenience. Having 3-4 devices with access to the OTP database isn’t a huge increase in my attack surface. An attacker would still need to steal one of my devices, rather than one specific device. Those devices would also naturally be protected by additional factors.

    I understand I would have to handle the syncing of the database for aegis, I was more curious if you knew of other clients that could use the same database format on other platforms.

    I’m very aware it’s a bad idea to keep your OTPs in the same database as your passwords (and in fact already make use of keepass). I would probably not even sync the databases using the same mechanism

    Bitwarden/vaultwarden does seem to be the front running option if there aren’t suitable clients for reading an Aegis database on other platforms, and I’ll just ignore the password manager aspects of it even if that means it’s a heavier solution than I’d have preferred.

    Thanks for bearing with me on this


  • Okay I see what you’re saying but it’s still a downgrade from what I thought my security was, the fact authy broke that trust doesn’t mean I want to compromise what I was expecting to the level they ended up providing me

    Sure, I guess the thing I’ve not made clear enough is that I accept the compromise of security by having an SMS backup in this scenario for the convenience it provides in restoration. Someone could compromise my SMS but they’d still need my password, and in Authy’s case, they would also then need to be able to sufficiently convince Twilio that I’m me before they allow access again. I understand that the last step is obviously not possible with a non-commercial solution.

    Tbh you’ve kinda come up with the solution for me though, if I keep the database in it’s own cloud storage separate from everything else I could set up SMS 2FA and a unique memorable password to get a similar experience to what I have now, albeit without the extra verification when SMS is used.

    Since you’ve been helpful already, one last question if you don’t mind: do you have good recommendations for iOS, Mac & Windows clients for aegis? The official repo seems to just be an android app, and I make use of authy across all 4 platforms currently