Reputation
17,367
Next tag badge:
68/100 score
24/20 answers
Badges
3 19 67
Impact
~287k people reached

Apr
4
comment For RSA keys, is the safety of a given key-length different for signing vs encryption?
@fgrieu Yeah, the use case and thread model should define the required key strength. But if the ciphertext is available to the entity that posesses the private key it is at least possible to upgrade the key strength by re-encrypting or adding another layer of encryption.
Apr
4
revised For RSA keys, is the safety of a given key-length different for signing vs encryption?
added 8 characters in body
Apr
4
revised For RSA keys, is the safety of a given key-length different for signing vs encryption?
added 8 characters in body
Apr
4
revised For RSA keys, is the safety of a given key-length different for signing vs encryption?
added 7 characters in body
Apr
4
answered For RSA keys, is the safety of a given key-length different for signing vs encryption?
Apr
3
comment Purpose of DES parity bits
@user1155120 At first I thought, wow, that's interesting. But the longer I think about it (with regards to usage scenarios) the more glad I am that they removed the parity bits from the AES requirements. Very interesting observation though.
Apr
3
comment Security implications of public nonce
@yyyyyyy What about converting your comments in an answer? dsd now has confirmation, but the question is still without answer.
Apr
3
comment Password-based encryption with small typos allowed
Two issues with this scheme: no work factor for the hash, and you'd better make sure the typo's don't overlap or you'll leak the key.
Apr
3
comment Purpose of DES parity bits
The intended purpose was already easily found in the DES Wikipedia article; fortunately the later question is somewhat more interesting.
Apr
3
answered Purpose of DES parity bits
Apr
2
revised What asymmetric key exchange algorithms are known besides DH?
edited title
Apr
1
comment Password-based encryption with small typos allowed
It's a pretty good paper, but I'm not 100% that it would be suitable for encryption schemes. Then again, "compatibility with existing password hash" could be an indication that it is possible.
Apr
1
comment Why is it a bad idea to use a UTF-8 derived symmetric key?
@MichaelJ.Gray HMAC is pretty resistant against abuse, even though it does recommend a key input the same size as the hash. I'd be more worried about the other software to use a different case for hexadecimals. Although there is an RFC, the use of uppercase or lowercase isn't really well standardized in practice.
Apr
1
revised About MAC and HMAC
formatting, removed "you should" etc. no semantical changes
Apr
1
comment Storing RSA private key
Pretty broad question probably without a single answer. I would recommend however to check which key stores are already present on the system. Zeroization is always a good idea, even though there are limits to what it can achieve on desktops. You don't want unused keys floating around.
Apr
1
revised Why need mapping to slots to embed bytes in AES-homomorphic encryption?
deleted 1 character in body; edited title
Apr
1
comment Why is it a bad idea to use a UTF-8 derived symmetric key?
I'm often telling people on StackOverflow that hexadecimals is just the human representation of the bytes. What you want to use is the actual value of the bytes. You can also put it in extremis and propose to use the binary (base 2) representation as key. Unless they're extremely daft they probably see the issue against using "00010010110001001000010100100010001001001010 (etc.)..." in ASCII.
Apr
1
comment Speed Up Twine Cipher for Java Card
Beside the off topic-ness, the Java Card API can be found on the internet. What's keeping you from looking up makeTransientByteArray yourself? Buy a book for starters, such as the venerable Java Card Technology for Smart Cards book. The principle ideas remain unchanged (unless you count the Connected Edition)
Apr
1
comment Speed Up Twine Cipher for Java Card
I'm voting to close this question as off-topic because this is a code review question.
Mar
31
revised Why is it a bad idea to use a UTF-8 derived symmetric key?
added 9 characters in body