HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

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

submissionscomments
jvehent··on Mozilla SSL Configuration Generator
It's a tricky thing to do because of all the possible versions of all the possible web servers. The dropdown would end up being rather long, and require maintaining a list in the code. And then there's distribution specific backports, etc...

So we tabled this problem for now and went with a free field, but please do open a github issue and we'll add look for ways to do it.

jvehent··on Mozilla SSL Configuration Generator
You can reuse the same diffie-hellman parameter. It's a public value anyway.
jvehent··on Mozilla SSL Configuration Generator
Very good catch! Thanks for bringing it up. I had reverted the first one but missed the two others.

Unfortunately, mediawiki only support two levels of access control: fully locked or fully open, so I need to manually police changes as they happen...

jvehent··on Mozilla SSL Configuration Generator
Hello HN, author of Server Side TLS [1] and co-maintainer of the conf generator here. Thanks for pushing this tool to the front page :) We've been improving our guidelines and this generator for the past year and a half, and while it in a pretty good shape, we always welcome comments and pull requests.

One comment that we get very often regards the ordering of the recommended ciphersuite. We've made some choices that are documented in [2] such as, for example, preferring AES 128 to 256 or maintaining compatibility with CAMELLIA and DES-CBC3-SHA in the intermediate configuration. The best place to discuss these choices is probably the `talk` section of the wiki page [3].

[1] https://wiki.mozilla.org/Security/Server_Side_TLS [2] https://wiki.mozilla.org/Security/Server_Side_TLS#Prioritiza... [3] https://wiki.mozilla.org/Talk:Security/Server_Side_TLS

jvehent··on Code Generation from the AST in Go
What if they are right, and saying no is the reasonable way to keep the language lean and efficient?
jvehent··on How to build a Debian package
Most definitely. I use it for building RPM, DEBs and even MacOS PKGs and it works great. https://github.com/mozilla/mig/blob/master/Makefile#L233-L27... Package signing could use some love, but it's still doable easily with a few extra steps.
jvehent··on Mozilla MASCHE – Memory Forensic Library
When MIG was started, in the summer of 2013, Rust was still too unstable to be a good candidate. Go, however, already had the toolkit to build cross-platform agents, so I went with this.

18 months in, I still think it was the right choice. Go is extremely powerful and yet simple enough for contributors to pick it up in a matter of days. I don't think we could have delivered as much value going with Rust, it's still too young and lack the necessary libraries (AMQP, OpenPGP, etc...).

jvehent··on Mozilla MASCHE – Memory Forensic Library
You are correct: MIG is designed to prevent a rogue investigator from executing random commands on systems. We do so by filtering what agents can run through modules, and by requiring OpenPGP signatures on all actions ran.

Even if the MIG platform is compromised, agents and systems are safe, as long as the keys of authorized investigators (kept on their laptops) are not compromised.

jvehent··on The HTTPS-Only Standard
They also use a pretty strong TLS conf https://gist.github.com/jvehent/98fdfef139b6237f7bf5

What strikes me is that their conf is inaccessible to old client (no sslv3, no sha-1 cert). Honest question: does the government think it's ok to break website access from ancient clients (XPSP2 IE6)? Or will they be forced to enable legacy ciphers when the first citizens complain? I'm genuinely interested, because the topic of TLS modernity is a hard problem to solve. If that was easy, google.com wouldn't be using RC4-MD5 and a sha-1 cert...

jvehent··on End-to-End Encryption Plugin for Yahoo Mail
GPG in Mutt is fantastically well integrated.

Now, of course, you have to get used to Mutt first :)

jvehent··on Making Pinterest HTTPS
75% of alexa's top 1 million have RC4 enabled [1]. It will take a lot of evangelizing to finally get rid of it.

[1] https://securitypitfalls.wordpress.com/2015/03/13/february-2...

jvehent··on Making Pinterest HTTPS
Looks pretty good. Their configuration could use a larger DHE parameters (2048), replace RC4 with 3DES and enable OCSP Stapling. But it's already in the top 1% for TLS quality!

    $ ./cipherscan pinterest.com
    ................
    Target: pinterest.com:443
    
    prio  ciphersuite                  protocols              pfs_keysize
    1     ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2                ECDH,P-256,256bits
    2     ECDHE-RSA-AES128-SHA256      TLSv1.2                ECDH,P-256,256bits
    3     ECDHE-RSA-AES128-SHA         TLSv1,TLSv1.1,TLSv1.2  ECDH,P-256,256bits
    4     DHE-RSA-AES128-SHA           TLSv1,TLSv1.1,TLSv1.2  DH,1024bits
    5     ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2                ECDH,P-256,256bits
    6     ECDHE-RSA-AES256-SHA384      TLSv1.2                ECDH,P-256,256bits
    7     ECDHE-RSA-AES256-SHA         TLSv1,TLSv1.1,TLSv1.2  ECDH,P-256,256bits
    8     AES128-GCM-SHA256            TLSv1.2
    9     AES128-SHA256                TLSv1.2
    10    AES128-SHA                   TLSv1,TLSv1.1,TLSv1.2
    11    AES256-GCM-SHA384            TLSv1.2
    12    AES256-SHA256                TLSv1.2
    13    AES256-SHA                   TLSv1,TLSv1.1,TLSv1.2
    14    ECDHE-RSA-RC4-SHA            TLSv1,TLSv1.1,TLSv1.2  ECDH,P-256,256bits
    15    RC4-SHA                      TLSv1,TLSv1.1,TLSv1.2
    
    Certificate: trusted, 2048 bit, sha256WithRSAEncryption signature
    TLS ticket lifetime hint: 300
    OCSP stapling: not supported
    Server side cipher ordering
jvehent··on Bank harrasses user because he tweeted screenshot of their SSL certificate
Along the same line, there are currently around 4,000 sites in Alexa's top 1 million that only support RC4. Nothing else.

Some of these sites have large user bases too, and it's making it hard to disable RC4 in Firefox. https://bugzilla.mozilla.org/show_bug.cgi?id=1138101

jvehent··on Academia's 1%
The same rule holds true for jobs in the private sector: work for a high profile company (Google, Apple, Facebook, ...) and you will find doors open everywhere. Getting there in the first place is the real challenge.
jvehent··on The Freak Attack SSL/TLS Vulnerability
> let those rare clients use non-PFS suites

That's not acceptable for us, which is why DHE is there. Mozilla aims to provide the best possible security to the larger number, and that drives a number of the choices in the recommended ciphers.

jvehent··on The Freak Attack SSL/TLS Vulnerability
Author of Server Side TLS here. Almost everyone should be able to use the intermediate configuration we propose. I recommend our conf generator at https://mozilla.github.io/server-side-tls/ssl-config-generat... . Cipherscan is also a good tool to have in your toolbox: https://github.com/jvehent/cipherscan
jvehent··on Walmart Labs: Why we run an open source program
You know what's cooler than working for Walmart? Working on disrupting Walmart, and forcing them to increase the quality of the products they sell to keep competing.
jvehent··on GPG and Me
I'm eagerly waiting for something better to come up. There hasn't been anything satisfying so far, so I keep encrypting truly confidential communication with GPG, and it gets the job done.
jvehent··on Ask HN: Got hired for a position that doesn't exist. How do I leave?
This is good advice. I went through similar experience in my 2nd and 3rd jobs, where the work of "junior security consultant" was reduced to pushing compliance paperwork. I ended up studying tons of new technologies on my own, and publishing tech articles in local magazines. It helped my resume tremendously when I got out of the consulting business.
jvehent··on Ask HN: How do you analyze logs?
At Mozilla Opsec, we use (and write) MozDef: https://github.com/jeffbryner/MozDef/
jvehent··on Comcast: Simulating shitty network connections so you can build better systems
I don't need this, I have comcast.

    $ sudo ping -i 0.02 8.8.8.8
    [...]
    64 bytes from 8.8.8.8: icmp_seq=578 ttl=53 time=15.5 ms
    ^C
    --- 8.8.8.8 ping statistics ---
    579 packets transmitted, 364 received, 37% packet loss, time 13854ms
    rtt min/avg/max/mdev = 15.009/19.308/50.884/6.152 ms, pipe 2
jvehent··on Last Call: HTTP2
It got 3 years :)
jvehent··on The Software Scientist
Maybe the author understands programming as "writing lines of code", and not as "architecting software".

Architecture requires experience. Writing the fastest quick sort in a given language is an exercise for fresh young brains.

jvehent··on Robdns – A fast DNS server based on C10M principles
> TCP connections that don't match a handful of patterns would be suspicious (IMHO) and should probably just be dropped.

I used to believe that. It is unfortunately not true. TCP packets will come in all shapes and forms, and all must be treated equally, which is what makes TCP stacks so incredibly complex to implement.

The Linux TCP stack is quite safe and fast. Especially with tight integration with NICs hardware (checksum offloading and the like). I'm a bit unsure what a custom stack in userland can provide that the standard kernel stacks don't have.

jvehent··on Robdns – A fast DNS server based on C10M principles
"The key feature is a built-in custom TCP/IP stack capable of handling millions of DNS queries-per-second per CPU core."

DNS uses UDP primarily. I suspect the author meant "UDP/TCP/IP" by "TCP/IP".

Years ago, I wrote a basic TCP stack for a honeypot research project. It is hard and incredibly complex. So this statement raises a number of concerns, and will need to be audited before being used in production.

jvehent··on Sum Types in Go
Idiomatic. http://www.merriam-webster.com/dictionary/idiomatic
jvehent··on Show HN: Initial release of H2O, and why HTTPD performance will matter in 2015
That's a cool project. Performance is a fascinating topic.

However, in the real world, the number of requests per second a http daemon can perform is the last thing to worry about. If the web is slow, it's not because Apache used to be bloated with thread. It's because of bad architecture: centralization of services, latency in page builds time, size of static components, data store bottlenecks, etc...

Nevertheless, a very cool project. One I'll follow closely.

jvehent··on Pure Go Postgres driver for database/sql
I've been using this driver heavily for about 9 months now, and it has served me flawlessly so far. Definitely recommended!
jvehent··on Sell Services on Amazon
And comments! Reputation is critical for services, those 5 stars are going to become very important to business owners.
jvehent··on Gngr – A new browser championing privacy
If what you want is a minimalistic browser, don't run a JVM, use elinks! It even has colors: http://4u.1nw.eu/elinks_hn.png
← PreviousPage 8 of 14Next →