Re: [openssl-dev] [openssl.org #4195] remove duplicates in util/libeay.num

2015-12-23 Thread Kurt Roeckx via RT
On Tue, Dec 22, 2015 at 09:03:56AM +, Roumen Petrov via RT wrote: > Hello, > > After remove of some global variables in export file left double Patch applied. Kurt ___ openssl-dev mailing list To unsubscribe:

[openssl-dev] [openssl.org #4195] remove duplicates in util/libeay.num

2015-12-22 Thread Roumen Petrov via RT
:00 2001 From: Roumen Petrov <open...@roumenpetrov.info> Date: Sat, 21 Mar 2015 15:29:25 +0200 Subject: [PATCH 2/2] remove duplicates in util/libeay.num --- util/libeay.num | 13 - 1 file changed, 13 deletions(-) diff --git a/util/libeay.num b/util/libeay.num index e9a678b..bce6c

Re: [PATCH or big HINT] libeay.num and ssleay.num changes needed in 1.0.2 and master

2014-07-20 Thread Jeff Trawick
speed_main speed.obj : error LNK2019: unresolved external symbol bn_probable_prime_dh_retry referenced in function speed_main speed.obj : error LNK2019: unresolved external symbol bn_probable_prime_dh_copri me referenced in function speed_main I don't see that in libeay.num or libssl.num, though I

[PATCH or big HINT] libeay.num and ssleay.num changes needed in 1.0.2 and master

2014-07-19 Thread Jeff Trawick
, and more.) 1.0.1 branch not checked... -- Born in Roswell... married an alien... http://emptyhammock.com/ http://edjective.org/ diff --git a/util/libeay.num b/util/libeay.num index a565877..aeba6e6 100755 --- a/util/libeay.num +++ b/util/libeay.num @@ -4417,3 +4417,87 @@ X509_get_signature_nid

Re: [PATCH or big HINT] libeay.num and ssleay.num changes needed in 1.0.2 and master

2014-07-19 Thread Dr. Stephen Henson
On Sat, Jul 19, 2014, Jeff Trawick wrote: This reduces the number of build problems on Windows+MSVC with the master branch. I don't know if the 1.0.2 branch was affected by the missing entries; it does build in the presence of these minor changes. I don't know if other fields have to be

Re: [CVS] OpenSSL: OpenSSL_1_0_1-stable: openssl/util/ libeay.num

2011-06-11 Thread Ben Laurie
: OpenSSL_1_0_1-stable) openssl/utillibeay.num Log: update ordinals Summary: RevisionChanges Path 1.296.2.19.2.7+8 -8 openssl/util/libeay.num patch -p0 '@@ .' Index

Re: [CVS] OpenSSL: OpenSSL_1_0_1-stable: openssl/util/ libeay.num

2011-06-10 Thread Dr. Stephen Henson
On Fri, Jun 10, 2011, Ben Laurie wrote: Hmm. This looks like the start of a version fight between FIPS and non-FIPS builds! The ordinals will be synced between builds so anything in 1.0.1 has the same ordinal in head. That can be done by just copying libeay.num from 1.0.1 to HEAD before make

[Patch] util/libeay.num

2006-05-12 Thread Gisle Vanem
With the following patch I'm able to link openssl.exe using the DLL (and not the static libs): --- orig/util/libeay.num Mon Apr 17 15:01:06 2006 +++ util/libeay.num Fri May 12 16:52:48 2006 @@ -3683,3 +3683,6 @@ EVP_PKEY_verify_recover 4079 EXIST::FUNCTION

Re: [Patch] util/libeay.num

2006-05-12 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Fri, 12 May 2006 16:57:58 +0200, Gisle Vanem [EMAIL PROTECTED] said: giva With the following patch I'm able to link openssl.exe using the DLL giva (and not the static libs): Did a make update. There were more symbols missing and some other stuff to correct. The

Re: libeay.num

2002-02-26 Thread Dr S N Henson
Jeffrey Altman wrote: When compiling an application with OPENSSL_LOAD_CONF defined, the macro maps to OPENSSL_add_all_algorithms_conf(), which additionally calls OPENSSL_config(NULL). This will automatically load the openssl.cnf file for engine configuration. The idea behind all this

Re: libeay.num

2002-02-26 Thread Jeffrey Altman
Where is the openssl.cnf file expected to be found on Windows? The actual location is now determined by the function CONF_get1_default_config_file() and the openssl utility will be modified so everything goes through it. Currently this follows the same logic for finding openssl.cnf

Re: libeay.num

2002-02-26 Thread Dr S N Henson
Jeffrey Altman wrote: Where is the openssl.cnf file expected to be found on Windows? The actual location is now determined by the function CONF_get1_default_config_file() and the openssl utility will be modified so everything goes through it. Currently this follows the same

Re: libeay.num

2002-02-26 Thread Jeffrey Altman
But most applications will share the same config file settings, at least as far as ENGINEs are concerned. It isn't really appropriate to provide a function to set the config file location. OPENSSL_config() is meant as a simple solution for existing applications and it does rather horrible

Re: cvs commit: openssl/util libeay.num mkdef.pl mkerr.pl

2002-02-14 Thread Dr S N Henson
Any reason for this: /* Override the default new methods */ static int sig_cb(int operation, ASN1_VALUE **pval, const ASN1_ITEM *it) { if(operation == ASN1_OP_NEW_PRE) { ECDSA_SIG *sig; sig = OPENSSL_malloc(sizeof(ECDSA_SIG)); if

Re: cvs commit: openssl/util libeay.num mkdef.pl

2001-10-24 Thread Richard Levitte - VMS Whacker
From: Ulf Moeller [EMAIL PROTECTED] ulf prior to using this function (see Lrand(3)|rand(3); for backward ulf-compatibility the function des_random_seed() is available as well). ulf+compatibility the function DES_random_seed() is available as well). Hmm, oops. The fact is,

Re: cvs commit: openssl/util libeay.num

2001-09-25 Thread Richard Levitte - VMS Whacker
From: Bodo Moeller [EMAIL PROTECTED] moeller Two functions with the same number - how'd that happen? moeller moeller util/mkdef.pl: moeller moellerif(exists $syms{ERR_load_CRYPTO_strings}) { moeller$platform{ERR_load_CRYPTO_strings} .= ,!VMS,!WIN16; moeller

Re: cvs commit: openssl/util libeay.num

2001-09-25 Thread Geoff Thorpe
not really the smartest if the functions would reappear (they would get a new number instead of getting the same number again, which may or may not be what you want). Ah ... OK. You seem to have a far better idea of what that script (and the libeay.num syntax) is all about, so perhaps I

Re: cvs commit: openssl/util libeay.num

2001-09-24 Thread Richard Levitte - VMS Whacker
From: Ulf Möller [EMAIL PROTECTED] ulf On Mon, Sep 24, 2001 at 07:42:38PM +0200, [EMAIL PROTECTED] wrote: ulf ulf-ERR_load_CRYPTOlib_strings 1009 NOEXIST::FUNCTION: ulf ERR_load_CRYPTO_strings 1009 NOEXIST::FUNCTION: ulf+ERR_load_CRYPTOlib_strings

Re: cvs commit: openssl/util libeay.num

2001-09-24 Thread Richard Levitte - VMS Whacker
From: Geoff Thorpe [EMAIL PROTECTED] geoff On Mon, 24 Sep 2001, Ulf [iso-8859-1] Möller wrote: geoff geoff On Mon, Sep 24, 2001 at 07:42:38PM +0200, [EMAIL PROTECTED] wrote: geoff geoff -ERR_load_CRYPTOlib_strings 1009 NOEXIST::FUNCTION: geoff

Re: cvs commit: openssl/util libeay.num

2000-11-17 Thread Ben Laurie
Ulf Moeller wrote: On Tue, Nov 14, 2000, [EMAIL PROTECTED] wrote: +rijndaelEncryptRound2642 EXIST::FUNCTION: +rijndaelDecrypt 2643 EXIST::FUNCTION: +rijndaelKeyEncToDec 2644 EXIST::FUNCTION:

Re: cvs commit: openssl/util libeay.num

2000-11-14 Thread Ulf Moeller
On Tue, Nov 14, 2000, [EMAIL PROTECTED] wrote: +rijndaelEncryptRound2642 EXIST::FUNCTION: +rijndaelDecrypt 2643 EXIST::FUNCTION: +rijndaelKeyEncToDec 2644 EXIST::FUNCTION: +rijndaelDecryptRound

Re: cvs commit: openssl/util libeay.num mk1mf.pl mkdef.pl mkerr.pl mkfiles.pl mkstack.pl

2000-11-10 Thread Ralf S. Engelschall
In article [EMAIL PROTECTED] you wrote: Remove references to RSAref. The glue library is but a memory to fade away now... Amen. Rest in peace RSAref... Thanks for kicking it out. Ralf S. Engelschall [EMAIL

libeay.num

2000-08-17 Thread Richard Levitte - VMS Whacker
... is full of unexisting symbols, has a few numbers missing and one duplicate (number 1009). Is that really the way it should be? I intended to use that file to produce shared libraries for VMS, but the way it currently looks, I get a huge amount of warnings about unresolved symbols. I'm

Re: cvs commit: openssl/util libeay.num

1999-06-28 Thread Arne Ansper
On Wed, 23 Jun 1999, Bodo Moeller wrote: This depends on how you define "properly written", obviously. If you yes. but in order to make the OpenSSLifying of existing applications simpler, it would be nice to follow the semantics of normal socket calls. then you can start using OpenSSL just

Re: cvs commit: openssl/util libeay.num

1999-06-23 Thread Anonymous
On Mon, 21 Jun 1999, Bodo Moeller wrote: It will work with the current implementation (but only if the applications don't do too stupid things, such as point to a buffer with different contents); but this may change. if the application does stupid things (i.e. does not check return value

Re: cvs commit: openssl/util libeay.num

1999-06-23 Thread Bodo Moeller
On Wed, Jun 23, 1999 at 08:02:28AM +0200, Arne Ansper wrote: Bodo Moeller: It will work with the current implementation (but only if the applications don't do too stupid things, such as point to a buffer with different contents); but this may change. if the application does stupid things

Re: cvs commit: openssl/util libeay.num

1999-06-21 Thread Anonymous
New functions CONF_load_bio() and CONF_load_fp() to load a configuration file from a bio or fp. Added some more constification to the BN library. i added write, delete and save functions + ability to use BIO's to CONF module long time ago and sent a patch to Ben too. too bad you had to

Re: cvs commit: openssl/util libeay.num

1999-06-21 Thread Anonymous
Arne Ansper wrote: New functions CONF_load_bio() and CONF_load_fp() to load a configuration file from a bio or fp. Added some more constification to the BN library. i added write, delete and save functions + ability to use BIO's to CONF module long time ago and sent a patch to Ben

Re: cvs commit: openssl/util libeay.num

1999-06-21 Thread Dr Stephen Henson
Arne Ansper wrote: New functions CONF_load_bio() and CONF_load_fp() to load a configuration file from a bio or fp. Added some more constification to the BN library. i added write, delete and save functions + ability to use BIO's to CONF module long time ago and sent a patch to Ben

Re: cvs commit: openssl/util libeay.num

1999-06-21 Thread Anonymous
Damn. I thought I'd applied all your patches. Are there any others I missed? i proposed to remove input parameter check from ssl/s2_pkt.c write_pending and ssl/s3_pkt.c ssl3_write_pending functions. there was a discussion about it back in January. snipet from original message: 8)

Re: cvs commit: openssl/util libeay.num

1999-06-21 Thread Anonymous
Arne Ansper [EMAIL PROTECTED]: [...] i proposed to remove input parameter check from ssl/s2_pkt.c write_pending and ssl/s3_pkt.c ssl3_write_pending functions. there was a discussion about it back in January. [...] if ((s-s3-wpend_tot (int)len) || (s-s3-wpend_buf != buf)