Hi All,
Got the solution.
The problem was due to difference in building environment of Application &
OpenSSL. Some of the application binaries were built using their older
project format, i.e. *.vcproj & rest other binaries were built using their
newer project format, i.e. *.vcxproj.
Thanks to a
Check out this page: http://www.openssl.org/docs/crypto/OPENSSL_Applink.html
Basically, you just need to #include in your application.
That file defines a virtual table like list of things related to stdout,
stderr, etc. This file only appears to be needed when you start using functions
that m
I know this is a FAQ, but the answers I found all included the response
"that didn't work".
openssl 1.0.1c on Linux: How do I compile and link so the debugger can
step into the openssl code?
Are there definitive instructions anywhere, or does everyone use trial
and error?
I'm using a loca
On 3 September 2013 15:16, Jonas Andersson wrote:
> Hi all,
>
> Is there a way to verify a signature with ECDSA_do_verify having only the
> x-coordinate (in public key) available?
Are you sure you *only* have the x-coord and not a point in compressed
format? The difference being that with compres
On Tue, Sep 03, 2013, Viktor Dukhovni wrote:
>
> To the specific point in your reply, does OpenSSL actually support
> DSA-style groups (with p, g and q) where DH groups are expected?
> For example can such groups be returned from the temp DH callback?
> Certainly the dhparam(1) command does not s
On Tue, Sep 03, 2013 at 04:53:52PM +0200, Dr. Stephen Henson wrote:
> The SSL_CONF_cmd interface in OpenSSL 1.0.2 and later might be
> useful too. It's designed to provide a common format for configuration.
Thanks, I'll take a look at that when I get a chance. [ I'm still
concerned about the DA
On Tue, Sep 03, 2013, Viktor Dukhovni wrote:
> On Tue, Sep 03, 2013 at 03:16:06PM +0200, Dr. Stephen Henson wrote:
>
> The Postfix user (that is email administrator) interface does not
> require users to know much or anything at all about the various EECDH
> curves. The administrator chooses one
Hi all,
Is there a way to verify a signature with ECDSA_do_verify having only the
x-coordinate (in public key) available?
I am trying to verify a signature using "ECDSA_do_verify":
ECDSA_do_verify(dgst, dgst_len, signature, eckey_nistp256);
, where the eckey_nistp256 is given from:
EC_KEY_set_pu
On Tue, Sep 03, 2013 at 03:16:06PM +0200, Dr. Stephen Henson wrote:
> > Incidentally, I just noticed the undocumented
> > SSL_CTX_set_tmp_ecdh_callback(), which has the same interface as
> > SSL_CTX_set_tmp_dh_callback(3) and it seems is also called with
> > keylength equal to either 512 or 1024.
On Sun, Sep 01, 2013, Viktor Dukhovni wrote:
>
> Incidentally, I just noticed the undocumented
> SSL_CTX_set_tmp_ecdh_callback(), which has the same interface as
> SSL_CTX_set_tmp_dh_callback(3) and it seems is also called with
> keylength equal to either 512 or 1024. What is the meaning of
> th
Hello,
I have compiled net-snmp-5.5.2 with openssl-1.0.1e, and find it can not
success in windows OS.
At last I realize net-snmp-5.5.2 is not compatible with openssl-1.0.1e.
So I want to know which version of net-snmp is right under openssl-1.0.1e
environment.
Hope your quick answer, thank
That's software dependant.
Either one is a valid responder, and either response has the same value,
there's no "priority".
--
Erwann ABALEA
Le 02/09/2013 10:27, deepak.kathuria a écrit :
Hi,
I am using openssl OCSP utility as OCSP Responder in linux platform. At OCSP
Requester side, if OCSP
12 matches
Mail list logo
