valyala

53 ms·

601.
Elliptic curve cryptography is vulnerable to remote timing attack(kb.cert.org)
2 points by valyala 15y ago|0 comments
602.
How to protect your business from 'Getting hit by a bus' problem(answers.onstartups.com)
1 points by valyala 15y ago|0 comments
603.
Mozilla rejects Google's WebP image format(arstechnica.com)
45 points by valyala 15y ago|28 comments
604.
by valyala 15y ago
Part 2 is already available - see http://lwn.net/Articles/443775/
605.
by valyala 15y ago
Zynga knows how to use properly cloud-based hosting :) lwn.net recently published an article about scalability with similar suggestion in the 'Cloud Addiction' chapter - http://lwn.net/Articles/443775/ .
606.
by valyala 15y ago
Perhaps, (this.lastIndexOf(s, 0) === 0) will work faster for startsWith(s), because it doesn't create new string just for the sole purpose of using it in a single comparison. What if s contains 1M 'a' chars, while this contains 1M 'b' chars
607.
Major sites are still unpatched against the 1.5 YO TLS renego vulnerability(my.opera.com)
1 points by valyala 15y ago|0 comments
608.
by valyala 15y ago
OK. How this prevents from man-in-the-middle attack on public keys sent over untrusted network? Can you point me to the description of the protocol aimed against man-in-the-middle attack during long term public keys' distribution? Let's say
609.
by valyala 15y ago
IE9 also had this bug, but it has been fixed - see http://code.google.com/p/chromium/issues/detail?id=36142#c53
610.
by valyala 15y ago
IE6 and FF 3.6 aren't modern browsers :)
611.
by valyala 15y ago
It looks like the first was IE9 - see http://code.google.com/p/chromium/issues/detail?id=36142#c53 . Chrome doesn't fix the related bug for more than a year - http://code.google.com/p/chromium/issues/detail?id=36142 . Safari wins with m
612.
by valyala 15y ago
It is OK to have in-memory cache for certain resources. It isn't OK when this cache doesn't shrink under memory pressure. This usually leads to swap trashing after the cache becomes bigger than the available physical RAM on the system. Swap
613.
by valyala 15y ago
Nice. I couldn't find the description on how long-term public keys' sharing will avoid man-in-the-middle attack. It's unclear how clients will obtain long-term public keys from new servers and how servers will obtain long-term public keys f
614.
All modern web-browsers except IE9 are vulnerable to a huge memory leak(code.google.com)
151 points by valyala 15y ago|65 comments