Michael Kurecka wrote:
> Thank you for your help that is definitely a point in the right
> direction; however, it leaves me more baffled. I found the only
> SSL_CTX_new function that is in the code and it is being passed
> the TLSv1_method not an SSLv*_method which is what it should be
> accordin
Exchange2007 will accept both a CER file (binary encoded PKCS7 file or
straight up PEM encoded PKCS7 file) or a PEM (Base64) encoded crt file
via the *Import-ExchangeCertificate* cmdlet. Same can be said for IIS 6
and 7. Both Default to the CER container format.
Exchange2007 has a function to
I haven't tried, but it's easy to know. Please post a CSR in base64 that you
produce in HSM and I will compare, posting both cases in text (one CSR made
in HSM and another made in openssl).
Or if you prefer I post one made in openssl and you use it to compare
Regards
shell session wrote:
>
>
Hello,
In case I use a HSM to generate a certificate request is it possible
to differentiate this cerificate request from a certificate request
issued from plain openssl?
Thank you.
__
OpenSSL Project
Make sure that key.pem actually contains a private key structure, not
just a public key.
-Kyle H
On Tue, Jul 21, 2009 at 11:49 AM, Chris Miller wrote:
> I have "key.pem" and "cert.pem" I'm trying to convert them to pkcs12 using
> the following command:
>
> openssl pkcs12 -export -in cert.pem -ink
Hello,
In case I use a HSM to generate a certificate request is it possible
to differentiate this cerificate request from a certificate request
issued from plain openssl?
Thank you.
__
OpenSSL Project
On Fri, Jul 17, 2009, Michael Kurecka wrote:
> I am trying to run wpa_supplicant in FIPS mode. The stack trace of the
> failure is below. I'm assuming that an algorithm not supported by FIPS
> is being used but I'm not sure which one since I thought I removed
> them all. I replaced SHA-1 with
>
>
Hi Javier, *,
Javier Mosqueda wrote:
>
> Exchange2007 Server expects a file *.cer. To get this I should somehow get
> a *.txt file to convert that into a *.cer. Am I right? What do I have to
> do to get a *.txt file to be able to convert that into a *.cer?
> Niels
>
Hi Niels:
Mail systems
>
> > What determines which SSL version is used? Is it the CTX object,
> > a configuration setting, etc.? I've tried tracing the code on
> > the OpenSSL side but it has me baffled even with a stack trace
> > I'm having trouble understanding its path. I would appreciate
> > any help you can give on
On Tue, Jul 21, 2009, Jeremy R. wrote:
> Never mind my question. Apparently the Base64 interpreter only accepts data
> if it's newline-terminated. Sorry for the bother.
>
By default yes but if you set BIO_FLAGS_BASE64_NO_NL in will handle data all
on one line.
Steve.
--
Dr Stephen N. Henson. Op
Hello,
I am facing a problem with the OCSP_basic_verify call.
I have a client certificate which is having the signature algorithm as
sha1RSA.
I have made sure that i call SSL_library_init with initialization of the
EVP_sha1 digest.
But i still see the error while processing the OCSP response:
Res
Hi Javier, *,
Check the man pages (man req), the -x509 option is for a self signed cert
(root), while the -new option produces a new cert request (so you are asking
for conflicting tasks). In this case no request is needed because the it's
the root cert. Your config option is ok.
This way a r
Hii'm writing an openssl engine for Tiny Encryption Algorithm .I can encrypt a
file with this engine, but when i decrypt output file, only first 16 bytes can
be decrypted and this error occurs : bad decrypt3412:error:06065064:digital
envelope routines:EVP_DecryptFinal_ex:bad decrypt:.\crypto\ev
Hi,
The application use the following functions for non-secure communication:
intBIO_write(BIO *b, const void *data, int len);
intBIO_read(BIO *b, void *data, int len);
calling them one by one.
The issue is that BIO_write() succeeds and returns the proper value of the data
written. The
I have "key.pem" and "cert.pem" I'm trying to convert them to pkcs12 using the
following command:
openssl pkcs12 -export -in cert.pem -inkey key.pem -out pkcs12.p12
I get the following:
"unable to load private key"
Any ideas?
Chris Miller
I have a problem configuring this old version (It's old - we couldn't
replace it because of embedded product issues - the lib is only used in
client mode)
@cd openssl; ./config -shared -no-idea -no-rc5 -no-mcs2 -no-aes
-threads; make depend
However, openssl ciphers -v still shows:
bash-2.0
16 matches
Mail list logo