Re: [Python-Dev] Other SSL issues in the tracker have been marked
apt-get install openssl will fix that on those systems. on windows you're unlikely to ever have an openssl binary present and available to execute. On 8/26/07, Bill Janssen <janssen@parc.com> wrote:
Now it looks as if both the Debian and Ubuntu failures are failing because they can't create a certificate, just like the Windows test. I'll go out on a limb here and guess that it's because "openssl" isn't on the path of the user running the tests.
That would also account for the other stack traces, if the keyfile or certfile didn't actually contain a key or a cert.
Bill _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/greg%40krypto.org
apt-get install openssl will fix that on those systems. on windows you're unlikely to ever have an openssl binary present and available to execute.
Well, if you have OpenSSL in the first place, you'll have the binary, won't you? But I agree it's unlikely to be on your path. As for Ubuntu and Debian, I checked the packaging, and they both put the "openssl" binary in /usr/bin, so it's unlikely to be a path problem. We could just build a fixed certificate and check it in, as the test_socket_ssl test does. That way we wouldn't have to futz with trying to run openssl. Bill
apt-get install openssl will fix that on those systems. on windows you're unlikely to ever have an openssl binary present and available to execute.
OTOH, having openssl(1) installed is not a prerequisite for Python buildbots currently, and IMO shouldn't be. Regards, Martin
participants (3)
-
"Martin v. Löwis" -
Bill Janssen -
Gregory P. Smith