Next privilege 125 Rep.
Next badge 0/1
0 people reached
- 0 posts edited
- 0 helpful flags
- 7 votes cast
Sequential identifying string that can't be reverse engineered (the “invoice number” problem)
I think hashids are reasonable for this use case. While hashids are reversible, they start short, they are guaranteed to be unique, and it prevents offensive English words (like fuck) from appearing as hashes. The reversibility can be mitigated by using a large secret. It won't be crypto secure like a UUID, but it does have many properties that are desirable for client facing Invoice Numbers.
Is it common practice for companies to MITM HTTPS traffic?
@TechnikEmpire I believe point 2 is where the software maker (not a remote party) verifies the cert fingerprint, in addition to verifying that the OS's CA Certs agree that the cert is valid.