3 ms·

Passwords have low entropy and high reuse, so they can be used outside of their purpose, which is to allow access to a single resource. A salted hash is only us

by jl2718 4y ago

Passwords have low entropy and high reuse, so they can be used outside of their purpose, which is to allow access to a single resource. A salted hash is only useful to the resource it provides access to, and a salted and peppered hash provides resistance from external unsalted disclosures. TLS in the browser is intentionally insecure. All browsers allow a back door . certificate to MITM every connection through proxies. Guess what happens to that traffic? Decrypted, stored, sent off to third parties, who knows what. Every major corporate network does this. An actually-secure protocol would enforce client certification to the device manufacturer’s authority, or at least to the browser vendor’s authority. Regarding the attack surface, use this: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypt... Please do not send passwords off the client. Use a standard (I’m surprised that no such thing exists in an accessible way from the browser), but the protocol should look something like: enter password, digest, salt, digest, tls, pepper, digest, encrypt, store. Asking HN: is there an open standard that actually spells out 100% of a password management protocol with highly trusted implantations on both sides?

jagged-chisel 4y ago
> Every major corporate network … That specific complaint seems to me more about trusted roots - corporate can just install their own CA cert on each machine. What backdoor are you talking about? Sounds like administrative access to the computers owned by the company. The seasoning and digesting doesn’t solve that problem. Every company also has the wherewithal to copy/store/transmit anything typed into an input field on computers they own. If there’s some other intentional “browser backdoor” (not social engineering attempts against end users) for installing random signing certs, I’d like to read about it. If I own the hardware and control the software installed on it (notwithstanding infiltration), none if my TLS traffic is peeled open on the way to its destination.
- jl2718 4y ago
  Please understand that a CA is a human person, subject to all laws of the jurisdictions in which they reside, as well as human nature.
GoblinSlayer 4y ago
>Asking HN: is there an open standard that actually spells out 100% of a password management protocol with highly trusted implantations on both sides? If you don't want to go full asymmetric cryptography, there's SCRAM. It doesn't specify pepper, but pepper can be added to salt like for any salted scheme: salt=hash(pepper, stored salt);

by jl2718 4y ago

jagged-chisel 4y ago

> Every major corporate network … That specific complaint seems to me more about trusted roots - corporate can just install their own CA cert on each machine. What backdoor are you talking about? Sounds like administrative access to the computers owned by the company. The seasoning and digesting doesn’t solve that problem. Every company also has the wherewithal to copy/store/transmit anything typed into an input field on computers they own. If there’s some other intentional “browser backdoor” (not social engineering attempts against end users) for installing random signing certs, I’d like to read about it. If I own the hardware and control the software installed on it (notwithstanding infiltration), none if my TLS traffic is peeled open on the way to its destination.

jl2718 4y ago
Please understand that a CA is a human person, subject to all laws of the jurisdictions in which they reside, as well as human nature.

GoblinSlayer 4y ago

>Asking HN: is there an open standard that actually spells out 100% of a password management protocol with highly trusted implantations on both sides? If you don't want to go full asymmetric cryptography, there's SCRAM. It doesn't specify pepper, but pepper can be added to salt like for any salted scheme: salt=hash(pepper, stored salt);