178 reputation
5
bio website
location
age
visits member for 1 year, 6 months
seen Aug 18 at 16:11

Dec
16
comment Unit testing a library RNG and its seeding for practical security
Does any one know if people actually do run collision tests to identify badly seeded CSPRNGs? And in particular, anything I can cite?
Sep
26
comment Is it possible to make time-locked encrytion algorithm?
That is really cool. I take it that elliptic curve cryptography can be used in place of El Gamal throughout. (Though I don't fully grok the VSS mechanism, so I'm not certain that that carries over, but I think it does.)
Sep
26
comment What is the security loss from reducing Rijndael to 128 bits block size from 256 bits?
Changing a widely adopted standard is not something to do lightly. And there hasn't been a lot of demand to revise or develop a new standard, probably because under proper usage, related key attacks are irrelevant.
Sep
24
comment Reusing keys with AES-CBC
I think a quick way to summarize this is: reusing a key/IV with CBC is bad. Reusing a key/nonce with CTR is catastrophic.
Sep
9
comment Which PRNG security requirements do I need for key generation
KDF is way to go. Hardware device isn't a workable for this application. This is a consumer product. We can't expect end users to each have HW RNGs.
Sep
8
comment Which PRNG security requirements do I need for key generation
The scheme we use is publicly known and well documented. I was not intending to rely its secrecy in any way. Only need small volume. I will update my question to clarify what threats I'm worried about.
Aug
26
comment Is there a public key encryption scheme with optimal key size?
Fair points, @fgrieu. "Understanding Cryptography" does not teach about the security notions (e.g., PTXT-IND, CTXT-MAL, etc) needed to understand a lot of the crypto literature. But I found it an excellent introduction to the algorithms and to the basic protocols.