3 ms·
You appear to be shadowbanned for no immediately obvious reason. I vouched this comment to point out that it contains a factual error, to wit, the claim that th
by throwanem 9y ago
You appear to be shadowbanned for no immediately obvious reason. I vouched this comment to point out that it contains a factual error, to wit, the claim that the headers and URI of a request made via TLS are sent in the clear. They are not; the socket is encrypted before any protocol messages are exchanged. Perhaps you're thinking of SMTP STARTTLS?
Companies have moved to OAuth, and to JWT as the payload, because it provides a lightweight, shared-little authentication/authorization framework that's well suited to the needs of a distributed microservice architecture and to third-party service integration - not because it overcomes a nonexistent problem with HTTPS not encrypting headers.
- 0x0 9y agoA properly configured SMTP STARTTLS would not really send anything substantial in cleartext either, it would issue the STARTTLS command as the first command and the rest would be wrapped in encrypted TLS. You can think of the unencrypted STARTTLS preamble as a set of static ascii bytes that are the same for every connection.
- throwanem 9y agoIt's the closest common parallel I can find for what the prior commenter is describing, but yeah, it isn't really all that close. I've seen poor implementations leak, but not for many years now.
- bmm6o 9y agoI don't think the op had something else in mind. IME it's a strangely widespread misunderstanding that https encrypts just parts of the http request. I think it's because of the advice to not put sensitive data in urls. The reason for that is due to logging at the endpoint, but it's misunderstood that it's not encrypted. It's funny because it's so easy to test the hypothesis, and it's hard to even propose a reason it would be that way.
- ataturk 9y agoI am shadow banned because my politics are unpopular here. I am locked to 2 posts every few hours because otherwise my dangerous ideas might get out into the wild. Thanks for the clarification on the headers part, though. As I said, I am no expert on TLS, only work on micro services that don't have to be heavily secured and have done work with OAuth and noted that API keys aren't much favored anymore. I really a am a thoughtful, well-rounded person, it's not my fault that the Internet world won't accept me, or perhaps because Y-Combinator has a particular agenda.