I noticed that for the FIPS Object module for "./config no-asm" the endian
flag is removed from CFLAGS.
But in openssl, this is not the case. So, e.g. for linux-ppc, openssl build
has -DB_ENDIAN flag, but fips build has no such flag.
I'm guessing that the powerpc gcc may default to big-endian, so
When I try with ...-inform der I get ...
32328:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong
tag:tasn_dec.c:1306:
32328:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1
error:tasn_dec.c:380:Type=X509
From: owner-openssl-us...@openssl.org
[mailto:owner-ope
I copied all the system header files from their special home into the
location the powerpc--netbsd-gcc was looking for them, and then I could do
the "./config no-asm; make" successfully.
I am thinking that is a legal approach for building the FIPS Object Module.
If so, I answered my own question.
Many thanks, does the case of der matter - I tried DER without success?
From: owner-openssl-us...@openssl.org
To: openssl-users@openssl.org
Sent: Wed Nov 30 16:52:26 2011
Subject: Re: Unable to load certificate
Try using openssl x509 -noout -text -in serve
I think I know the answer to this but I'm hoping I am wrong.
I am building the FIPS Object Module v2.0 (a recent snapshot) on an
x86-linux2 host for an embedded PowerPC target running NetBSD. There is a
well-established and intricate build process already in place for the
product, and I am trying
Try using openssl x509 -noout -text -in server.crt -inform der
On Wed, Nov 30, 2011 at 10:28 AM, Hopkins, Nathan wrote:
> Hi, please can anyone help - what could be the possible cause for the
> below - my expectation is the .crt should be in the .pem format but I'm
> getting the below?
>
>
> open
Hi, please can anyone help - what could be the possible cause for the
below - my expectation is the .crt should be in the .pem format but I'm
getting the below?
openssl x509 -noout -text -in server.crt
unable to load certificate
31237:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong
ta
Hi
I try to pre-calculate the size of a EVP_Seal encrypted buffer (just the seal,
exkl. keys).
How do i precalculate that? I assume with some blocksize stuff (i'm a crypto
novice).
I'm using AES256 as EVP_CIPHER.
Thanks for any help
---
EVP_EncryptFinal and EVP_DecryptFinal must be used only one time after the
last update.
2011/11/28 Jussi Peltonen :
> I think I'm loadaing the correct DLL versions.
>
> From the Visual Studio IDE I can see that the libaye32.dll is loaded
> from the debug folder where I copied it.
>
> libeay32.dll
I mean all the bytes sent over the TCP socket (in both directions) up until
the point where the TLS layer will not send anymore data until you start
feeding it some plaintext to encrypt. You need to decide on a convention
for ordering sends relative to receives so both ends agree on the order in
10 matches
Mail list logo