jvehent

11 ms·

61.
Mercurial 4.3 and 4.2.3 released, fixes shell injection attack(mercurial-scm.org)
2 points by jvehent 9y ago|0 comments
62.
by jvehent 9y ago
Helping end users?
63.
by jvehent 9y ago
I have this laptop and run archlinux on it. It's a great machine, and almost everything works straight out of the box (even the external docking station).
64.
A Security Audit of Firefox Accounts(blog.mozilla.org)
4 points by jvehent 9y ago|0 comments
65.
by jvehent 9y ago
Slowly getting there, but they still have to wear pants...
66.
by jvehent 9y ago
I wrote https://github.com/mozilla/sops to manage secrets in our deployments, and also use it as my personal password store, to encrypt a file stored in a private git repo.
67.
Obama’s secret struggle to punish Russia for Putin’s election assault(washingtonpost.com)
4 points by jvehent 9y ago|0 comments
68.
Scanning APIs with ZAP(zaproxy.blogspot.com)
5 points by jvehent 9y ago|0 comments
69.
by jvehent 9y ago
> they don't seem to want to just rip-out Gecko and put Servo in there It's hard enough to change the wheels of a car while driving on the highway, you really don't want to do all four at once.
70.
by jvehent 9y ago
Your secret sauce is purely based on the hard work of open source developers. Pardon me if I don't support your obscurantism.
71.
by jvehent 9y ago
I doubt you rewrote a vulnerability scanner from scratch, since it takes years and a lot of efforts to do, so why don't you tell us a bit more about the technology behind it. Does it use ZAP? Arachni? W3AF? OpenVAS? SQLMap? All of them
72.
by jvehent 9y ago
It always depends on the vulnerability, but most major organizations are able to patch critical issues in less than 24 hours. That's the result of improving continuous integration and release engineering pipelines to the extreme. The r
73.
Mozilla Security Engineering Newsletter(wiki.mozilla.org)
4 points by jvehent 9y ago|0 comments
74.
by jvehent 10y ago
True infosec l33t$ know the only real certification is being able to recite from memory the lyrics of https://www.youtube.com/watch?v=FoUWHfh733Y
75.
by jvehent 10y ago
If your service has higher SLA requirements than your providers contractually committed to, you're doing something wrong.
76.
by jvehent 10y ago
In addition, it's really not that hard to add the equivalent of "apt update && apt -y upgrade && apt autoclean" to every dockerfile.
77.
by jvehent 10y ago
The story I heard from my data warehouse professor in college was that Walmart analyzed receipts of purchases made on saturdays, and noticed a strange correlation between diapers and cases of beer. A deeper analysis showed that fathers wher
78.
by jvehent 10y ago
It's present on mine under the paper plane icon: https://pageshot.net/tXxzW2A7XAhVuAGN/mail.google.com
79.
by jvehent 10y ago
The removal of XUL addons is scheduled for Firefox 57. https://blog.mozilla.org/addons/2017/02/16/the-road-to-firef...
80.
by jvehent 10y ago
> it will take years Yes. > if they start now We started last year with e10s, testpilot and dozens of other improvements.
81.
by jvehent 10y ago
> Enhanced Sync to allow users to send and open tabs from one device to another. If you haven't used this, try it out, it's a fantastic feature. I use it all the time to send a page I'm reading on my phone to my laptop, an
82.
How Firefox Sync keeps your secrets if TLS fails(medium.com)
2 points by jvehent 10y ago|0 comments
83.
by jvehent 10y ago
ASN.1 just called and wants it's encoding back...
84.
Sudo into a read-only file system(gist.github.com)
2 points by jvehent 10y ago|0 comments
85.
So Yeah We Tried Slack… and We Deeply Regretted It(medium.freecodecamp.com)
6 points by jvehent 10y ago|3 comments
86.
by jvehent 10y ago
"You may be tempted to use JWT instead of a database of session cookies. Please don't. Here's why: http://cryto.net/~joepie91/blog/attachments/jwt-flowchart.pn... " source: https:/&#
87.
by jvehent 10y ago
Too many comments here recommend to clean up the commit and just hide the mistake under the rug. This is wrong. If you leak a password to any public location, there is only one reasonable course of action: CHANGE IT! Don't even bother
88.
by jvehent 10y ago
> Just using a random commit name like 'minor bug fix', 'updated version' for these kind of commits will save a lot of headaches like this. Just change the leaked passwords, don't try to hide the commits.
89.
by jvehent 10y ago
These HTTP clients are all very cool, and probably fun pet projects, but they shouldn't stop devs from learning as much cUrl as they can. It's the Swiss army knife of web services.
90.
by jvehent 10y ago
The time to take a stand was a year ago, before the (albeit flawed) democratic process elected a president you now disagree with.

More ›