Thanks, that makes perfect sense.
-Robert
Mounir IDRASSI wrote:
Hi,
This is normal since the RSA private key is in the Chinese Remainder
format ( p, q, dp, dq and d). The first four elements have half the size
of the moduluse and the last has the same size as the modulus. Thus, the
I noticed that using RSA with OpenSSL places a 117 character limit when
encrypting messages. Would anyone happen to know the reason for this?
Thanks,
--
View this message in context:
http://www.nabble.com/117-Character-Limit-tp16291750p16291750.html
Sent from the OpenSSL - Dev mailing list
The SSL_set_fd and SSL_get_fd take an int as parameter for the socket.
While this was fine on windows 32 bit and on all *nix variants (even 64
bit), this is not fine anymore on Windows 64 bit.
I hope this can be fixed. Because a SOCKET on windows 64 bit is a
UINT_PTR which is 64 bit while an
robert2007 wrote:
I noticed that using RSA with OpenSSL places a 117 character limit when
encrypting messages. Would anyone happen to know the reason for this?
1) It doesn't
2) Do you mean with a 1024-bit modulus the encryption block size
is 936? Because of padding.
If one were to Wiki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Sierchio wrote:
| robert2007 wrote:
| I noticed that using RSA with OpenSSL places a 117 character limit when
| encrypting messages. Would anyone happen to know the reason for this?
|
| 1) It doesn't
|
| 2) Do you mean with a 1024-bit
Goetz Babin-Ebell wrote:
RSA has some weaknesses against chosen plain text attacks.
RSA is just an algorithm, so if you talk of chosen plaintext
or chosen ciphertext attacks, it needs to be in the context
of an encryption method. OAEP is a response primarily to
a chosen ciphertext
