HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

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

submissionscomments
jvehent··on MEGAChat now includes end-to-end encryption
> the scheme to accomplish this was rigorously vetted in a 12-day audit.

Vetted by whom? It would help build trust if there was a public report on the strength of your implementation available somewhere.

jvehent··on Ask HN: In a microservice architecture, how do you handle managing secrets?
I wrote some of my thoughts on the topic, and the primary motivation behind SOPS [1] (which uses PGP and KMS): https://jve.linuxwall.info/blog/index.php?post/2015/10/01/In...

The initial trust problem boils down to trusting the API that controls the provisioning of your infrastructure. Failing that, you have to ask a human to manually authorize new nodes to retrieve secrets (that's how puppet approves new agent certs).

[1] https://github.com/mozilla/sops

jvehent··on Parsing 10TB of Metadata, 26M Domain Names and 1.4M SSL Certs for $10 on AWS
I see you've reused the zscan DB schema. It's a good choice, we used it to inspire our schema too. We went a bit beyond because we also store ciphersuites (from cipherscan) and chains of trusts, so the DB schema had to be more relational than what zscan uses.
jvehent··on Parsing 10TB of Metadata, 26M Domain Names and 1.4M SSL Certs for $10 on AWS
The problem isn't so much exposing the data as a rest api, as it is allowing for complex queries that may contain various table joins, subqueries or recursive conditions. I only skimmed through the documentation of postgrest, but it doesn't make mention of joining tables, which is a deal breaker for our use case.
jvehent··on Get SSL Expiration Alerts with AWS Lambda and CloudWatch
That's fairly easy to do in a cron job:

    TARGET="mysite.example.net"; \
    RECIPIENT="hostmaster@mysite.example.net"; \
    DAYS=7; \
    echo "checking if $TARGET expires in less than $DAYS days"; \
    expirationdate=$(date -d "$(: | openssl s_client -connect $TARGET:443 -servername $TARGET 2>/dev/null \
                                  | openssl x509 -text \
                                  | grep 'Not After' \
                                  |awk '{print $4,$5,$7}')" '+%s'); \
    in7days=$(($(date +%s) + (86400*$DAYS))); \
    if [ $in7days -gt $expirationdate ]; then \
        echo "KO - Certificate for $TARGET expires in less than $DAYS days, on $(date -d @$expirationdate '+%Y-%m-%d')" \
        | mail -s "Certificate expiration warning for $TARGET" $RECIPIENT ; \
    else \
        echo "OK - Certificate expires on $expirationdate"; \
    fi;
jvehent··on Parsing 10TB of Metadata, 26M Domain Names and 1.4M SSL Certs for $10 on AWS
Exporting is one possibility, but eventually I'd like to provide a read-only sql access to the database we host. We have a few ideas on how to do this [1], but it's not implemented yet.

[1] https://github.com/mozilla/tls-observatory/issues/92

jvehent··on Parsing 10TB of Metadata, 26M Domain Names and 1.4M SSL Certs for $10 on AWS
Our dataset is not loaded from an external source, it is generated by scanners.

But to answer your question: yes, postgres can load data from csv files: http://stackoverflow.com/questions/2987433/how-to-import-csv...

jvehent··on Parsing 10TB of Metadata, 26M Domain Names and 1.4M SSL Certs for $10 on AWS
I have about the same amount of data in a Postgres database as part of the TLS Observatory project [1].

    observatory=> select count(distinct(sha256_fingerprint)) from certificates;
      count  
    ---------
     1239943

    observatory=> select count(distinct(target)) from scans;
      count  
    ---------
     6483386
The scanner evaluates both certificate and ciphersuites and stores the results in DB, so we can run complex analysis [2,3]. There is also have a public client [4].

I don't have a good way to provide direct access to the database yet, but if you're a researcher, ping me directly and we can figure something out.

[1] https://github.com/mozilla/tls-observatory

[2] https://twitter.com/jvehent/status/684127067005390848

[3] https://twitter.com/jvehent/status/686938805413232640

[4] https://twitter.com/jvehent/status/687429007680376833

jvehent··on Why I Write Games in C
Go has spoiled me for the past couple years.
jvehent··on Quiet naval hero who rescued Enigma machine dies aged 95
The serie Foyle's War has excellent details about the impact of the war on normal citizens of southeast UK. I grew up in Normandie, on the other side of the channel, and heard the same stories from my grand-parents.
jvehent··on Segway robot
I work remote. Most video conferences are great, except when too many people are in the same office and start talking to each other. Then audio quality goes down, and you can't place a word in the discussion.

I couldn't imagine using one of those robot to participate in a discussion with 15 people in the same room, and being the only remotee.

jvehent··on Man-In-the-Middle Interfering with Increased Security
The updates themselves are served over HTTP and signed, but the request that verifies an update is available is done over HTTPS.
jvehent··on Man-In-the-Middle Interfering with Increased Security
Setting security.pki.sha1_enforcement_level to 0 will still only accept SHA-1 certs that are signed by a root CA in the NSS truststore. That setting only disables the SHA-1 deprecation logic.
jvehent··on Man-In-the-Middle Interfering with Increased Security
For some background around the discovery and analysis of the issue, see this thread: https://groups.google.com/forum/#!topic/mozilla.dev.platform...
jvehent··on Jack Dorsey addresses Twitter's character limit
This should have been a blog post.
jvehent··on Postponing the Retirement of SHA-1
Ryan Sleevi, of the Chrome PKI team, has written a much more detailed analysis of the Cloudflare proposal and its caveats. I recommend you read them before voicing an opinion on this topic, because it is a complex one.

1. https://medium.com/@sleevi_/a-history-of-hard-choices-c1e1cc...

2. https://medium.com/@sleevi_/legacy-verified-legacy-solutions...

Today is the last day to get SHA-1 certs issued. We, at Mozilla, stocked up on SHA-1 certs that expire 39 months from now, so we can keep serving old clients up until March 2019 using cert switching technology. Most organizations that want to keep supporting old clients have done similar things. Smaller companies typically don't care about old clients, and most likely already broke compatibility with them by using various modern web stacks.

jvehent··on Yubico with new 4096-bit keys and gpg-agent for ssh authentication
My colleague Guillaume Destuynder wrote that blog post. We still use CryptoSticks at Mozilla, with sops[1] to securely store backup keys of some of our secrets files.

[1] https://github.com/mozilla/sops

jvehent··on Open Letter to Mozilla: Bring Back Persona
> In the event that Persona is decommissioned, we will provide at least 9 months of notice, so there are no actions that need to be taken right now. Persona continues to be monitored and supported, though there is still no new feature development.

I'm part of the team that runs the production service of Persona, and I can confirm it is operated, monitored and managed like any other critical production service today.

jvehent··on Open Letter to Mozilla: Bring Back Persona
There is an Apache module too: https://github.com/mozilla/mod_authnz_persona
jvehent··on GitLab 8.3 released with Auto-merge and GitLab Pages
AWS CodeCommit is another option.
jvehent··on SHA-1 Deprecation: No Browser Left Behind
Soon enough, modern browsers will deprecate SHA-1, rendering this attack mostly impossible.
jvehent··on Mozilla Wants To Split Off Its Thunderbird Email/Chat Client
> The best solution imo is to just let the community take over.

... which is exactly what is being proposed here, with financial help from the Mozilla Foundation to ease the transition.

jvehent··on Support for older versions of Internet Explorer ends on January 12, 2016
Microsoft not supporting older IE doesn't mean front-end people won't have to if their sites have users who don't upgrade.

It just means Microsoft can't be bothered to ship patches for those older browsers.

jvehent··on MIG: Search through your infrastructure in real-time from the command line
Well, it was a conference presentation... But if you prefer text, there is a pretty good overview at http://mig.mozilla.org ;)
jvehent··on MIG: Search through your infrastructure in real-time from the command line
MIG was started in 2013, and osquery did not exist back then. Even today, osquery does not provide a good way to remotely investigate your infrastructure, it's mostly a local-only tool (I know they are working on that now, but it's not a core feature).

GRR was and still is a very strong inspiration to MIG. I interact with the GRR team regularly, and we exchange ideas. GRR takes the approach of transferring all data from endpoints into central servers for analysis, which adds high bandwidth and storage costs. It's fine if you're Google and have tons and tons of storage, but we wanted to go with a lean approach for MIG, so we pushed the investigation to the agents, and only return results, never any raw data.

Not returning raw data has the added benefit of respecting the privacy of the endpoints being investigated, but also means that MIG is not your typical digital forensic imaging tool: it's a distributed search framework. If you want to take images of your systems, you need to do it via other means. (That said, we almost never need that capability).

jvehent··on MIG: Search through your infrastructure in real-time from the command line
Hi HN, I'm the lead dev of MIG and author of this presentation. We've been using it at Mozilla for over two years now, and it's proven to be very useful in our security effort. Happy to answer any questions you may have.

Also worth noting, there's a standalone install script at [1], and a deployment doc at [2].

[1] https://github.com/mozilla/mig/blob/master/tools/standalone_...

[2] http://mig.mozilla.org/doc/configuration.rst.html

jvehent··on Confidant: an open-source secret management service
An alternative approach, if you don't want to be 100% tied to KMS, is https://github.com/mozilla/sops . It uses KMS, but also PGP, and potentially anything that comes up in the future.
jvehent··on Your own Debian Mail Server (part II): how to prove you are not a spammer
Been doing it for 10 years, and it's still fun :) https://jve.linuxwall.info/blog/index.php?post/2015/03/11/10...
jvehent··on Full Speed Ahead with HTTP/2 on Google Cloud Platform
It's a poor workaround, but you can set your ELBs in TCP mode, and terminate TLS and HTTP/2 on the instances directly.
jvehent··on Wikipedia's TLS Cipher stats
And apparently des-cbc3-sha is still a thing...
← PreviousPage 6 of 14Next →