3,020 karma · joined March 15, 2010
https://signal.me/#eu/tJgEd9pEdyiankVrQI3j1y2n5jPNLW7y4cZ09RJ0Vhjh2mihvq9IwL6toyfg8Kma
1. Top researchers come up with algorithms and techniques
- The research corpus reviews them
2. Top programmers implements these techniques - The programmers communities review them
3. Top engineers write books to explain these techniques - which everybody else relies on in their tools
1 knows more than 2 which knows more than 3. But each group needs the two others, and the rest of the worlds needs all of them. People who write books are rarely the same people who come up with cryptographic breakthrough. Instead, they are engineers, and they can use a bit of help to get things right.Your review was harsh, because you know more. What, I think, was missing from it is a bit of "This is a great first step, let me help you make it better so we can move everybody else forward. Here are my comments."
We are talking about a small group of people, a couple thousands at best, that work with limited resources to keep the web open for everybody.
When this tidal wave hit Mozillians, the base contributors and employees who spend most of their days in code and features, we lost focus of our work, and stepped into a world of politics that most of us dislike, and are uncomfortable to navigate.
I believe Chris Beard is a true Mozillian, as is Brendan Eich. And I am glad that we can refocus on our mission, and move forward. I just wish people can put their differences aside, accept each other's beliefs, and share code!
If you're a developer with little linux experience, don't try to play the sunday morning sysadmin with fancy bash scripts on your startup. It takes a lot more time and resources to keep a system in good state than you can foresee.
$ echo -e "quit\n" | openssl s_client -connect google.com:443 -tlsextdebug 2>&1| grep 'TLS server extension "heartbeat" (id=15), len=1'
TLS server extension "heartbeat" (id=15), len=1
This doesn't tell you that the server uses OpenSSL, or that it is vulnerable, simply that it supports the extension.Encoded json in get parameters? That's not what GET requests are for. use POST requests for that, or you'll quickly be limited by the max size of a get request, somewhere around 8KB.
That still wouldn't help old clients. For them, only one solution: upgrade!
If the platform isn't secure, the app can't be trusted. Basic defense rule.
I presented it at my local LUG a while back, here are the slides http://www.slideshare.net/jvehent/di-ymail
I still believe that using PFS, even with this limitation, is safer than encrypting pre-master keys with a single private key that almost never rotates and is stored on plenty of servers.
The ciphersuite focuses on ordering ciphers by strength and performance, and we don't just disable cipher for the sake of keeping it small. After all, it's the same number of clicks to copy a large ciphersuite than a small one ;)
At the end of the day, it's not realistic to imagine that everyone will spend days researching this to come up with a proper ciphersuite. There is a strong need for guidance.
You are correct about SSLv3: it is up to each organization to stop supporting it. But do know that it is still widely used, if not in browser, in client libraries. I wouldn't turn it off on a corporation site if I were you.