[openssl-dev] AI_ADDRCONFIG test from configure

Here is a segment that should work { $as_echo "$as_me:${as_lineno-$LINENO}: checking for working AI_ADDRCONFIG fla g" >&5 $as_echo_n "checking for working AI_ADDRCONFIG flag... " >&6; } if ${inn_cv_func_getaddrinfo_addrconfig_works+:} false; then : $as_echo_n "(cached) " >&6 else if test

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On Fri, Mar 11, 2016 at 7:26 PM, Richard Levitte via RT wrote: > In message > on Fri, > 11 Mar 2016 19:12:27 -0500, Jeffrey Walton said: > > noloader> >> What is actually running? How

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On Fri, Mar 11, 2016 at 7:26 PM, Richard Levitte via RT wrote: > In message > on Fri, > 11 Mar 2016 19:12:27 -0500, Jeffrey Walton said: > > noloader> >> What is actually running? How

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

In message on Fri, 11 Mar 2016 19:12:27 -0500, Jeffrey Walton said: noloader> >> What is actually running? How can I get it under a debugger? noloader> > noloader> > noloader> > $ ./config -d noloader> > $

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

>> What is actually running? How can I get it under a debugger? > > > $ ./config -d > $ make > $ make test/afalgtest > $ cd test > $ OPENSSL_ENGINES=../engines/afalg gdb ./afalgtest > Ooh, -d looks like a new option. Would that be for Debug builds? Jeff -- openssl-dev mailing list To

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On 12/03/16 00:12, noloa...@gmail.com via RT wrote: >>> What is actually running? How can I get it under a debugger? >> >> >> $ ./config -d >> $ make >> $ make test/afalgtest >> $ cd test >> $ OPENSSL_ENGINES=../engines/afalg gdb ./afalgtest >> > > Ooh, -d looks like a new option. Would that be

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

>> What is actually running? How can I get it under a debugger? > > > $ ./config -d > $ make > $ make test/afalgtest > $ cd test > $ OPENSSL_ENGINES=../engines/afalg gdb ./afalgtest > Ooh, -d looks like a new option. Would that be for Debug builds? Jeff -- Ticket here:

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

Close it; it was cleared around bb26842d1c8f99c1267b45361a2fc76822c0f913. On Fri, Mar 11, 2016 at 5:11 AM, noloa...@gmail.com via RT wrote: > Working from Master. > > $ make test > make: don't know how to make usr/include/stddef.h. Stop > > make: stopped in /root/openssl --

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

Close it; it was cleared around bb26842d1c8f99c1267b45361a2fc76822c0f913. On Fri, Mar 11, 2016 at 5:11 AM, noloa...@gmail.com via RT wrote: > Working from Master. > > $ make test > make: don't know how to make usr/include/stddef.h. Stop > > make: stopped in /root/openssl --

[openssl-dev] libcryto 1.1 leaks since old locks are removed

Hi, I have just removed the old locking "stuff" from my Windows 7 tests programs, and now they leak again. :'( If someone have time to look at this issue, here under is the call stack : Detected memory leaks! Dumping objects -> {3750} normal block at 0x002F34B8, 24 bytes long. Data:

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On 11/03/16 19:38, noloa...@gmail.com via RT wrote: > On Thu, Mar 10, 2016 at 2:29 PM, noloa...@gmail.com via RT > wrote: >> Working from Master: >> > > It looks like the hang is still present as of 603358d. > > When the following runs: > >

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On 11/03/16 19:38, noloa...@gmail.com via RT wrote: > On Thu, Mar 10, 2016 at 2:29 PM, noloa...@gmail.com via RT > wrote: >> Working from Master: >> > > It looks like the hang is still present as of 603358d. > > When the following runs: > >

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

Returning to the issue at hand: https://github.com/openssl/openssl/pull/851 On Fri, Mar 11, 2016 at 7:24 PM Erik Forsberg wrote: > add Solaris to the platforms that are not at beta-level yet. > Richard Levitte and myself are helping each other out though, so we should > be close

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On Thu, Mar 10, 2016 at 2:29 PM, noloa...@gmail.com via RT wrote: > Working from Master: > It looks like the hang is still present as of 603358d. When the following runs: ../test/recipes/30-test_afalg.t What is actually running? How can I get it under a debugger? Jeff

Re: [openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

On Thu, Mar 10, 2016 at 2:29 PM, noloa...@gmail.com via RT wrote: > Working from Master: > It looks like the hang is still present as of 603358d. When the following runs: ../test/recipes/30-test_afalg.t What is actually running? How can I get it under a debugger? Jeff

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

add Solaris to the platforms that are not at beta-level yet. Richard Levitte and myself are helping each other out though, so we should be close >-- Original Message -- > >> noloader> Testing master on real hardware is showing some minor issues on a >> few >> noloader> platforms, including

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

> but from my point of view it is really hard to contribute code to OpenSSL. Things are much better, but it is still harder than we'd like. Hopefully it will continue to improve. > I feel really sorry for the authors of PR's that got first review but their > code won't get into 1.1 because of

Re: [openssl-dev] CRYPTO_lock definition gone?

Yes, the old locking “stuff” is gone now. Look in threads.pod for information about CRYPTO_THREAD_lock_new, etc. Its cross-platform and better-integrated with the native OS -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: RichSalz From: Blumenthal, Uri - 0553 - MITLL

[openssl-dev] CRYPTO_lock definition gone?

In a commit done in the last two days, definition of CRYPTO_lock() seems to have disappeared or moved. As a result, libp11 cannot compile on openssl-1.1-pre4: p11_cert.c:50:3: warning: implicit declaration of function 'CRYPTO_lock' is invalid in C99 [-Wimplicit-function-declaration]

Re: [openssl-dev] [openssl.org #4415] test/certs/mkcert.sh uses "#! /binbash"

On Fri, Mar 11, 2016 at 12:05:32PM +, noloa...@gmail.com via RT wrote: > test/certs/mkcert.sh uses: > > #! /bin/bash" This shell script is only used in test development, it is not used during either compilation or testing of OpenSSL. It need not be especially portable. --

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

On 11 March 2016 at 15:22, Salz, Rich wrote: > > I would like to point out that there are several already reviewed pull > requests with new features - e.g. [0] and [1] - waiting to be merged. Do > openssl devs plan to address these before 1.1 freeze? > > >[0]

Re: [openssl-dev] [openssl.org #4416] 1.0.1s makes porting to HP-UX much harder than before

> On Mar 11, 2016, at 9:25 AM, H.Merijn Brand via RT wrote: > > https://github.com/openssl/openssl/issues/806 > > Let me take HP-UX 11.11/PA2 as an example. > Up to and including 1.0.1r, I just unpacked from the > distributes .tar.gz and ran > > $ ./Configure zlib

[openssl-dev] [openssl.org #4416] 1.0.1s makes porting to HP-UX much harder than before

https://github.com/openssl/openssl/issues/806 Let me take HP-UX 11.11/PA2 as an example. Up to and including 1.0.1r, I just unpacked from the distributes .tar.gz and ran $ ./Configure zlib zlib-dynamic no-asm hpux64-parisc2-cc $ perl -pi -e's/\+O3/+O2 +Z -AC99/' Makefile $ make $ make test $

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

> I would like to point out that there are several already reviewed pull > requests with new features - e.g. [0] and [1] - waiting to be merged. Do > openssl devs plan to address these before 1.1 freeze? >[0] https://github.com/openssl/openssl/pull/576 > [1]

[openssl-dev] [openssl.org #4411] VIA C7-D processor: Hang in 30-test_afalg.t

Hi Jeff On Thu Mar 10 19:29:21 2016, noloa...@gmail.com wrote: > Working from Master: > > $ git reset --hard HEAD && git pull > HEAD is now at fb04434 In the recipe using "makedepend", make sure the > object file extension is there > Already up-to-date. > > $ ./config > ... > $ make depend &&

Re: [openssl-dev] OPENSSL_cleanup new issue

Hi Roumen On 10/03/16 22:21, Roumen Petrov wrote: > Hello, > > With new thread model in some configurations openssl hands on unload of > engine. I just pushed commit 773fd0bad4 to master which should hopefully resolve this issue. Matt -- openssl-dev mailing list To unsubscribe:

[openssl-dev] [openssl.org #4401] [PATCH] plug potential memory leak(s) in OpenSSL 1.1 pre 4 in 'ec_lib.c'

Yep, there is no need to clean up early here (we don't guarantee that errored calls leave everything in a pristine unmodified state). Plus this does indeed forget to zero the pointer. Closing. Thanks for submitting, though, and thanks David for the review! -- Ticket here:

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

On 11 March 2016 at 10:21, Matt Caswell wrote: > I'd argue that a freeze helps us to iron the issues out. Problems tend > to get introduced when new features are added. By declaring a freeze we > no longer accept new features and can instead divert our attention to > stability

[openssl-dev] [openssl.org #4415] test/certs/mkcert.sh uses "#! /binbash"

test/certs/mkcert.sh uses: #! /binbash" It does not work as expected on some platforms, like OpenBSD and FreeBSD where Bash is located in, say, /usr/local/bin or /usr/pkg/bin/bash. Instead, I believe you should use: #! /usr/bin/env bash Another potential pain point is PERL: grep

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

On 11 March 2016 at 09:24, Jeffrey Walton wrote: >> noloader> Testing master on real hardware is showing some minor issues on a >> few >> noloader> platforms, including ARM32, ARM64, PowerPC and i686. In addition, >> noloader> there seems to be one-off issues on other

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

In message on Fri, 11 Mar 2016 05:25:29 -0500, Jeffrey Walton said: noloader> On Fri, Mar 11, 2016 at 5:14 AM, Richard Levitte via RT wrote: noloader> > In message

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

On Fri, Mar 11, 2016 at 5:14 AM, Richard Levitte via RT wrote: > In message on Fri, 11 > Mar 2016 10:11:43 +, "noloa...@gmail.com via RT" said: > > rt> Working from Master. > rt> > rt> $ make test >

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

On Fri, Mar 11, 2016 at 5:14 AM, Richard Levitte via RT wrote: > In message on Fri, 11 > Mar 2016 10:11:43 +, "noloa...@gmail.com via RT" said: > > rt> Working from Master. > rt> > rt> $ make test >

[openssl-dev] Patent Issues for openssl version

Hello Team, The following procedure is used to Integrate compiled openssl-fips2.0 in openssl-1.0.1e : a. Extract the contents of openssl-1.0.1e.tar.gz to C:\openssl-1.0.1e-fips-compliant\ b. Open Visual Studio 2008 Command Prompt. c. cd C:\openssl-1.0.1e-fips-compliant\

Re: [openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

In message on Fri, 11 Mar 2016 10:11:43 +, "noloa...@gmail.com via RT" said: rt> Working from Master. rt> rt> $ make test rt> make: don't know how to make usr/include/stddef.h. Stop rt> rt> make: stopped in

[openssl-dev] [openssl.org #4414] NetBSD 7.0: make test fails with "don't know how to make usr/include/stddef.h"

Working from Master. $ make test make: don't know how to make usr/include/stddef.h. Stop make: stopped in /root/openssl -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4414 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

> noloader> Testing master on real hardware is showing some minor issues on a > few > noloader> platforms, including ARM32, ARM64, PowerPC and i686. In addition, > noloader> there seems to be one-off issues on other combinations, like VIA's > C7 > noloader> processor on Linux. > noloader> >

Re: [openssl-dev] Please consider delaying the Beta-1 freeze for a week or two

On 11/03/16 01:03, Jeffrey Walton wrote: > Hi Everyone, > > Testing master on real hardware is showing some minor issues on a few > platforms, including ARM32, ARM64, PowerPC and i686. In addition, > there seems to be one-off issues on other combinations, like VIA's C7 > processor on Linux. >

Re: [openssl-dev] [openssl.org #4413] Cygwin x86_64: make: *** No rule to make target '/openssl/Configurations/unix-Makefile.tmpl', needed by 'configdata.pm'.

In message on Fri, 11 Mar 2016 08:07:17 +, "noloa...@gmail.com via RT" said: rt> Working from master: rt> rt> $ git reset --hard HEAD && git pull rt> HEAD is now at 603358d Add include directory options for assembler

[openssl-dev] [openssl.org #4413] Cygwin x86_64: make: *** No rule to make target '/openssl/Configurations/unix-Makefile.tmpl', needed by 'configdata.pm'.

Working from master: $ git reset --hard HEAD && git pull HEAD is now at 603358d Add include directory options for assembler files that include from crypto/ Already up-to-date. $ ./config ... $ make depend $ make make: *** No rule to make target