HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

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

submissionscomments
jvehent··on Instagram rolling out algorithmic feeds to some users
I agree. The clickbaity title actually makes me want to skip that article, whereas an informative title like you proposed would make me read it.
jvehent··on Qb: Database toolkit for Go
How does it compare to https://github.com/jinzhu/gorm/ ?
jvehent··on Chatbots Are the Newest, Dumbest Co-Workers
That's what your boss is for.
jvehent··on Scaling Down Gracefully with AWS Lambda and HAProxy
Soft reload takes care of that for you, sockets aren't dropped.

If you restart, however, everything's dropped.

jvehent··on Taskwarrior – intelligent TODO list
I use taskwarrior with bugwarrior [1] to automatically maintain a list of pending bugs/issues and pull requests assigned to me. The initial setup takes a couple hours, but it's a great way to track stuff spread across dozens of locations.

[1] http://bugwarrior.readthedocs.io/en/latest/

jvehent··on Infosec's Jerk Problem (2013)
That only works if your application is simple enough for the infosec folks to know how to write a patch for it.

If the organization has 200 of those apps, it's unlikely a transversal security team is able to write patches for each one of them.

jvehent··on Infosec's Jerk Problem (2013)
I've seen this happen way too often at various organizations. My take away is security is a function of the product, not some external process you bolt on top of it.

Organizations typically fail at security because they try to manage it as far away from the product as possible. That leads security and dev/ops teams to manage their goals in isolations: one cares about preventing incident, the other cares about shipping products.

If Agile & DevOps have taught us anything, it's that everyone in the organization should be focused on serving the customer, be it through features, reliable operations, or data security. The only good way to do infosec is to embed security with devs and ops and make everyone shares the goal of making the product better.

jvehent··on We only hire the trendiest
Can you share an example of challenge given to candidates? In the past, I've used "script a file sharing tool that handles encryption", which worked well and took candidates ~4/8 hours to complete, but isn't something we used directly in our projects.
jvehent··on Jo - JSON output from a shell
echo 'alias json="$(which jo)"' >> ~/.bashrc
jvehent··on What's the Best Cloud? Probably GCP
> Not to say 150th isn't impressive or likely a lot of traffic..

Ballpark, I'd say that's between 700 and 1,000 hits/second on the main frontend. I sort of doubt either AWS or GCP is so much faster than the other for this kind of load.

jvehent··on Ten years on LinkedIn
Those articles are useful: everytime someone mentions LinkedIn, I remember to check my account.

Without them, I'd pretty much never open the site.

jvehent··on “I've been working at Mozilla for many years, from peak to decline”

   Since they have so much money to burn, why don't they support worthwhile OSS efforts (like SSL, for example)? 
The NSS library is supported by Mozilla and Red Hat, mostly.

   There are tons of little tools and libraries that we use in *nix land, that could benefit from some $$.
Mozilla is much more than just Firefox, Firefox OS and Thunderbird. Take a look at the hundreds of projects on https://github.com/mozilla/, for example.

    Mozilla should offer "Mozilla fellowships" or "Mozilla sabbaticals", where they support a developer for a year or two fulltime to work on their projects.
There are many internships, community supports and developer support programs at Mozilla. The foundation also donated one million dollars to various prominent projects very recently: https://blog.mozilla.org/press/2015/10/mozilla-launches-open...

    Most of Mozilla's work is done by volunteers anyways
I don't know if this statement is accurate. There are over 1,000 people employed by Mozilla directly working full time on the various projects.

disclaimer: I work for Mozilla.

jvehent··on The DROWN Attack
Yes, as long as one of the server that shares the keypair has SSLv2 enabled.
jvehent··on CacheBleed: A Timing Attack on OpenSSL Constant Time RSA
The important bit, if you have to decide on patching emergency:

OpenSSL has classified this vulnerability as "low severity", which we agree with. In order to mount the attack, the attacker has to be able to run the attack code on the same machine that runs the victim code. CacheBleed is a complex attack and there are much easier-to-exploit vulnerabilities in personal computers that it is unlikely that anyone would use CacheBleed in such an environment.

Note that frameworks that embed OpenSSL, such as NodeJS, will need to be upgraded as well. https://groups.google.com/forum/#!topic/nodejs-sec/ORAkxchrT...

jvehent··on The DROWN Attack
From a pool of 11 million scans of HTTPS sites, I could only find ~265k targets with SSLv2 enabled [1]. That's 2.4%, not 25%.

A breakdown of the type of target that have SSLv2 enabled would be useful to understand how they reached that number. It's possible that they scanned much much more than HTTPS on port 443, and found a lot of embedded devices with poor SSL configurations.

At any rate, you should verify the configuration of your websites. There are many tools to do that, and we publish configuration sample to make it easy: https://mozilla.github.io/server-side-tls/ssl-config-generat...

[1] https://twitter.com/jvehent/status/704657734810148864

[edit] the page https://drownattack.com/top-sites shows that sites like yahoo.com are vulnerable, but there are no details as to why it is listed vulnerable. yahoo.com does not allows connections with SSLv2, but some of its subdomains do, so maybe the top-level domain is listed because some of its subdomains are vulnerable?

[edit 2] according to one of the researcher, the scanner "check if pubkey (not cert) runs on SSLv2. Then mark all others with that pubkey vuln" (src: https://twitter.com/seecurity/status/704665265712308224)

jvehent··on Early Impacts of Let's Encrypt
tldr: Let's Encrypt is achieving its original mission: help people use TLS on domains that were previously insecure, and make the internet a safer place.

> In the first quarter of its' operation then, Let's Encrypt has far and away been used more to secure previously-unsecured (or at least untrusted) websites than simply as a cost-savings measure.

jvehent··on Glibc getaddrinfo stack-based buffer overflow
iptables -t filter -A INPUT -p udp --sport 53 -m connbytes --connbytes 512 --connbytes-dir reply --connbytes-mode bytes -j DROP

iptables -t filter -A INPUT -p tcp --sport 53 -m connbytes --connbytes 512 --connbytes-dir reply --connbytes-mode bytes -j DROP

jvehent··on Investigate switching away from GitHub
Fine grained classification and management of issues is why Mozilla is so reliant on Bugzilla.

Bugzilla is a beast, for sure, and it takes some time to learn how to use it correctly, but few other systems come close in functionalities, and github is certainly not one of them.

jvehent··on Kill Your Dependencies
This is pretty much what Rob Pike advocates in Go: "A little copying is better than a little dependency." http://go-proverbs.github.io/
jvehent··on SSH: Best practices
It's all a matter of prioritization. In an ideal world, address all the issues and be perfectly secure. But if you have to choose by priorities, private ssh key compromise is not exactly at the top of my concerns because people are generally careful about their keys.
jvehent··on SSH: Best practices
You're describing the workflow of an APT attack. Those are extremely costly, take several months to complete and definitely involve highly technical skills. I agree they are a real threat, but not to startups, to Fortune 500 companies.

For startups, the #1 risk is a vulnerability in some web app, or a forgotten admin panel, that leaks the entire database to an attacker. Not a complex attack conducted by a nation-sponsored offensive team.

But again, SSH security matters, you should take it seriously.

jvehent··on SSH: Best practices
> 3. Never grand direct SSH to access the the staging/production environment.

Most complex systems fail in unexpected ways, and the best way to debug is to grant the devs access to production machines. It can be temporary, monitored and through a secure channel, but it's still something most organizations can hardly live without.

jvehent··on SSH: Best practices
> Developer laptop compromise is probably the biggest security risk that any startup company faces, because the developer laptop is an uncontrolled environment with a lot of "attack surface" which may have been previously compromised.

It's also the least likely to happen. Attackers will have broken deep into your database due to poor webapp security before getting a hold of your ssh private key.

Not that SSH security doesn't matter. It's easy enough and carries enough risks that putting some effort into it is worthwhile.

jvehent··on “We will end development on Firefox OS for smartphones after the 2.6 release”
They were distributed to several hundreds mozillians last year. I used one for a while. Excellent device, very responsive with FxOS on it. If it had enough apps, it could have been competitive...
jvehent··on The State of Go: Where we are in February 2016
This is my experience as well. The only thing that somewhat breaks between Go project is vendoring (or lack thereof). But in comparison to the pain of supporting python applications that must run on everything from 2.6.6 to 3.5, Go is a walk in the park.
jvehent··on RabbitMQ Internals
Use cases and examples are pretty scarce. The doc is accurate, but understand the doc for a newcomer to the tool is difficult.
jvehent··on OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)
That's what your local security team should be for ;) At Mozilla, we track those and inform the various ops teams of our assessments. They very much rely on us to decide if it warrants emergency patching or not (modulo operational concerns to upgrade systems outside maintenance windows).
jvehent··on RabbitMQ Internals
This is cool! RabbitMQ could really use better documentation. I had to implement permissions for MIG a while ago, and it tooks many trials and errors to get it right. https://github.com/mozilla/mig/blob/master/tools/create_rabb...
jvehent··on OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)
Ops teams need a clear "should I do emergency patching? yes/no" message when any vulnerability gets published. In this instance, it looks like this doesn't require emergency patching unless you're using something unusual to terminate SSL.

That said, it's a serious issue, no doubt about that.

jvehent··on OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)
Thanks for the excellent description of the vuln! You mention Apache not being vulnerbale. I just looked through the Nginx code, and it doesn't seem to be vulnerable either because Igor Sysoev enabled SSL_OP_SINGLE_DH_USE back in 2008. https://github.com/nginx/nginx/blob/master/src/event/ngx_eve...
← PreviousPage 5 of 14Next →