Thanks matt for looking at this. below are the details
json from C with openSSL
{
prime:
1) The C version is in hex while the java version is in decimal. Is this
intentional? When you are reading in the values are reading them correctly
(i.e. as hex or as decimal as required)
Yes. it was intentional. I am taking care of this.
2) Is this sample from the *same* key exchange? The
Hi Erwann
What you have to do it hash your data, prepare an X509_SIG object, set
its algor to SHA1 (with NULL parameters), and fill the digest part
with your hash result. Then transform it into DER, and sign it with
CKM_RSA_PKCS mechanism.
Thanks a lot for the explanation. However, I can't
On 18 March 2013 12:15, azhar jodatti azhar...@gmail.com wrote:
2) Is this sample from the *same* key exchange? The parameters are
different which are obviously going to cause it to fail.
When I run both programs it calculates the params (p,g,pk) every time on
execution . that's the reason
I'm unable to build Git 1.8.1.3 with libcrypto. I've compiled and
built OpenSSL with the same LDFLAGS and CPPFLAGS as below. I also have
a `/etc/ld.so.conf.d/sandbox.conf` file which loads
`/sandbox/builds/lib` as a library path for LD_LIBRARY_PATH.
$ uname -a
Linux kosuna 3.5.0-17-generic
Hello kapetr,
I have successfully time-stamped with TSA server
https://www.postsignum.cz/DEMOTSA/TSS_user/; (u: demoTSA, p: demoTSA2010),
using 2 Time-stamp clients:
1. Adobe Reader 10.1.3
2. Serbian Post Time-stamp client:
On Mon, Mar 18, 2013, Tim Tassonis wrote:
Hi Erwann
What you have to do it hash your data, prepare an X509_SIG object, set
its algor to SHA1 (with NULL parameters), and fill the digest part
with your hash result. Then transform it into DER, and sign it with
CKM_RSA_PKCS mechanism.
Hi Stephen
Thanks a lot, that did the trick, the verify now returns ok.
Kind regards
Tim
On 03/18/2013 02:26 PM, Dr. Stephen Henson wrote:
On Mon, Mar 18, 2013, Tim Tassonis wrote:
Hi Erwann
What you have to do it hash your data, prepare an X509_SIG object, set
its algor to SHA1 (with
On 18 March 2013 12:15, azhar jodatti azhar...@gmail.com wrote:
2) Is this sample from the *same* key exchange? The parameters are
different which are obviously going to cause it to fail.
When I run both programs it calculates the params (p,g,pk) every time on
execution . that's the reason
On 18 March 2013 15:05, azhar jodatti azhar...@gmail.com wrote:
I also just noticed that in your JSON sample there is only one prime
number provided. There are in fact two required: p and q.
well, I think other prime number is g and not q. other prime number is
base generator i.e g in above
Viktor and others, thanks for the tips. I found that by using OpenSSL
1.0.1e I've been able to create the UTF8 format fields, such as:
71:d=5 hl=2 l= 3 prim: OBJECT:commonName
76:d=5 hl=2 l= 6 prim: UTF8STRING:Róót
However, creating the subjectAltName is not
From: owner-openssl-us...@openssl.org On Behalf Of azhar jodatti
Sent: Saturday, 16 March, 2013 14:00
I am working on application which has android and iPhone client.
Both the client talk to my server which is written in JAVA. I am
using JCE implementation of DH algorithm and X509EncodedkeySpec
From: owner-openssl-us...@openssl.org On Behalf Of Matt Caswell
Sent: Monday, 18 March, 2013 09:17
On 18 March 2013 12:15, azhar jodatti azhar...@gmail.com wrote:
2) Is this sample from the *same* key exchange? The parameters are
different which are obviously going to cause it to fail.
When I
Hi,
The application I am working on should not support TLS 1.1 and above protocols.
I am using SSL_CTX_set_options( ctx, SSL_OP_NO_TLSv1_1); to disable the same
after creating the SSL context. But it doesn't seem to disable the TLS1.1 and
TLS1.2 protocols
Code Snippet:
SSL_CTX *c =
On 18 March 2013 21:02, Dave Thompson dthomp...@prinpay.com wrote:
I also just noticed that in your JSON sample there is only one
prime number provided. There are in fact two required: p and q.
No. *DSA* uses p,q,g. DH requires p,g which effectively determines
q, but DH computation doesn't
On 18 March 2013 21:44, Matt Caswell fr...@baggins.org wrote:
However, you are correct that the DH computation does not use q, although
I do not
know whether JCE requires it to be specified (not having used JCE).
One other point on this - X9.42 describes an optional validation procedure
Hello,
Are you linking with libdl.so? (-ldl)
-Tom
Thomas Floodeen, Jr.
Mentor Graphics BSD
720.494.1133
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of zero modulo
Sent: Sunday, March 17, 2013 10:33 PM
To:
I suspect you need a
export FIPS_SIG=path to openssl-fips/util/incore
which embeds the signature in libcrypto.
On 18/03/13 17:16, Abhijit Ray Chaudhury wrote:
Hello,
I am trying to cross compile FIPS compliant openssl module
(openssl-fips-ecp-2.0.2.tar.gz) for linux armv4 pratform :
I have
18 matches
Mail list logo
