One related caveat. I've found that if OPENSSL_NO_FP_API is defined, then
there will be some undefined symbol errors at compile time; some references to
FILE, etc. are not conditionalized out.
However, I've done an embedded port to a non-standard OS, so your mileage may
vary.
Paul
___
On Wed, Aug 17, 2011 at 1:51 PM, Kchitiz Saxena
wrote:
> Hi Wim
> Thanks for the response. Actually, I am trying to compile openssl for WinCE
> 5.0. That's why I was trying to figure out whether I should define this
> macro while compiling or not. However, if this macro is defined, I get few
> com
Hello,
I have been chasing this issue for a while now, but have not been able to
reproduce myself.
I am using OpenSSL 0.9.8n.
We see that the HTTPS (apache) crashes (don't know the exact reason).
We have been able to get core files of the crashes and have the backtrace for
them
Below are some o
Hi Wim
Thanks for the response. Actually, I am trying to compile openssl for WinCE
5.0. That's why I was trying to figure out whether I should define this
macro while compiling or not. However, if this macro is defined, I get few
compilation errors.
Have anyone compiled the code with this flag for
On 17 Aug 2011, at 7:36 AM, Kchitiz Saxena wrote:
> Can somebody briefly explain the use of macro OPENSSL_NO_STDIO. There are few
> functions like SSL_CTX_use_certificate_file() which are defined only if this
> macro is not defined. What is the functionality which is derived out of this
> macro
Hi Dave,
thanks a lot for your help. Will try out your suggestions.
Dhoti
dave.mclel...@emc.com wrote:
Also look at BIO_s_fd().This is the one you want if you need to get the raw socket.
Dave
-Original Message-
From: mclellan, dave
Sent: Wednesday, August 17, 2011 7:45
Hi
Can somebody briefly explain the use of macro OPENSSL_NO_STDIO. There are
few functions like SSL_CTX_use_certificate_file() which are defined only if
this macro is not defined. What is the functionality which is derived out of
this macro definition. In short, what I get/loose if I define this ma
Thank you, I got it worked out. I just had to concatenate the ca pem file to
the client pem file and using that as the -in argument when export the pkcs12,
then I had the full chain in one file.
Thank you to both you and yyy for your help.
Travis
From: owner-openssl-us...@openssl.org [mailto
Hi Erwann and Stephen,
We solved the problem about generating a PKCS#10 from a embedded
processor. Some configurations in the signature generation coprocessor
were wrong.
Your hints helps to discover it.
Tnakyou very much
Giordano
2011/8/5 Dr. Stephen Henson :
> On Fri, Aug 05, 2011, Erwann AB
Perhaps, I am answering the wrong question but I use the following makefile
receipts to do what I understand from your question:
trusted.cert.pem: $(ROOTCA)/root.root.crt.pem \
$(SUBCA)/proxy.root.crt.pem
$(RM) -f $@
cat $^ >$@
server.pfx: server.root.crt.
p12 files can contain multiple certificates (full chain). It seems to install full chain,however i had root cert already installed, for this chain.I do not know, how to add a der (or pem) file to existing p12 file.Probably it wold be easier to make a new p12 filefrom all necessary der (or pem) file
Perhaps I am asking the wrong question. Files types aside, can one create a
single file that can be used to install a full chain of trust on a windows
machine?
Travis
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Travis Dimmig
Sent: Friday, Augus
12 matches
Mail list logo