[Python-Dev] Other SSL issues in the tracker have been marked

Gregory P. Smith greg at krypto.org
Mon Aug 27 18:09:18 CEST 2007

nope, not on many package based distributions.  libssl0.9.8, libssl-dev and
openssl are all separate packages (with appropriate dependencies).
/usr/bin/openssl comes from the openssl package.

Regardless, building a fixed test certificate and checking it in sounds like
the better option.  Then the openssl command in the test code can be turned
into a comment describing how the test data was pregenerated.

On 8/27/07, Bill Janssen <janssen at parc.com> wrote:
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20070827/9e57d76d/attachment.htm 

More information about the Python-Dev mailing list