Hello,
I am trying to compile my appilcation performing PKCS7 logic. I am having
issue during compilation of the x509 related objects.
Specifically, there is name collision between wincrypt.h and openssl.
During my initial research I found that it is a common problem (user list
and ticket#1749).
Hi there,
I am trying to cross compile openssl 1.0.0beta4 on my Linux box. I am
using mingw-w32 (http://sourceforge.net/projects/mingw-w64/files/
Toolchains%20targetting%20Win32/Release%20for%20GCC%204.4.1/mingw-w32-
bin_x86-64-linux_4.4.1a.tar.bz2/download).
$ export CC=/home/zmichl/tools/ming
What do you find unclear about the INSTALL file? As it says, if you want
dynamic libraries use ntdll.mak, if you want static libraries use
nt.mak. I can't tell you which you should prefer, that depends on what
you're doing with them.
I don't know about openssl.cfg.
_
On Thu, Nov 19, 2009, Shaw Graham George wrote:
>
> No, this is the output from "openssl x509 -text", but without "-nameopt
> utf8", which has no effect on the output anyway.
>
Try -nameopt oneline,utf8,-esc_msb
Also: -nameopt multiline,utf8-esc_msn,show_type which will show how the actual
st
No, this is the output from "openssl x509 -text", but without "-nameopt utf8",
which has no effect on the output anyway.
G.
-Original Message-
From: dry...@sky-haven.net [mailto:dry...@sky-haven.net]
Sent: 19 November 2009 17:16
To: Shaw Graham George
Subject: Re: Creating a certifica
On Thu, Nov 19, 2009, Brant Thomsen wrote:
> One major issue to consider when using UTF-16 encoding is that the string
> can be big-endian or little-endian. If you were to somehow generate a
> certificate using UTF-16 encoded strings, you would need to make sure that
> those certificates will onl
One major issue to consider when using UTF-16 encoding is that the string can
be big-endian or little-endian. If you were to somehow generate a certificate
using UTF-16 encoded strings, you would need to make sure that those
certificates will only be used on machines that have the same architec
Krishnappanaidu, Vasu wrote:
We are using your ssldump to decrypt the SSL traffic and we get
“segmentation fault” and also it core dumps.
Use wireshark (or the command line version tshark), ssldump is dead and
buried.
wireshark also has some bugs in this domain (less than ssldump, but
still
Could anyone tell the procedure to set up the Openssl in fc7..I am using the
certificates for EAP-TLS authentication.
What are the packages I need to install?
Currently I am using three scripts to generate certificates. I am attaching
it.
Thanks in advance.
Regards
Anoop C
On Thu, Nov 19, 2009, Shaw Graham George wrote:
> Thanks Steve,
>
> >> OpenSSL will *NOT* however do what happens above with the C (Country)
> field.
> >> That is a two character code and only PrintableString (a restricted
> version of
> >> ASCII) characters are permitted. Doing anything else vio
Thanks Steve,
>> OpenSSL will *NOT* however do what happens above with the C (Country)
field.
>> That is a two character code and only PrintableString (a restricted
version of
>> ASCII) characters are permitted. Doing anything else violates several
standards.
That's interesting, considering that
UTF-8 *IS* perfectly valid Unicode -- it's one of the main Unicode
encodings, and seems entirely appropriate for use in certs, although I
personally have no knowledge of the support in OpenSSL or the X509
standard. UTF-8 is a variable length encoding where the valid UTF-8
characters are from 1 to
On Thu, Nov 19, 2009, Shaw Graham George wrote:
> Hi,
>
> I have a requirement to make some test keys/certificates that contain
> Unicode (Chinese) data in the Issuer and Subject fields. Print-out from
> an example certificate using "openssl x509" is:
>
> Issuer: C=\x00C\x00N,
> ST=\x00
Hi,
I have a requirement to make some test keys/certificates that contain
Unicode (Chinese) data in the Issuer and Subject fields. Print-out from
an example certificate using "openssl x509" is:
Issuer: C=\x00C\x00N,
ST=\x00G\x00u\x00a\x00n\x00g\x00d\x00o\x00n\x00g,
L=\x00G\x00u\x00a\x00n
On Wed, Nov 18, 2009, Krishnappanaidu, Vasu wrote:
> Hi,
>
> We are using your ssldump to decrypt the SSL traffic and we get
> "segmentation fault" and also it core dumps.
>
It is not "our" ssldump, it isn't part of the OpenSSL project.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core deve
Hi Vasu,
> We are in desperate to resolve this issue and any help/insight
> would be greatly appreciated as this is an urgent issue.
In case no one is interested in grinding though the dump files, you
might find someone to assist at
http://www.openssl.org/support/consulting.html.
Jeff
On Wed, No
Hello,
Please help me in clearing doubts regarding the openssl lib and dll
generation from the openssl tar ball.
I downloaded the openssl tar ball from the site and generated lib
files(libeay32.lib and ssleay32.lib) using the command "nmake -f ms\nt.mak".
The lib files generated has a s
Hi
Thank you very much for a complete review on codeI resolved all the
problems and found the issue is in key...
can you tell me now what is problem..the code below run into error at set
decrypt key
the shell command for decryption of my file is o
penssl enc -d -K
3834373532303435333730323
Hi,
We are using your ssldump to decrypt the SSL traffic and we get
"segmentation fault" and also it core dumps.
- Operating system: Red Hat Linux el4 i386, update 4.
- The key that's being used: 3 chained certificates as an extended
certificate signed by VeriSign Class 3 Extended Val
Oh.. I've been away from this for a while. So, I didn't check email from
OpenSSL.
By the way, i would like to appreciate your kindness of providing some
sample code. :)
JongAm Park
Reid Thompson wrote:
JongAm Park wrote:
Hello.
Thank you for mentioning the book.
However, I could figure ou
20 matches
Mail list logo
