HNHacker News
TopNewBestAskShowJobs

jvehent

3,020 karma · joined March 15, 2010

https://jvehent.org

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

submissionscomments
jvehent··on What It Costs to Run Let's Encrypt
Have you tried writing that code from scratch without any libraries?
jvehent··on The Marriage of DevOps and SecOps
I couldn't agree more. At Mozilla, the Services Security team is part of the team that develops and builds services. We work with devs and ops every day. We write application and infrastructure code. We share successes and failures.

The traditional bystander/compliance security team approach shows its limits very quickly. Being embedded that deeply into the DevOps team is by far the most efficient way to secure services.

jvehent··on The Marriage of DevOps and SecOps
I'm not a fan of the "DevSecOps" or "SecDevOps" terms. Security is just part of DevOps, the same way QA or product management are. It's not its own thing bolted on top of DevOps practices, it's an integral part of the product.

That said, I agree with the blog post. We are seeing more and more security teams reinvent themselves as they adopt DevOps practices, which really means security is learning to use the CI/CD pipeline and to build controls in IaaS and PaaS. We're moving away from security teams that panicked at the idea of not controlling layer 2 and 3, like they used to in the goold old datacenter, and seeing teams focus on web application security more and more.

It doesn't mean L2/3 are not important. There is still a lot of value to adding an IDS or a proxy to an infrastructure. But there is also tremendous value in testing controls continuously in the delivery pipeline, which means collaborating with devs and ops in the CI/CD pipeline. That's really what "secdevops" is about.

In the next few years, we'll see more and more security teams learn DevOps and that's a good thing. Let's just make sure we don't reinvent decades of infrastructure security in the process.

(shameless plug: I'm writing a book on devops security: https://securing-devops.com/book)

jvehent··on HTTP Observatory: analyze your website and review available methods to secure it
You need https to guarantee data in transit is not being modified between your server and web clients. ISPs, for instance, have a bad tendency to inject tracking cookies in http traffic.
jvehent··on HTTP Observatory: analyze your website and review available methods to secure it
Direct link to the live Observatory: https://observatory.mozilla.org/

Example run on addons.mozilla.org: https://observatory.mozilla.org/analyze.html?host=addons.moz...

The Observatory measures site's compliance with the Web Security guidelines [1] and the Server Side TLS guidelines [2]. It's primarily meant as a helper for website developers and operators.

[1] https://wiki.mozilla.org/Security/Guidelines/Web_Security

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

(disclaimer: I work on security at Mozilla)

jvehent··on Mutt 1.7.0 released
Many people try to switch to Mutt thinking it will be like using gmail but in the terminal. It is not.

Mutt is a productivity tool, like vim and emacs, but for email instead of code. You need to invest a lot of time into learning it, refining your configuration, and getting comfortable with its interface. It will originally be as frustrating as giving emacs to a notepad user, but eventually pays off the learning cost in productivity.

Some examples of commands I use all the time:

* shift+D deletes an entire thread. Very useful to delete entire github discussions in one command.

* `t` flags a message, then `;+s` moves the entire flag to another folder

* custom macros. For example, I use `short+C` to move the message under the cursor to folder `foo`. I have 5/6 similar macros for the folders I use most.

GnuPG integration is also a big help (I use it constantly). I'm use many other MUA offer similar shortcuts and configurability, but Mutt is the fastest and most flexible by far. The one thing that I haven't found a good solution for is full text search across multiple folders. I still rely on gmail for that.

jvehent··on What Do Public Library Workers Do? (2011)
Unless you're poor. Then you don't have a computer.
jvehent··on Bitcoin 0.13.0 Binary Safety Warning
bitcoin.org does not implement HPKP. Any government that controls a CA can generate its own cert for bitcoin.org, hijack the site's IP and replace this page with their own fingerprint.
jvehent··on Why We Moved from Amazon Web Services to Google Cloud Platform
Does anyone have feedback running app at scale in Google Cloud for more than one year?
jvehent··on Why aren’t we using SSH for everything?
This technique assumes the operator is OK with taking a few weeks for all users to register the new host key. In the event of a leak, revocation of the leaked key must be immediate. That's why we have CRLs (and OneCRL) and OCSP.
jvehent··on Why aren’t we using SSH for everything?
No. I said that changing the key, which must happen, will trigger a warning that will scare users away. Which is (partly) why no one uses SSH with non technical populations.
jvehent··on Why aren’t we using SSH for everything?
You're missing the point: SSH does not provide a host key rotation/revocation mechanism. TLS does.
jvehent··on Why aren’t we using SSH for everything?
> Why aren’t we using SSH for everything?

Because when you have 100,000 users and you need to rotate your host key following a leak, the team in charge of user retention has a heart attack.

jvehent··on Server Side TLS
If you want to contribute to this page, or the config generator [1] that goes with it, check out its repository on github: https://github.com/mozilla/server-side-tls

[1] https://mozilla.github.io/server-side-tls/ssl-config-generat...

jvehent··on Ask HN: Who is hiring? (August 2016)
Firefox Services Security Engineer | Mozilla | Remote (GMT-4 to GMT-9)

Mozilla’s Services Security Team is looking for an ambitious Security Engineer to help us protect the back-end services that power Firefox and serve millions of users worldwide.

Role:

* develop, implement and operate controls to secure online services and web APIs

* Assist developers in auditing and hardening the security of web applications

* Implement techniques to detect and block abuses of our services

* Advocate security across the organization, be a teacher for security.

See the job listing: https://careers.mozilla.org/position/oQ1k3fwY

jvehent··on Go Packaging Proposal Process
Godoc is searchable: https://godoc.org/?q=json+web+token
jvehent··on Go Packaging Proposal Process
I have not looked into this.

The S3 method is kinda experimental. It works for first-level packages but fails for nested packages. We need to look into setting up redirects for those.

The best way to do this yourself is to run an instance of https://github.com/niemeyer/gopkg, but that's not #serverless anymore ;)

jvehent··on Go Packaging Proposal Process
Projects I care about use a domain I control. It's not that hard to setup: https://jve.linuxwall.info/blog/index.php?post/2015/08/26/Ho...

We even do it with just an S3 bucket for go.mozilla.org: https://go.mozilla.org/

jvehent··on My Interviews with Amazon
And this is why remote work for tech people is the future.

Timezones are still an issue, but if you're willing to adapt your work hours to meet the majority, being remote allows you to work for fantastic companies without sacrificing your way of life.

jvehent··on ISRG (Let's Encrypt) Root X1 Inclusion in NSS
Let's Encrypt currently uses a cross-signature provided by Identrust that expires in 2021. This inclusion is the first step toward making Let's Encrypt completely autonomous.
jvehent··on Native encryption added to ZFS on Linux
That is a terrifying amount of crypto code. Has anyone audited this, or plan to?
jvehent··on Show HN: Dependency CI – Continuous testing for your dependencies
Similar to Greenkeeper or requires.io, but with a larger range of languages supported. Very interesting.

As a side note, I recommend creating a separate github account when granting permission to this kind of 3rd party. Don't grant them full read/write on your repos, create an account that's temporarily admin, then make that account read only.

jvehent··on Mozilla could walk away from Yahoo deal and get more than $1B
and also influence policies that protect the Internet or support hundreds of local communities that teach the web worldwide [1]

[1] https://www.mozilla.org/en-US/contact/communities/

jvehent··on Facebook Does Not Use Your Phone’s Microphone for Ads or News Feed Stories
Let me fix that for you: "Facebook Does Not [yet] Use Your Phone’s Microphone for Ads or News Feed Stories"
jvehent··on Multiple assignees on Issues and Pull requests
The best way to make sure something never gets done is to share ownership of it.
jvehent··on Achieving a Perfect SSL Labs Score with Go
Neither should they. Both guides haves different goals.

SSLLabs evaluates the highest possible security, while Mozilla's levels compromise to implement the best possible TLS for a given population of users. "best" isn't always determined by security: speed and compatibility are taken into account as well.

That said, Mozilla's modern level ranks A+ in SSLLabs: https://www.ssllabs.com/ssltest/analyze.html?d=jve.linuxwall...

jvehent··on Achieving a Perfect SSL Labs Score with Go
We also recommend AES-256 being preferred to AES-128 in Mozilla's modern configuration. From the rationale section:

    AES256-GCM is prioritized above its 128 bits variant,
    and ChaCha20 because we assume that most modern devices 
    support AESNI instructions and thus benefit from fast 
    and constant time AES.
https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_com...
jvehent··on Push.js – A minimalist JavaScript library for desktop notifications
See also https://hacks.mozilla.org/2016/01/web-push-arrives-in-firefo...

WebPush is (going to be) an IETF standard: https://datatracker.ietf.org/wg/webpush/documents/

jvehent··on SSL Labs in 2016 and Beyond
Ivan Ristic has done a remarkable service to the Internet with SSLLabs and ModSecurity, and he has done so with a fantastically positive attitude all throughout. Thank you Ivan, I'll be curious to see what you come up with next ;)
jvehent··on Mr. Robot Blind SQL Injection Vulnerability
Sites operators should reward responsible disclosure, not get researchers into trouble. Bug bounties are a good way to do that. Unfortunately, there are still people out there who don't understand their true value.
← PreviousPage 4 of 14Next →