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 <[EMAIL PROTECTED]> 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 >
_______________________________________________ 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/archive%40mail-archive.com
