jvehent

34 ms·

301.
by jvehent 12y ago
Idiomatic. http://www.merriam-webster.com/dictionary/idiomatic
302.
by jvehent 12y ago
That's a cool project. Performance is a fascinating topic. However, in the real world, the number of requests per second a http daemon can perform is the last thing to worry about. If the web is slow, it's not because Apache used
303.
by jvehent 12y ago
I've been using this driver heavily for about 9 months now, and it has served me flawlessly so far. Definitely recommended!
304.
Generate Secure Configuration with `sslmate mkconfig`(sslmate.com)
3 points by jvehent 12y ago|0 comments
305.
SoakSoak: Payload Analysis – Evolution of Compromised Sites – IE 11(blog.sucuri.net)
1 points by jvehent 12y ago|0 comments
306.
Stripe's AWS-Go and uploading to S3(jve.linuxwall.info)
1 points by jvehent 12y ago|0 comments
307.
by jvehent 12y ago
And comments! Reputation is critical for services, those 5 stars are going to become very important to business owners.
308.
go iOS.App()(groups.google.com)
3 points by jvehent 12y ago|0 comments
309.
by jvehent 12y ago
If what you want is a minimalistic browser, don't run a JVM, use elinks! It even has colors: http://4u.1nw.eu/elinks_hn.png
310.
SSL/TLS for the Pragmatic(jve.linuxwall.info)
1 points by jvehent 12y ago|0 comments
311.
by jvehent 12y ago
I prefer HTML & CSS, maybe with something like restructuredText on top.
312.
by jvehent 12y ago
Do you have to maintain backward compatibility with Windows XP pre-SP3 for gov sites? That would require SHA-1 certs and SSLv3.
313.
by jvehent 12y ago
> If you're not big enough, then it probably doesn't affect you anyway. How so?
314.
by jvehent 12y ago
...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
315.
by jvehent 12y ago
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/mast
316.
by jvehent 12y ago
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.
317.
by jvehent 12y ago
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!
318.
by jvehent 12y ago
In my opinion, Firefox for android is vastly superior to chrome.
319.
by jvehent 12y ago
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 fo
320.
by jvehent 12y ago
"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
321.
TLS scan results for October 2014(securitypitfalls.wordpress.com)
4 points by jvehent 12y ago|1 comments
322.
by jvehent 12y ago
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
323.
by jvehent 12y ago
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
324.
by jvehent 12y ago
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!
325.
by jvehent 12y ago
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
326.
Mitigating Poodle SSLv3 Vulnerability on a Go Server(jve.linuxwall.info)
1 points by jvehent 12y ago|0 comments
327.
Mozilla Server Side TLS Guidelines(wiki.mozilla.org)
2 points by jvehent 12y ago|0 comments
328.
by jvehent 12y ago
I'm assuming that a user stuck on IE6 doesn't have the necessary technical expertise to upgrade or change security parameters.
329.
by jvehent 12y ago
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
330.
Automated configuration analysis for Mozilla's TLS guidelines(jve.linuxwall.info)
3 points by jvehent 12y ago|0 comments

More ›