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.<br><br>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.
<br><br><div><span class="gmail_quote">On 8/27/07, <b class="gmail_sendername">Bill Janssen</b> <<a href="mailto:janssen@parc.com">janssen@parc.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> apt-get install openssl will fix that on those systems. on windows you're<br>> unlikely to ever have an openssl binary present and available to execute.<br><br>Well, if you have OpenSSL in the first place, you'll have the binary,
<br>won't you? But I agree it's unlikely to be on your path. As for Ubuntu<br>and Debian, I checked the packaging, and they both put the "openssl" binary<br>in /usr/bin, so it's unlikely to be a path problem.
<br><br>We could just build a fixed certificate and check it in, as the test_socket_ssl<br>test does. That way we wouldn't have to futz with trying to run openssl.<br><br>Bill<br></blockquote></div><br>