Reputation
100,371
Next tag badge:
207/100 score
19/20 answers
Badges
13 158 279
Newest
 random
Impact
~3.1m people reached

Aug
31
comment what is the most secure hash for virus definition databases in 2015?
As long as we are talking about collisions, then the false positives would be against non-virus files specially crafted by the attacker itself, so the confusion would be rather limited. If the attacker could create collisions where one of the file is a pre-existing "normal" executable, then we would be talking about second preimages, which are a lot harder to build (even with MD5 we do not know how to do that).
Aug
31
answered Why should I choose SHA (such as SHa-512), instead of bcrypt or PBKDF2, for FIPS-compliance?
Aug
31
answered what is the most secure hash for virus definition databases in 2015?
Aug
27
awarded  Good Answer
Aug
27
awarded  Guru
Aug
26
awarded  Good Answer
Aug
20
awarded  Necromancer
Aug
19
awarded  Enlightened
Aug
19
awarded  Nice Answer
Aug
11
awarded  key-management
Aug
9
awarded  Enlightened
Aug
9
awarded  Nice Answer
Aug
7
answered Is a large encrypted file more secure than a small one?
Aug
7
comment Is HttpUtility.HtmlAttributeEncode considered for single-quotes attributes?
I think that the statement refers to the idea that they always intended the method to be used only for double-quoted arguments, but they added the escape for apostrophes nonetheless to help the poor sods that do not read documentation. They still don't want to claim support for single-quoted attributes, even though they kind-of added it surreptitiously. If you want to escape apostrophes explicitly, you can always do a String.Replace().
Aug
7
answered Is HttpUtility.HtmlAttributeEncode considered for single-quotes attributes?
Aug
7
awarded  Good Answer
Aug
6
awarded  Great Answer
Aug
5
answered Received email at work from someone using a member's name
Aug
5
answered TLS handshake encrypted alert on client certificate
Aug
5
comment What are requirements for HMAC secret key?
Let's be precise: with SHA-256, the output size is 256 bits, but the block size is 512 bits, so the "shortening" occurs only for keys of more than 512 bits. However, cryptographic keys (for symmetric algorithms like HMAC) longer than 128 bits don't really add security, so there is no actual need to go to a full block-length key.