Hi,
I've been trying to build aes-armv4 for an embedded ARM 9 using the
Green Hills Software tools. In the FIPS canister, the line following
the label .Lok ...
.Lok: stmdb sp!,{r4-r12,lr}
sub r10,r3,#fips_aes_set_encrypt_key-AES_Te-1024@ Te4
gets this error:
[asarm]
Thank you for your quick response.
how come it's not required in all other perlasm modules?
errors do also occure in other perlasm modules, but i'am running this configure
command without asm support
which avoids calling other perlasm modules?
perl Configure debug-VC-WIN64A no-asm
On Sat, Apr 07, 2012 at 03:39:13PM +0200, Sebastian Andrzej Siewior via RT
wrote:
The command
|openssl enc -pass pass:pass -iv 0 -K 0 -S 0 -aes-256-cbc -base64 file
file.enc.b64
first performs the encryption followed by base64 encoding. That means the
output
is base64 encoded as
There are two groups of four ciphersuites that I think have mismatched key
exchange cipherlist labels.
The first four are DH-DSS ciphersuites with which don't seem to be enabled, but
as long as they are in the table perhaps they ought to be corrected.
This patch changes Kx in those instances
According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.
__
OpenSSL Project http://www.openssl.org
Development Mailing
On Thu, May 03, 2012, Alexander Komyagin wrote:
Thanks for the note, Stephen! I'll certainly take this into account.
If I incorporate OCSP check in check_revoked() function, which is called
during SSL connect/handshake it would just block during connect op for a
while, and I believe that no
[runningdoglac...@yahoo.com - Fri May 04 11:18:52 2012]:
There are two groups of four ciphersuites that I think have mismatched
key exchange cipherlist labels.
The first four are DH-DSS ciphersuites with which don't seem to be
enabled, but as long as they are in the table perhaps they
Can you give me an example of such application? I'll take a look at it.
On Fri, 2012-05-04 at 13:14 +0200, Dr. Stephen Henson wrote:
On Thu, May 03, 2012, Alexander Komyagin wrote:
Thanks for the note, Stephen! I'll certainly take this into account.
If I incorporate OCSP check in
Hello,
I am integrating OpenSSL X.509 functionality to an embedded system (first
use will be for SSH authentication), which presents a unique set of
problems. As I stated in an earlier post, certificate revocation checking
will be performed by OCSP and not CRLs due to limited storage capacity.
1. Someone posted a complaint on comp.os.vms about a missing header
file:
http://groups.google.com/group/comp.os.vms/browse_thread/thread/0887b1dfe5609d3f
Apparently, srtp.h is new, and was not added to the list in
ssl/install-ssl.com, so it doesn't get put into the installation
10 matches
Mail list logo
