On Mon, Dec 31, 2012 at 11:39 AM, Jeffrey Walton noloa...@gmail.com wrote:
On Sun, Dec 30, 2012 at 3:20 PM, jb-open...@wisemo.com wrote:
On 30-12-2012 21:01, Jeffrey Walton wrote:
Hi All,
While working on Apple with Mac OS X and iOS, I found I needed to
patch OpenSSL 1.0.1c's Makefile.
I had changed my hostname for the system, and that does not produce a
new localhost.crt, so the message was from this cert content and the
ssl.conf reference to the localhost.crt Grumble, Grumble.
As for the '/' in the report of cert content, this seems to be a 'bug'
in how the DN is
I'm trying to extend the list of certifictaes (the default CA bundle)
OpenSSL and OpenSSL-aware apps trust to include out Enterprise root
cert.
This is on a RHEL 5.x machine (0.9.8e plus backported RH patches).
From reading, it seems like the proper way to do this is either to
append the cert to
|On Mon, Dec 31, 2012 at 1:58 PM, Walter H. walte...@mathemainzel.info \
|wrote:
| Hello,
|
| why does the following makefile not succeed?
|
| ...
| I have isolated the problem:
|
| openssl crl -noout -text -in $ $@
| exits with exit code 1 instead of 0, why?
|
| openssl crl -noout
From: owner-openssl-us...@openssl.org On Behalf Of Robert Moskowitz
Sent: Monday, 31 December, 2012 17:02
I am running on Centos 6.3 where it looks like Openssl is 1.0.0-25
I am creating my cert with:
openssl req -new -outform PEM -out certs/test.htt-consult.com.crt
-newkey rsa:2048
On 1/1/2013 1:26 AM, Sial Nije wrote:
Greetings,
I need help to generate an ECDSA key file that is passphrase protected
and the key file is used in FIPS mode. My application is StrongSwan
linked with FIPS enabled libcrypto.so, version 1.0.1c.
Seems FIPS capable openssl executable uses hard
