Am Montag, 3. November 2008 08:12:26 schrieb shivakumar Balur:
> HI All,
>
> when i tried to generate DH parameters using : openssl genpkey
> -genparam -algorithm DH -out dhp.pem -pkeyopt dh_paramgen_prime_len:1024
>
> ERROR:
> error: openssl:Error: 'genpkey' is an invalid command.
>
> Can any
HI All,
when i tried to generate DH parameters using : openssl genpkey -genparam
-algorithm DH -out dhp.pem -pkeyopt dh_paramgen_prime_len:1024
ERROR:
error: openssl:Error: 'genpkey' is an invalid command.
Can any one help me in this or any other commands to generate DH parameter n DH
Key.
HI All,
when i tried to generate DH parameters using : openssl genpkey -genparam
-algorithm DH -out dhp.pem -pkeyopt dh_paramgen_prime_len:1024
ERROR:
error: openssl:Error: 'genpkey' is an invalid command.
Can any one help me in this or any other commands to generate DH parameter n
DH Key.
I am developing an AES routine that utilizes some custom hardware to
perform the encryptions. I made a change to the code in the AES
folder, and the appropriate change to the Include paths in the AES
Makefile.
My custom hardware requires some libraries to be linked in. I am not
even close to a M
Double check your fipsld link line when generating the executable . I
suspect an issue with fingerprint which gets generated/embeds by using
the fipsld tool.
HTH
Jatheen Anand
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin A
Sent: Thursday, October 30, 2008 4:01 P
I all!
Maybe I'm too much novice on this, but I want to create a certificate
for each virtual host on my apache server (3 virtual hosts).
So i created my own CA, then one for each virtual host, like this:
Created the private CA and certificate:
openssl genrsa -out SSC_CA.key 1024
openssl re
Let me try one more time to explain the problem with an unrealistic, but I hope
easy to follow, example. Consider:
A <-> B
Now, imagine A sends a message to B requesting some unit of data. B begins
sending a very, very large chunk of data to A, many tens of MB. After 10 MB or
so, A realizes t
I'm going to punt this and suggest first and foremost that at least
part of this is a MatrixSSL issue (it's not handling the protocol
correctly, so it's extremely possible and even likely that it's
treating other aspects of SSLv3 like they're TLSv1+). You should
contact PeerSec and inform them tha
> please tell me where the deadlock is.
> As far as I know a deadlock arise when one process locks a
> resource an other
> process requests and vice versa.
A deadlock occurs when two or more agents are waiting for each other. Neither
can make forward progress until the other does. This is preci
