jvehent

39 ms·

361.
by jvehent 13y ago
No problem here with Fedora 20 and Firefox 31.0a1 (2014-04-04)
362.
by jvehent 13y ago
"Our clients send base64 encoded JSON objects to our edge server using HTTP GETs." Encoded json in get parameters? That's not what GET requests are for. use POST requests for that, or you'll quickly be limited by the max
363.
Firefox comes out as gay, new Mozilla CEO resigns(oddshocks.com)
2 points by jvehent 13y ago|0 comments
364.
by jvehent 13y ago
This is cool, and as a heavy IRC user, I'm eager to find a solution that can replace self-hosted IRSSI+ZNC entirely, without compromising security. Don't reinvent the protocol, reinvent the UI.
365.
by jvehent 13y ago
I saved 15 minutes by not reading this blog post :)
366.
by jvehent 13y ago
No. MozDef analyzes logs and events that are shipped to its data pipeline by servers and applications.
367.
by jvehent 13y ago
protip: nagios.
368.
Heka v0.5 Released(blog.mozilla.org)
8 points by jvehent 13y ago|0 comments
369.
by jvehent 13y ago
Firefox is not vulnerable to this.
370.
by jvehent 13y ago
Happy rollback when it breaks ;)
371.
by jvehent 13y ago
If you are still asking yourself that question, I strongly recommend you read this book: http://restfulwebapis.com/
372.
MWC 2014 The Mozilla Booth(youtube.com)
2 points by jvehent 13y ago|0 comments
373.
Russ Allbery's perspective on the Debian technical committee impasse(lwn.net)
3 points by jvehent 13y ago|0 comments
374.
by jvehent 13y ago
afaik, webrtc uses srtp, which is a separate from https.
375.
by jvehent 13y ago
I agree. Unfortunately, there is currently no way to configure different ciphersuites for different versions of TLS. With issues like BEAST, it would be highly beneficial if Apache, Nginx & others would supports ciphers preferences per
376.
by jvehent 13y ago
That's an interesting piece of information! Thank you for sharing it.
377.
by jvehent 13y ago
Chrome and Firefox (among many others) use NSS, which accepts patches ;)
378.
by jvehent 13y ago
You mean this? https://wiki.mozilla.org/Security/Server_Side_TLS#Apache
379.
SSL/TLS analysis of the Internet's top 1,000,000 websites(jve.linuxwall.info)
63 points by jvehent 13y ago|11 comments
380.
by jvehent 13y ago
That's a good beginners guide. To take it a step further, check out the documentation that we maintain at Mozilla: https://wiki.mozilla.org/Security/Server_Side_TLS
381.
by jvehent 13y ago
Fantastic lecture indeed, and very well delivered!
382.
by jvehent 13y ago
Is ctrl+ really that hard to do?
383.
by jvehent 13y ago
If you are root, you can also strace the process and grab the password, without modifying anything. If the platform isn't secure, the app can't be trusted. Basic defense rule.
384.
by jvehent 13y ago
I wrote something similar, that uses Postfix, Dovecot, OpenLDAP, Roundcube, DSPAM and OpenDKIM. http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:n... I presented it at my local LUG a while back, here are the
385.
Navigating the TLS landscape(blog.mozilla.org)
3 points by jvehent 13y ago|0 comments
386.
Telefónica Vivo Launches Firefox OS Smartphones in Brazil(blog.mozilla.org)
1 points by jvehent 13y ago|0 comments
387.
Firefox OS on the LG Fireweb(youtube.com)
3 points by jvehent 13y ago|0 comments
388.
by jvehent 13y ago
Nginx has a patch to store them in memcache, for what it's worth. It's far from ideal, but at least it's not persistent storage. The standard is still to point clients to a single termination endpoint, and do active/pass
389.
by jvehent 13y ago
Not yet, but we plan to add a correspondence table between OpenSSL and GnuTLS. Any contribution is most welcomed.
390.
by jvehent 13y ago
We don't control what the client enables. Any client could decide tomorrow to disable AES-128, and we need to support that. The ciphersuite focuses on ordering ciphers by strength and performance, and we don't just disable cipher

More ›