HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

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

submissionscomments
jvehent··on The Beauty of LaTeX (2011)
I prefer HTML & CSS, maybe with something like restructuredText on top.
jvehent··on Why we use HTTPS for every .gov website we make
Do you have to maintain backward compatibility with Windows XP pre-SP3 for gov sites? That would require SHA-1 certs and SSLv3.
jvehent··on Facebook Go Libraries
> If you're not big enough, then it probably doesn't affect you anyway.

How so?

jvehent··on Facebook Go Libraries
...and the Apache 2.0 license belongs to a short list of licenses that have been extensively reviewed and can be trusted.

Every time someone comes up with a new license, the review work must be redone to ensure it respects the philosophy of Open Source. Which is why I prefer project published under well-known licenses (GPL2/3, LGPL, Apache, Mozilla, BSD, ...).

jvehent··on Facebook Go Libraries
This is the first time I see a patent file in an open source project [1] and now I know I won't use this until my lawiers take a look at it. Sad world...

[1] https://github.com/facebookgo/runcmd/blob/master/patents

jvehent··on Half a decade with Go
Writing in Go has made me find Python code ugly. Much like Python made me dislike Perl many years ago. That is, of course, very subjective.
jvehent··on Celebrating 10 Years of Firefox
I was a Mozilla Suite user 12 years ago. Then became a passionate Firefox user and supporter of the Open Web. Happy Birthday Firefox! Looking forward to 10 more years!
jvehent··on Celebrating 10 Years of Firefox
In my opinion, Firefox for android is vastly superior to chrome.
jvehent··on Osquery: Expose the operating system as a relational database
MIG author here. First, congrats to Mike Arpaia for shipping! That must have been a busy couple of months :)

There is a number of conceptual differences between MIG, GRR and OSquery. MIG does not retrieve data from endpoints, but instead focuses on answering yes/no questions.

For example: find hosts that have a file in /var/www that contains the regex '12345'. MIG will run the search on all endpoints and return the location of files and hosts that match. But it won't return the files themselves. Privacy is preserved, but investigators need to manually retrieve files if needed. MIG takes this approach to keep the search very fast (parallel AMQP runs in seconds across thousands of endpoints). Retrieving data at large scale is too expensive for Mozilla (bandwidth, storage, execution time), and we like to protect privacy.

I really like the SQL approach taken by osquery. I brainstormed something similar last year [1] but did not get around to it yet. SQL is very natural to use for a lot of IT/Security people, and it's great to be able to transfer that knowledge to search tools.

GRR and OSquery are awesome tools. And I can tell their authors are solving some really hard problems. We're competing a bit, but it's OK to have multiple tools with varying goals. And it's great for borrowing each other's good ideas ;)

[1] http://4u.1nw.eu/Presentation_workweek_20130916.pdf slides 10 & 11

jvehent··on TLS scan results for October 2014
"SSLv3 support has taken a blow, its use has fallen by over 26%, bringing its support to 69.5% [of sites]"

That's not enough! Administrators still don't pay enough attention to their crypto configurations. We try to make this easier in Mozilla's guidelines [1], but it still is a complex and mostly misunderstood topic.

[1] https://wiki.mozilla.org/Security/Server_Side_TLS

jvehent··on Making sure crypto remains insecure [pdf]
I found this particular talk to be different that the usual DJB. It felt more like a self-reflection on why, despite being technically correct, his cryptographic solutions always fail to gain mainstream traction.

I have a lot of respect for DJB and for the way he always challenges the status-quo. This talk is an excellent summary of the current issues in the crypto industry. But he ignores the fact that we use AES, SHA and RC4 because _it's easy to use them_. And his solutions are never easy to use.

Make Nacl dead simple to use. Write clients and servers that use it. Integrate it into Firefox, Chrome, Dovecot, Nginx, Postfix, cUrl, etc... and people will slowly move away from TLS and its broken crypto.

jvehent··on Making sure crypto remains insecure [pdf]
Not being one of them myself, I can only notice that their time is limited, and many much wanted improvements sit on the backburner waiting for a smart crypto implementor to work on them.

NSS and OpenSSL are difficult codebases to work with, which may also explain why it's so hard to find people to work on them.

jvehent··on Making sure crypto remains insecure [pdf]
If anyone has the time and skills to implement these curves in NSS, I'm sure that the Firefox and Chrome security teams would be more than happy to enable them!
jvehent··on Making sure crypto remains insecure [pdf]
Bernstein on a "thought experiment", analyzing how government could have deliberately weakened cryptographic standards through various means. It's actually quite compelling, given that we know DES key size was weakened by the NSA back in the 70s, against IBM's will, and that we know Dual_EC_DRBG was backdoored also by the NSA a few years ago.

Bernstein's main point is that we need independent, peer-reviewed, cryptography that doesn't depend on government standardization. This talk is mostly a justification for his own work on ChaCha20/Poly1305 and DNSCurve, that were designed to be fast, constant-time and padding resistant. But the talk doesn't make mention of alternatives, except for Serpent that should have been a better cipher than Rijndael in the AES competition.

A good read. I would love to see broader adoption of ChaCha20 in OpenSSL and its standardization in TLS1.3. Google already supports it and it needs more attention from cryptographic before we start using it everywhere. It also seems that SHA-3 has failed to convince, and everyone is standardizing on SHA-2 instead, despite the computational cost. Maybe here too we need an alternative...

jvehent··on This POODLE bites: exploiting the SSL 3.0 fallback
I'm assuming that a user stuck on IE6 doesn't have the necessary technical expertise to upgrade or change security parameters.
jvehent··on This POODLE bites: exploiting the SSL 3.0 fallback
To business owners and large sites operators out there: before disabling SSLv3, make sure that none of your clients/customers/users are stuck on IE6. We still see significant IE6 traffic coming from China. Some legacy clients are also stuck on SSLv3.

As a general rule, review your logs before disabling things. And ask your users to use modern browsers as soon as possible.

jvehent··on PostgreSQL Outperforms MongoDB in New Round of Tests
I have been using JSON types in postgres 9.3 for several weeks now. It's nice. It just works. I love being able to mix relational logic on static columns with undefined documents on dynamic columns, all in the same tables.
jvehent··on Everything you need to know about the Shellshock Bash bug
Thank you for that blog post. I managed to retrieve some of them and add a few attack vectors to my checklist: https://jve.linuxwall.info/blog/index.php?post/2014/09/25/Sh...

If you find any more of them, do you think you could publish their checksums?

jvehent··on Official Go support
So I'm gonna make a wild guess here and assume you haven't written in Go. If you had, you'd probably find it fun and convenient. Not revolutionary, just fun and convenient. That's enough for me to like it better than python or ruby or perl.
jvehent··on Need Postgresql HTTP API Extension
Sure, you can treat HTTP as a transport mechanism, which is what we've all been doing for the last 10 years because opening ports on firewalls sucks.

But HTTP is a resource manipulation mechanism: GET/POST/PUT/DELETE/... It's not optimized for transporting data.

Postgres, however, does provide a protocol that is optimized for transporting data [1]. It's also very simple to use, and full of thousands of features that are bug free. Which is why I find it odd to try to recreate a stable and efficient protocol into something less optimized, just so that a minority of developers can use http requests...

[1] http://www.postgresql.org/docs/current/static/protocol.html

jvehent··on Need Postgresql HTTP API Extension
At what point did HTTP and JSON become synonymous to Simple? Yes, a protocol and a data format can be convenient when applied to a specific problem, but that doesn't mean that everything should use them.

I've seen people refuse to use LDAP, and request a JSON (not rest) API instead, thus disregarding the security benefits of using a protocol that has 20 years of experience for dealing with access control and authentication.

Postgres has a tremendously powerful and efficient network protocol. There is great value in using and understanding it, because not every problem is a nail that can be hammered with a few GET requests.

jvehent··on Ask HN: Experienced dev having career lull
Don't work for the man. Work for mankind.
jvehent··on MDN Database Disclosure
A process failed, and the DB dump that is published to help contributors improve the MDN site got out unsanitized. The sanitization/publication process will be redesigned to include stricter controls. For now, it is shut down.

MDN has been using persona for a while now, meaning that most accounts don't have passwords in the database. But older accounts still had the SHA256 salted hash that Django creates.

We traced back as much as we could. Access logs, netflow data, etc... We found that the tar.gz containing the DB dump had been downloaded only a small number of times. Mostly by known contributors. But we can't rule out that someone with malicious intentions got access to it.

jvehent··on MDN Database Disclosure
It's useful to contributors who work on the site development.
jvehent··on MDN Database Disclosure
It's what django uses, and this site uses django.
jvehent··on MDN Database Disclosure
tldr: an automated data sanitization process failed, emails and salted hashed passwords were disclosed. no server was hacked.
jvehent··on Using SSL Certificates with HAProxy 1.5
See also https://wiki.mozilla.org/Security/Server_Side_TLS#Haproxy and https://jve.linuxwall.info/ressources/taf/haproxy-aws/
jvehent··on I made a patch for Mozilla, and you can do it too
C++, Javascript, Python... or Rust ! :)
jvehent··on $1.99 SSL certificates offered by Namecheap
http://startssl.com/ . $0/year. No bullshit.
jvehent··on Introducing Mozilla Winter of Security 2014
This is exactly what MWoS is about.
← PreviousPage 9 of 14Next →