Problem porting from OpenSSL 0.9.7e to 0.9.8

Hello All, I used OpenSSL 0.9.7e on Tru64 Unix 5.1A.I could generate the Certificate even without /dev/random or /dev/urandom Or EGD daemons. But now I am using OpenSSL 0.9.8 in the same environment and I am getting an error PRNG not seeded. I would like to know if any changes have been done in

X509_NAME_get_text_by_NID fails with accent?

Hello I have a problem with the function X509_NAME_get_text_by_NID. To get the last name of the subject of a certificate I use this call: i = X509_NAME_get_text_by_NID(X509_get_subject_name(x), NID_givenName, buf, lenbuf); usually it works fine but with this certificate (see the attachment)

Re: X509_NAME_get_text_by_NID fails with accent?

Massimo Rando [EMAIL PROTECTED] writes: The function returns: i = 6 buf (hex) = 4d 61 72 69 c3 b2 but the buffer 'buf' should contain the given name 'Mariò' (hex: 4d 61 72 69 f2) while I find the string Mariò (hex: 4d 61 72 69 c3 b2). ò in UTF-8 is 0xc3 0xb2. ò in ISO-8859-1 is 0xf2. I

Re: building openssl0.9.8a fails

I found the cause of evil. The error message (see original post) refers to /usr/local/include/unistd.h. I found it peculiar that the build would use headers that are in /usr/local/... Looking further, I found that there are more copies of unistd.h around, which all reside under /usr/include,

Re: How to encrypt a large file by a public key?

Just curious: Putting speed aside, what is the security risk by encrypting a large file chunk by chunk using RSA public key? (e.g. using chain mode like what is done in symmetric block cipher) On 12/14/05, Amir (sent by Nabble.com) [EMAIL PROTECTED] wrote: Thank you for your reply, I do

Re: How to encrypt a large file by a public key?

On Tue, Dec 20, 2005 at 10:48:57AM -0500, [EMAIL PROTECTED] wrote: Just curious: Putting speed aside, what is the security risk by encrypting a large file chunk by chunk using RSA public key? (e.g. using chain mode like what is done in symmetric block cipher) RSA is not intended for

Re: How do I correctly handle SSL_shutdown?

I think I understand but I still seem to have an issue with my code. 1). Server opens an SSL port for a client to connect to 2). Client connects to this port and SSL_read and Write stuff. 3). Client Calls SSL_shutdown( sslSocket ); 4). Server Calls SSL_get_shutdown( sslSocket ), If shutdown is

(export control) AES 128 bit

I would like to implement a C++ program that will use openssl to encrypt packets using AES 128 bit key. However, the problem is that I live in the US. Does this mean that I will be breaking the export control law if I put the program on a server for others to download? I have look at

secure code guidance

Hi Team, This might be dev topic, but let me ask. Is there any coding guidance for the core team and application developer? Is anybody doing the source code review like open bsd team does for their code? Thanks! With Best Regards, Kiyoshi Kiyoshi Watanabe

Re: (export control) AES 128 bit

Dudue Doo wrote: I would like to implement a C++ program that will use openssl to encrypt packets using AES 128 bit key. However, the problem is that I live in the US. Does this mean that I will be breaking the export control law if I put the program on a server for others to download? I

Re: How do I correctly handle SSL_shutdown?

If the server is unable to see the SSL_RECEIVED_SHUTDOWN, then probably the close notify did not go on the wire, i.e client failed sending it? Can you check the wire to see if it actually went out? Try calling ssl_get_error to see the status on the error queue. Also by any chance have you set the

rsa certificate and private key question

dear all: by using the following openssl cli, i generate a rsa private key key and a self signed certificate file. $ openssl genrsa -out key.pem 1024 $ openssl req -new -key key.pem -out request.pem $ openssl x509 -req -days 30 -in request.pem -signkey key.pem -out certificate.pem when i try