Forwarded for public discussion.
Best regards,
Lutz
- Forwarded message from Ramon Madera ramonjmad...@yahoo.com -
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Proper
Thanks a lot, Jakob! Adding rdata align=8 to the section declaration
in tmp32/x86_64cpuid.asm helped. At least the warnings disappeared, and
*OPENSSL_ia32cap_loc() is now EFFB instead of 0.
So, the instructions to build on windows x64 would be:
* call C:\Program Files\Microsoft Visual
On Mon, Oct 04, 2010, per frykenvall wrote:
Thanks a lot, Jakob! Adding rdata align=8 to the section declaration in
tmp32/x86_64cpuid.asm helped. At least the warnings disappeared, and
*OPENSSL_ia32cap_loc() is now EFFB instead of 0.
So, the instructions to build on windows x64 would
Hello,
Apart from a question of version of openssl,
? could it be for an End Of Line management difference between the two worlds
:
\n on unix
\r \n on Windows
Tricks exist with sed or tr to convert between the two.
Best regards,
Pierre Delaage
Selon Lutz Jaenicke jaeni...@openssl.org:
Hello everyone!
My name's Irving and I'm new to openssl.
I'm having an issue and I hope I can get help here.
I have a tiny software written to communicate with an http server; on a
Solaris system it works alright, but on an OpenVMS system I'm getting these
errors:
545318540:error:0D07809F:asn1
Does BIO support 64 bit IO (large files)? If so would the rest of
OpenSSL (such as the ssl itself) support those BIOs?
I configured the build with 64bit support and didn't see any noticeable
changes.
Specifically, I'd like to know if BIO_tell() is able to return a 64bit
value?
On Mon October 4 2010, irivas wrote:
Hello everyone!
My name's Irving and I'm new to openssl.
I'm having an issue and I hope I can get help here.
I have a tiny software written to communicate with an http server; on a
Solaris system it works alright, but on an OpenVMS system I'm getting
I have a tiny software written to communicate with an http server; on a
Solaris system it works alright, but on an OpenVMS system I'm getting
these
errors:
545318540:error:0D07809F:asn1 encoding
routines:ASN1_ITEM_EX_D2I:unexpected
eoc:TASN_DEC:337:Type=X509_ALGOR
On Mon, Oct 04, 2010 at 10:37:55AM -0400, Jeff Saremi wrote:
Does BIO support 64 bit IO (large files)? If so would the rest of
OpenSSL (such as the ssl itself) support those BIOs?
I configured the build with 64bit support and didn't see any noticeable
changes.
Specifically, I'd like to know
I do not know anything about OpenVMS and Solaris,
BUT big endian / little endian and improper use of htons in YOUR software
could explain many things.
You should check also \r and \r \n issue, even if not reading any file,
because it may be in cause in fprintf(fd, \n);
\n being expanded
To further clarify:
The error is a result of a call to BIO_do_connect();
Prior to that call, I make a call to sprintf(%s:%d); (no newlines
involved).
I'll try substituting the sprintf for a more ubiquitous process and let you
know. Any further ideas on the matter?
-Original Message-
ASN.1 encoding will require much more than a simple sprintf.
If your resulting string is expected to be encoded in ASN.1, then there
may be a problem there.
Pierre
Le 04/10/2010 22:02, irivas a écrit :
To further clarify:
The error is a result of a call to BIO_do_connect();
Prior to that
I don't even know where those errors come from. As I said before, the same
code under Solaris runs alright.
I'm only connecting to a regular webserver with ssl, nothing more, nothing
less.
I'm not consciously using anything other than plain http-- none of which is
used up to that point.
Calls
Hi all,
i using openssl test tool by using this command
openssl.exe ocsp -issuer issuer.pem -CAfile CACert.pem -cert
Certificate.pem -url http://192.168.0.235:8080/myCA/publicweb/status/ocsp
my CACert and issuer cert already expired. but it still return me respond
verify OK. i see in my ca
From: owner-openssl-us...@openssl.org On Behalf Of irivas
Sent: Monday, 04 October, 2010 16:36
(I changed the subject to be more descriptive.)
I don't even know where those errors come from. As I said
before, the same code under Solaris runs alright.
I'm only connecting to a regular
Hi All,
I found a code snippet as follows:
ASN1_SEQUENCE(KDC_PRINCNAME) = {
ASN1_EXP(KDC_PRINCNAME, realm, ASN1_GENERALSTRING, 0),
ASN1_EXP(KDC_PRINCNAME, princname, KRB5_PRINCNAME, 1)
} ASN1_SEQUENCE_END(KDC_PRINCNAME);
IMPLEMENT_ASN1_FUNCTIONS(KDC_PRINCNAME)
Here
16 matches
Mail list logo
