Viewing profile — lexman0
lexman0
HN member- Joined
- Tue, Aug 30, 2016, 11:44 AM UTC
- HN karma
- 117
- Public activity
- 10 items
- HN profile
- View on Hacker News ↗
About lexman0
No profile information was provided.
Recent public activity
-
comment
Comment #13752346
This is my thinking. >> Not a hash of the contents, just the sub/external domains' key-ids. Yes, the main page would have to change if you updated the keys. Doesn't seem too onerou…
-
comment
Comment #13752148
> Should you ever really trust kiosk machines? They could easily be setup with MITM eavesdropping software. I should have the choice. This doesn't even give me that. > Presumably t…
-
comment
Comment #13751995
I completely disagree with this. Public key pinning has some well known problems that make it very dangerous to implement at scale [1]. There are some very large problems that this…
-
comment
Comment #13063979
While HPKP looks good, I really wouldn't implement it. Too dangerous for big sites in it's current form. Ivan puts it better than me: https://blog.qualys.com/ssllabs/2016/09/06/is-…
-
comment
Comment #12863935
Generally the cliche is about not implementing your own cryptographic algorithms. As long as they only implement existing algorithms and don't generate new ones, I don't think this…
-
comment
Comment #12787693
"Although Mozilla’s sanctions are too severe..." These guys must be joking. Trust has been lost, the roots should be permanently revoked. If anything, I think Mozilla's actions are…
-
comment
Comment #12684516
Oh no! Now where will I get my smug sense of satisfaction from?
-
comment
Comment #12642358
True enough. But those who steal your account information and use it to pose as you don't follow the rules and regulations.
-
comment
Comment #12642300
There are a lot of keyboard warriors in this thread. This guy puts forward a rational argument for big business. Unless you have extensive experience in this area, perhaps you shou…
-
comment
Comment #12389152
I'm a bit disappointed that this article doesn't mention the threats specifically that SSL in this way will defend against.. So what if the back end isn't encrypted? How much more …