6 ms·

Firefox is using TripleDES??

• hulitu 2y ago
  > Firefox is using TripleDES?? What's wrong with it ? /s
  • penguin359 2y ago
    I would mostly say that it's just slow and AES is a much more modern and faster (partly due to hardware acceleration built into modern chips) that is already built info Firefox to support TLS anyways. There are some known attacks against 3DES now, but nothing that completely breaks it yet. And, since this is just for local storage, primarily, it shouldn't be as vulnerable as using 3DES for TLS channel encryption.
    • N-Krause 2y ago
      Thanks, even tho the comment above signaled sarcasm, the explanation was helpful for me, as I really had no idea what 3DES means and why it could be problematic.
      • Dalewyn 2y ago
        I shudder to think that even a simple Google query leading to a Wikipedia article was too much effort here... https://en.wikipedia.org/wiki/Triple_DES https://en.wikipedia.org/wiki/Triple_DES
        • b112 2y ago
          Any "simple" Google query now means pages of nonsense answers, promoted sites, AI "help", before you even get to a cogent result. Much better to just talk to others than use Google.
          • echoangle 2y ago
            When I google „TripleDES“, the first result is a box showing the Wikipedia article on Triple DES. Click on that and you’re done.
            • lupusreal 2y ago
              Create a search keyword for Wikipedia. Then you can type "wiki whatever" into your address bar and be taken right to Wikipedia without the google middleman.
          • Scoundreller 2y ago
            Reddit, got it. and Google and quora are in cahoots, right?
          • andrepd 2y ago
            Agree with the sentiment, but that's a Wikipedia link. Wikipedia is (as of yet) immune to LLM slop
            • nneonneo 2y ago
              Meh...not immune, just resistant. There's unfortunately a big difference. LLM slop is coming in at the corners, typically on articles that are less well-patrolled.
          • dspillett 2y ago
            > promoted sites, AI "help" I've been experimenting with Kagi for those reasons (amongst others) and finding it works well. Far from ideal for all as it isn't free after 100 queries, but it seems to be a workable solution to the problem for me for now.
        • N-Krause 2y ago
          The problem wasn't that a google search was to much effort, I just happened to be in the comments and saw this right with an explanation below it. I actually read up on it quite a bit afterwards. Feels very unwarranted to just assume laziness into a simple thank you for information spreading.
    • wtallis 2y ago
      For a password manager, whether a cipher is fast or slow could mean something entirely different than for something that has to encrypt and decrypt large amounts of data. Cycles per byte is probably completely irrelevant here and I'd expect performance to basically be a function of how many cache misses (both data and code) are incurred to decrypt a single password.
• captn3m0 2y ago
  The README is surely LLM slop.
  • dlenski 2y ago
    What…?
    • TheChaplain 2y ago
      https://en.wikipedia.org/wiki/Slop_(artificial_intelligence) https://en.wikipedia.org/wiki/Slop_(artificial_intelligence)
      • dlenski 2y ago
        I’m familiar with _the term_ and the phenomenon, but I am incredulous at the evidence-free claim that the project’s README is AI slop.
• jackjeff 2y ago
  It uses both AES and TripleDES If you glance at the code there's a single "key encryption key" in the whole SQLITE file (in the 'metadata' table). That key is decrypted using AES with the PBKDF2 derived secret. Then each password is in turn encrypted using TripleDES. The "data encryption key" for each these records is in turn encrypted using the aforementioned "key encryption key". My suspicion is that the TripleDES format must be really old, and when they migrated the crypto layer to use AES they just re-encrypted the top layer (the "key encryption key" later) to use AES. It's much faster (and safer) to just re-encrypt all the TripleDES keys with the new AES than go and mess with "all" the records in the database. It's inelegant and lazy but you effectively get "AES level" of security without having to do all the work, so to speak… https://github.com/Sohimaster/Firefox-Passwords-Decryptor/blob/main/recon/browser/firefox/passwords.go https://github.com/Sohimaster/Firefox-Passwords-Decryptor/bl...
  • alexey-salmin 2y ago
    I don't know about the particular case of TripleDES+AES but I think in a general case you can't claim that A+B encryption is always at least as strong as B alone. The A part can result in e.g. first bytes of input being the same enabling a crib-type attack.
    • jackjeff 2y ago
      I'm not defending this choice, and I think you're right in general. In this case, the only thing encrypted with TripleDES is the password itself, so the practicality of a crib or other known plaintext attacks is debatable in my opinion. If you use the same (or similar) password everywhere, then you have bigger worries than Firefox use of TripleDES. Password stuffing based with leaks from poorly hashed password DB (cough facebook cough) is likely the most practical attack vector in this case. If all your passwords are like q@qrG#Z4ARYm^qjeTEMN2Kh45v^p7L# then crib like attacks are impractical. There are other weird/debatable choices in the Firefox encryption layer: - Why bother with CBC? Things like AES-GCM or other authenticated* encryption mode would be nicer. Not sure it's a flaw here (google the cryptographic doom principle of Moxie Marlinspike) - Why not wrap the encryption keys with some kind of "key wrap" mode instead. There are such things as AES-KV for instance. - Why do the weird PBDKF2 derivation here? It's not based on a password the player enters, so there's nothing to "strengthen"? Seems oddly unnecessary (or I don't understand and there's a password somewhere). - If there's a password then PBKDF2 is really really shit compared to scrypt or even better one the variant of argon OWASP said you should use.