[openssl-users] DSA_generate_key() or DSA_print_fp() with passphrase protection

in advance, Erik Leunissen. -- ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] DSA_generate_key() or DSA_print_fp() with passphrase protection

On 10/05/15 17:37, Erik Leunissen wrote: Hi all, The openssl gendsa command supports passphrase protected generation of dsa keys. I'm doing the dsa parameter and key generation, using the C API, using DSA_generate_parameters(), DSA_generate_key() and DSA_print_fp() Now, I'd like to write

[openssl-users] Retrieve OpenSSL version from C library

Hi, Does the OpenSSL C library have a function that returns the OpenSSL version? Thanks in advance for your help, Erik Leunissen. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Retrieve OpenSSL version from C library

On 12/01/15 22:57, Erik Leunissen wrote: Hi, Does the OpenSSL C library have a function that returns the OpenSSL version? Never mind. I found it just after sending this post. #include openssl/crypto.h const char *SSLeay_version(int type); Erik. Thanks in advance for your help, Erik

Confused about argument dsa to DSA_sign()

? Thanks in advance for any clarification, Erik Leunissen __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager

Building OpenSSL outside the source tree

defined for its own usage and takes care of proper referencing of SRC and BUILD directories. Does the openssl roadmap foresee a further development in this area, or is the current state deemed the right thing? Thanks for your response, Erik Leunissen

Re: Building OpenSSL outside the source tree

Richard Levitte wrote: You're thinking of configuration scripts generated using auto* tools. OpenSSL isn't one of those. I confess that I did, but at the same time I question whether it matters very much. As long as the Makefile is generated by *a* configure script, such a script could

Re: How to use DTLS?

hasn't been made public (yet). That might well be because no API *functions* are needed for the use of DTLS. However, some data structures are public. In your exploration of the openssl DTLS support, did you make use of the header file dtls1.h? Greetings, Erik Vladislav Erik Leunissen

Re: How to use DTLS?

Erik Leunissen wrote: So, indeed, it appears that the DTLS function interface hasn't been made public (yet). That might well be because no API *functions* are needed for the use of DTLS... Of course I meant this to be: So, indeed, it appears that no specific DTLS function interface has

How to use DTLS?

My previous post (30/03/07 01:54) regarding DTLS support didn't receive any replies. Maybe I wasn't clear. So here's the question rephrased: Can somebody please point out the commands to do DTLS? Thanks in advance, Erik Leunissen

API functions for DTLS?

introduce new API's? - If so, (where) have they been documented? - If not, is there a difference in usage of the existing TLS API's between securing TCP and securing UDP? Thanks for any pointers/explanation, Erik Leunissen

Re: ca setup problem

a better idea... Right. I replaced the name_opt entry and now it works. Hope it helps, It did absolutely. Greetings, Erik Leunissen. Ted ;) __ OpenSSL Project http://www.openssl.org

ca setup problem

that use My_CA (see below). Can anybody say what's wrong? Please say so if you need further/other information. Thanks in advance, Erik Leunissen == From the custom configguration file ca.conf: [ ca

Predictability of DSA signatures (first 8 bytes)

) Is the observed pattern normal? Thanks in advance for any advice, Erik Leunissen. === test script === #! /bin/sh openssl dsaparam -out dsaparam.pem 1024 openssl gendsa -out dsaprivatekey.pem dsaparam.pem rm ./result for file in ./text_1 ./text_2 ; do cat $file result echo result

Re: Predictability of DSA signatures (first 8 bytes)

Erik Leunissen wrote: ... The signatures (if expressed in hexadecimal format) all start with an 8 byte sequence that matches the regular expression: 302[cde]021[45] ... Of course that should be: the first 4 bytes, which corresponds to the first 8 hex digits Duh! Erik Leunissen

Re: How to find out why EVP_DecryptFinal failed?

Boris wrote: ... Maybe it would be a good idea to add this link to the return values section of http://www.openssl.org/docs/crypto/EVP_EncryptInit.html which explains only that 0 means failure. I too find that some inter-related aspects of the OpenSSL libraries are not linked/referred at

Re: How to find out why EVP_DecryptFinal failed?

is stored in an error queue associated with the current thread. The err library provides functions to obtain these error codes and textual error messages. Does this help? Erik Leunissen. __ OpenSSL Project

Re: Seeding the OpenSSL PRNG

Thanks all for your valuable comments, Erik Leunissen. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager

Re: Seeding the OpenSSL PRNG (continued ...)

whether an entropy source is lacking. Erik Leunissen. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager

Re: Seeding the OpenSSL PRNG (continued ...)

Richard Koenning wrote: Call RAND_status() (see http://www.openssl.org/docs/crypto/RAND_add.html#). Right. I overlooked that one. Thanks, Erik. __ OpenSSL Project http://www.openssl.org User

Seeding the OpenSSL PRNG

() ), or - the warning mechanism doesn't work properly Can anybody shed some light on what's happening here? In case it's relevant: the DSA_* functions that I mentioned above, are used in a program that has been running on Linux and on Windows 2000. Thanks in advance, Erik Leunissen

Re: Seeding the OpenSSL PRNG

whether the PRNG has been seeded before OpenSSL complains. How would I do that? TIA, Erik Leunissen == __ OpenSSL Project http://www.openssl.org User Support Mailing List

valgrind warnings for 0.9.8b

. Please let me know if further particulars are desired because it is significant. Erik Leunissen Valgrind output from a shared lib xxx that uses openssl0.9.8b === ==29192== Conditional jump or move depends on uninitialised value(s

Re: building openssl0.9.8a fails

managed to pick a copy under /usr/local/include while another one is available in /usr/include. Could this be an issue regarding the configuration of my Linux system, or is this an issue with the build configuration? Erik Leunissen

Re: building openssl0.9.8a fails

, help, Erik Leunissen == __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager

building openssl0.9.8a fails

what's wrong? Thanks in advance, Erik Leunissen == __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List

Usage of DSA parameters p, q and g with DSA_verify() and DSA_sign()

key? Could anybody please enlighten me? Thanks in advance, Erik Leunissen == __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users

Re: Problem using DSA_verify()

DSA_verify() believe the signature size to be different from 20 bytes, if I pass a hard coded 20 as the fifth argument to DSA_verify()? - I don't understand which structure containing two 160 bit numbers you're referring to. Greetings, Erik Leunissen

Re: Problem using DSA_verify()

(). Adapting my code to variably sized signatures made the errors go away. I'm still curious though, about the signature structure that you mentioned. Could you perhaps point me to any documentation regarding that? Thanks in advance, Erik Leunissen

Re: Problem building shared libs for openssl0.9.7f

Nils Larsch wrote: doing a make clean before building the sources should help It did indeed. Thanks a lot, Erik Leunissen == __ OpenSSL Project http://www.openssl.org User Support

Problem building shared libs for openssl0.9.7f

. Thanks in advance, Erik Leunissen == System specification: cpu: i586 Linux version: 2.4.21-202-athlon gcc version: 3.3.1 (SuSE Linux) openssl-0.9.7f Build sequence and make output: -- ./config shared make The last lines from

Problem building openssl0.9.7f shared

did read the remark in the INSTALL file, saying: Shared library is currently an experimental feature. Can anybody clarify whether a build should be possible? If that should be possible, what's gone wrong in my case? Thanks in advance, Erik Leunissen == make output follows