5 ms·

What do you suggest we use instead?

• cperciva 18y ago
  It depends on what you're doing -- and I'm not saying that there aren't places where SSL is appropriate (there certainly are). But to take a simple example: If you can securely distribute the hash of a file out-of-band, you're better off distributing the file over HTTP, and verifying its hash after it is downloaded, rather than distributing the file over HTTPS.
  • jrockway 18y ago
    Ah, great idea. Instead of using time-tested crypto, invent your own! That never goes wrong!
    • cperciva 18y ago
      Instead of using time-tested crypto, invent your own! That never goes wrong! The only cryptography I'm talking about using here is "if the file I download has the right SHA256 hash, it's the right file" -- and that's far more "time-tested" than SSL is. (And in any case, the rule against inventing ones' own cryptosystems is usually stated as "until you've shown that you can break other peoples' cryptography" -- so it doesn't apply to me.)
      • jodrellblank 18y ago
        Thinking that you can design your own crypto system is the flaw. If you can say "I did X so now that doesn't apply to me", then you're back to thinking it's OK for you to do it - in that case, it's not OK for you to do it again. Yes, that leaves nobody who can invent new cryptosystems. That's fine. I guess we'll have to get some smart person who doesn't think they can invent a good crypto system to do it, and who thus spends many years of careful, skillful analysis doing the best job they can instead. Oh well. ;)
        • cperciva 18y ago
          Even people who think they can invent good crypto spend years of careful, skillful analysis. :-)