HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

https://signal.me/#eu/tJgEd9pEdyiankVrQI3j1y2n5jPNLW7y4cZ09RJ0Vhjh2mihvq9IwL6toyfg8Kma

submissionscomments
jvehent··on Fighting Cargo Cult – An Incomplete SSL/TLS Bookmark Collection
Yet Another Test Script: https://github.com/jvehent/cipherscan It uses openssl to find out the cipher priorities, PFS keys and a few others things from a target site. I wrote it because, while I love SSLLabs and Ivan's work in general, I find it too slow to scan a setup I'm working on many times. And I like doing stuff in the terminal.
jvehent··on Fighting Cargo Cult – An Incomplete SSL/TLS Bookmark Collection
Author of the Mozilla's Server Side TLS here. Glad that you found it helpful. Anything else that you think we should add to it?
jvehent··on Tptacek's Review of "Practical Cryptography With Go"
It's not specific to cryptography. There is a hierarchy in all fields:

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."

jvehent··on Mozilla Moving Forward
And just to add to this :) http://people.mozilla.org/~smartell/cbeard/cbeard-illustrati...
jvehent··on Mozilla Moving Forward
People who are going to comment on this blog post need to realize how disturbing this episode has been for Mozillians.

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!

jvehent··on What do you need to make a successful web app?
On small websites, I use git to track /etc and /var/www (where the webapp code is installed). 5 years ago, I would have recommended to rsync the entire server daily. But nowadays it's a lot easier to snapshot an EC2 instance daily. For the database, just use RDS which handles point-in-time snapshot for you.

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.

jvehent··on OpenSSL Security Advisory: TLS heartbeat read overrun
Check for the extension:

    $ 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.
jvehent··on RegExr 2.0
No problem here with Fedora 20 and Firefox 31.0a1 (2014-04-04)
jvehent··on The Twitch Statistics Pipeline
"Our clients send base64 encoded JSON objects to our edge server using HTTP GETs."

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.

jvehent··on Show HN: Mogo Chat – open-source team chat app written in Elixir and Ember.js
This is cool, and as a heavy IRC user, I'm eager to find a solution that can replace self-hosted IRSSI+ZNC entirely, without compromising security. Don't reinvent the protocol, reinvent the UI.
jvehent··on Don't waste life
I saved 15 minutes by not reading this blog post :)
jvehent··on MozDef: The Mozilla Defense Platform
No. MozDef analyzes logs and events that are shipped to its data pipeline by servers and applications.
jvehent··on Mailgun Down – SSL cert is expired
protip: nagios.
jvehent··on TLS Triple Handshakes
Firefox is not vulnerable to this.
jvehent··on Go 1.2.1 is released
Happy rollback when it breaks ;)
jvehent··on Flask API – Browsable Web APIs for Flask
If you are still asking yourself that question, I strongly recommend you read this book: http://restfulwebapis.com/
jvehent··on Show HN: We just open-sourced a Skype replacement with HTML5
afaik, webrtc uses srtp, which is a separate from https.
jvehent··on SSL Labs: Stricter security requirements for 2014
I agree. Unfortunately, there is currently no way to configure different ciphersuites for different versions of TLS. With issues like BEAST, it would be highly beneficial if Apache, Nginx & others would supports ciphers preferences per TLS versions.

That still wouldn't help old clients. For them, only one solution: upgrade!

jvehent··on SSL/TLS analysis of the Internet's top 1,000,000 websites
That's an interesting piece of information! Thank you for sharing it.
jvehent··on SSL/TLS analysis of the Internet's top 1,000,000 websites
Chrome and Firefox (among many others) use NSS, which accepts patches ;)
jvehent··on SSL/TLS analysis of the Internet's top 1,000,000 websites
You mean this? https://wiki.mozilla.org/Security/Server_Side_TLS#Apache
jvehent··on A basic guide to when and how to deploy HTTPS
That's a good beginners guide. To take it a step further, check out the documentation that we maintain at Mozilla: https://wiki.mozilla.org/Security/Server_Side_TLS
jvehent··on People Don’t Actually Like Creativity
Fantastic lecture indeed, and very well delivered!
jvehent··on History of T
Is ctrl+ really that hard to do?
jvehent··on Open Source Implementation of the Two-Man Rule in Go
If you are root, you can also strace the process and grab the password, without modifying anything.

If the platform isn't secure, the app can't be trusted. Basic defense rule.

jvehent··on How to set up a mail server on a GNU / Linux system
I wrote something similar, that uses Postfix, Dovecot, OpenLDAP, Roundcube, DSPAM and OpenDKIM. http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:n...

I presented it at my local LUG a while back, here are the slides http://www.slideshare.net/jvehent/di-ymail

jvehent··on Security/Server Side TLS
Nginx has a patch to store them in memcache, for what it's worth. It's far from ideal, but at least it's not persistent storage. The standard is still to point clients to a single termination endpoint, and do active/passive cluster, so that there's no need to share the session tickets.

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.

jvehent··on Security/Server Side TLS
Not yet, but we plan to add a correspondence table between OpenSSL and GnuTLS. Any contribution is most welcomed.
jvehent··on Security/Server Side TLS
We don't control what the client enables. Any client could decide tomorrow to disable AES-128, and we need to support that.

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 ;)

jvehent··on Security/Server Side TLS
Yes, the goal is to provide a ciphersuite that can be copied directly. But instead of stopping after the first paragraph, we explain why we think this ciphersuite is best. The guideline is not just a ciphersuite, it's a study of the state-of-the-art of SSL/TLS.

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.

← PreviousPage 10 of 14Next →