Great! Glad to hear it is working. Apache conf file can be a haunting task if we try new things as never before.
"Wendy Reetz" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] AHAH! Thank you for your help. You mentioned that the private key was missing. I didn't realize I was generating a private key! (ok, I'm not new to php, but definitely new to the whole system configuration, apache, ssl side of things). So, in looking into that I found that I hadn't restarted apache in ssl mode, when I tried I found that failed with the same error. added some missing directives to the conf file & it started right up & is working great! Thank you for the point in the right direction! Wendy "Scott Fletcher" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Try "https://"; instead of "ssl://", this is what is normally done. > > As for your problem. It look like the private key when generated was too > short, this can be overcomed by entering more characters at the time of the > generation of hte key. But from your comments, you mentioned that from the > article at OpenSSL that it either not exist or is too short and that you > mentioned that you have both. So, if this is the case, then it seem that it > had nothing to do with being too short. Just that there is no key, so that > in turn is too short because it isn't there. > > I don't have an idea of what is going on. > > "Wendy Reetz" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > Using php 4.3.2, apache 1.3.27, openssl .9.7b > > I'm trying to open a secure connection using fsockopen("ssl://"...,443...) > as described in http://us4.php.net/manual/en/function.fsockopen.php. > > I keep getting an error: PRNG not seeded. > OpenSSL says http://www.openssl.org/support/faq.html#USER1 says: > If the default seeding file [/dev/random or /dev/urandom] does not exist or > is too short, the "PRNG not seeded" error message may occur. > Now, both of these exist, but I'm not sure how to tell if they are too > short... > > has anyone used fsockopen("ssl://"...) successfully? I've read through the > php site, apache, and openssl...but I'm not finding a solution. Is there > something that may have been overlooked when the 3 were compiled? Do you > need to create a certificate? > > The answer may be staring me right in the face & I'm just not seeing it.Any > point in the right direction would be appreciated. > > Thanks, > > Wendy > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
