Hi,
I have an HTTP server named thttpd, on ARM platform. I use stunnel to redirect
http requests to https, with openSSL secure certification.
I have created two seperate certificates for my server and client (he re client
is a web browser).
Now my question is, when I create .crt certificate s
On May 2, 2014, at 3:19 AM, Kevin Le Gouguec
wrote:
> (tl;dr : see questions at the end)
>
> I'm trying to build nested CMS structures, as in, having a file F, a signer S
> and a recipient R, I want to build a CMS-compliant message M which looks like:
>
> M = SignedData(ECI, SignerInfo(S))
>
On 02/05/14 15:38, foxtrot wrote:
3) Here is the new cert we are trying to introduce (sales.1d.qb.com)
Certificate:
Data:
Version: 1 (0x0)
X.509v1 rather than X.509v3. Could that be the problem?
--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust O
Thanks for your suggestions. I missed a basic step to set the INCLUDE path
which points to VS header files and Windows Embedded Compact SDK. This was
not mentioned in the blog which i followed. I was able to successfully
compile openssl for WINCE 6.0 as well as WEC7. Thanks all.
--
View this me
On Fri, May 2, 2014 at 7:05 AM, krinalishah wrote:
>
> ...
> I have created two seperate certificates for my server and client (here
> client is a web browser).
> Now my question is, when I create .crt certificate signed by CA, via
> openSSL, it asks me for Common Name.
> What I understand by this
Thank you for your input!
> No; I’d be concerned if it didn’t show up that way — that’s how CMS is defined
> to work.
Just took another look at RFC 5652 and indeed, EncapsulatedContentInfo is a
SEQUENCE of { ContentType, EXPLICIT OCTET STRING OPTIONAL }.
> I’ll let someone else answer that;
