Reputation
1,684
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
2 10 20
Newest
 Yearling
Impact
~61k people reached

Dec
19
awarded  Yearling
Dec
15
reviewed Approve Lightweight Asymmetric encryption algorithm
Dec
11
awarded  Famous Question
Nov
14
awarded  Nice Question
Nov
6
comment Is this a correct way of use symmetric encryption?
A more standard (and safe) approach would be to calculate a hmac of the ciphertext with an independent key. Or, use authenticated encryption en.wikipedia.org/wiki/Authenticated_encryption
Oct
30
awarded  Custodian
Oct
30
reviewed Approve A self-decrypting block-cipher
Oct
25
awarded  Notable Question
Jun
25
comment Why is the public/private key length used in libsodium so much shorter than needed for RSA
"For libsodium, the main problem is taking discrete logarithms"... libsodium (github.com/jedisct1/libsodium) is a cryptographic library which uses many primitives including (but not limited to) authenticated symmetric encryption, key agreement, public-key signatures, and key derivation. Do you mean Curve25519?
Jun
25
comment Why is the public/private key length used in libsodium so much shorter than needed for RSA
libsodium uses curve25519, which is based on elliptic curve cryptography — it is an entirely different algorithm to RSA (and yes , ECC key sizes are much smaller... see here for a reference... linuxjournal.com/content/elliptic-curve-cryptography). Aside from that, your question is broad - you should do some reading.
Jun
23
awarded  Caucus
Mar
13
awarded  Notable Question
Feb
2
awarded  Notable Question
Jan
21
comment HMAC-Ripemd-160 in TrueCrypt
Personally, in 2015, I wouldn't feel comfortable with anything less than 100'000 pbkdf2 iterations as a baseline, but a million would be preferable. Using something like Scrypt is better still. Of course, if you have a sufficiently strong password, then 3000 iterations of Ripemd-160 is fine.
Jan
7
comment NTRU key generation
@CodesInChaos - I'm not sure where that number comes from, but it's also mentioned in the documentation: github.com/NTRUOpenSourceProject/ntru-crypto/blob/master/…
Jan
5
comment NTRU key generation
+1 - thanks! I accepted the other answer because it also addressed the other doubt I had
Jan
5
comment NTRU key generation
Very succinct - thanks!
Jan
5
accepted NTRU key generation
Jan
5
comment NTRU key generation
1718 bytes. To illustrate further, here is a pastebin of sample public and private keys (obviously they're not production keys)
Jan
5
comment NTRU key generation
The string above is just to illustrate the repetition of zeros towards the end of a much larger (and seemingly pseudorandom) key. The key itself is 1718 bytes. As for the representation - I'm not sure how to answer. I'm just using the API - (ntru_crypto_ntru_encrypt_keygen) provided in the implementation, it returns the private key as a byte array (uint8_t).