Working from Master...
gentoo@Gentoo-2012 ~/openssl $ ./config
Operating system: x86_64-whatever-linux2
Configuring for linux-x86_64
Configuring OpenSSL version 1.1.0-pre4-dev (0x0x1014L)
no-crypto-mdebug [default] OPENSSL_NO_CRYPTO_MDEBUG (skip dir)
no-crypto-mdebug-backtrace [forced
Bump... The issue is still present as of b36a2ef for OS X 10.6 64-bit.
32-bit tests OK.
The relevant snippets are:
$ make test
...
../test/recipes/90-test_async.t ... 1/1
# Failed test 'running asynctest'
# at ../test/testlib/OpenSSL/Test/Simple.pm line 70.
# Looks like you failed 1 t
Bump... The issue is still present as of b36a2ef for OS X 10.6 64-bit.
32-bit tests OK.
The relevant snippets are:
$ make test
...
../test/recipes/90-test_async.t ... 1/1
# Failed test 'running asynctest'
# at ../test/testlib/OpenSSL/Test/Simple.pm line 70.
# Looks like you failed 1 t
The README.PERL states:
You MUST have at least Perl version 5.10.0 installed. This
minimum requirement is due to...
However, the Configure source files use:
#! /usr/bin/env perl
# -*- mode: perl; -*-
##
## Configure -- OpenSSL source tree configuration script
## I
On Sun, Mar 13, 2016 at 7:56 PM, Richard Levitte via RT
wrote:
> Vid Sun, 13 Mar 2016 kl. 23.16.45, skrev noloa...@gmail.com:
>> On Sun, Mar 13, 2016 at 7:09 PM, Richard Levitte via RT
>> wrote:
>> > Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
>> >> $ perl --version
>> >> This i
On Sun, Mar 13, 2016 at 7:56 PM, Richard Levitte via RT
wrote:
> Vid Sun, 13 Mar 2016 kl. 23.16.45, skrev noloa...@gmail.com:
>> On Sun, Mar 13, 2016 at 7:09 PM, Richard Levitte via RT
>> wrote:
>> > Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
>> >> $ perl --version
>> >> This i
Vid Sun, 13 Mar 2016 kl. 23.16.45, skrev noloa...@gmail.com:
> On Sun, Mar 13, 2016 at 7:09 PM, Richard Levitte via RT
> wrote:
> > Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
> >> $ perl --version
> >> This is perl, v5.8.8 built for x86_64-linux-thread-multi
> >
> > This is a pro
On Sun, Mar 13, 2016 at 7:09 PM, Richard Levitte via RT
wrote:
> Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
>> $ perl --version
>> This is perl, v5.8.8 built for x86_64-linux-thread-multi
>
> This is a problem. We don't really support perl older than 5.10, so 5.8.x is
> potentia
On Sun, Mar 13, 2016 at 7:09 PM, Richard Levitte via RT
wrote:
> Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
>> $ perl --version
>> This is perl, v5.8.8 built for x86_64-linux-thread-multi
>
> This is a problem. We don't really support perl older than 5.10, so 5.8.x is
> potentia
Vid Sun, 13 Mar 2016 kl. 22.05.21, skrev noloa...@gmail.com:
> $ perl --version
> This is perl, v5.8.8 built for x86_64-linux-thread-multi
This is a problem. We don't really support perl older than 5.10, so 5.8.x is
potentially challenging. It's quite possible you found a problem area.
As far as
By the way, the serial number accessors are missing from the docs too or is
that just a problem with the website?
Cheers
Rich.
On 13 March 2016 at 22:30, Richard Moore wrote:
> On 13 March 2016 at 21:34, Viktor Dukhovni
> wrote:
>
>>
>> > On Mar 13, 2016, at 10:41 AM, Rainer Jung
>> wrote:
>
On 13 March 2016 at 21:34, Viktor Dukhovni
wrote:
>
> > On Mar 13, 2016, at 10:41 AM, Rainer Jung
> wrote:
> >
> > The docs should be fixed, but there's:
> >
> > int EVP_PKEY_id(const EVP_PKEY *pkey);
> > int EVP_PKEY_base_id(const EVP_PKEY *pkey);
>
> Thanks for the nudge:
>
>
> https://github.
That's great, thanks Rainer. I'll give those a try.
Rich.
On 13 March 2016 at 14:41, Rainer Jung wrote:
> Am 13.03.2016 um 14:34 schrieb Richard Moore:
>
>> I'm currently testing the new release by trying to port Qt to use it
>> (with the compatibility stuff disabled). Here are the first proble
Line 1248 is the 'mkpath' below.
sub cleandir {
my $base = shift;
my $dir = shift;
my $relativeto = shift || ".";
$dir = catdir($base,$dir) unless isabsolute($dir);
# Make sure the directories we're building in exists
mkpath($dir);
my
This is kind of odd... Working from Master at b36a2ef.
It appears Configure is trying to create the directory "/include"
rather than "$PWD/include".
$ git clone ...
$ ls -Al | grep openssl
drwxrwxr-x 19 jwalton jwalton 4096 Mar 13 17:37 openssl
$ cd openssl
$ ./config
Operating system: x86_64-w
> On Mar 13, 2016, at 10:41 AM, Rainer Jung wrote:
>
> The docs should be fixed, but there's:
>
> int EVP_PKEY_id(const EVP_PKEY *pkey);
> int EVP_PKEY_base_id(const EVP_PKEY *pkey);
Thanks for the nudge:
https://github.com/openssl/openssl/commit/b36a2efd55078a5fff32b2755046b23cb3c5d8a3
--
On Sun, Mar 13, 2016 at 02:09:34PM +, Olaf Kirfel via RT wrote:
> Hallo
> I am using Embarcadero/Borland C++-Builder for my personal interest and
> I have the problem, that after the update to openssl 1.0.2g the
> indy-components are not working.
> They are delivering an error message like "s
Am 13.03.2016 um 14:34 schrieb Richard Moore:
I'm currently testing the new release by trying to port Qt to use it
(with the compatibility stuff disabled). Here are the first problems
I've hit:
How do we get the certificate serial number? We were doing
x509->cert_info->serialNumber to get it as
Hallo
I am using Embarcadero/Borland C++-Builder for my personal interest and
I have the problem, that after the update to openssl 1.0.2g the
indy-components are not working.
They are delivering an error message like "ssl-security library could
not be loaded" (I tried to translate it, sorry).
I
doctor> > Please don't be surprised if a daily snapshot is broken for a day,
consider waiting a day or two to see if the problem is fixed.
doctor> >
doctor> > This is not the first time we've asked for this.
doctor>
doctor> Now add Openssl-SNAP-20160313 issue
I'm currently testing the new release by trying to port Qt to use it (with
the compatibility stuff disabled). Here are the first problems I've hit:
How do we get the certificate serial number? We were doing
x509->cert_info->serialNumber
to get it as an ASN1_INTEGER.
https://www.openssl.org/docs/m
e include your config/setup command when you report things.
>
> Please don't be surprised if a daily snapshot is broken for a day, consider
> waiting a day or two to see if the problem is fixed.
>
> This is not the first time we've asked for this.
Now add Openssl-SNAP-201
Vid Sun, 13 Mar 2016 kl. 11.19.45, skrev noloa...@gmail.com:
> On Sun, Mar 13, 2016 at 6:48 AM, Richard Levitte via RT
> wrote:
> > Could you check again? I believe it should have been fixed when I did
> > away with
> > `sed` for dependency post-processing.
> >
>
> Yes, you're right. My bad.
No p
On Sun, Mar 13, 2016 at 11:27:23AM +, noloa...@gmail.com via RT wrote:
> >> static const uint64_t blake2b_IV[8] =
> >> {
> >> 0x6a09e667f3bcc908U, 0xbb67ae8584caa73bU,
> >> 0x3c6ef372fe94f82bU, 0xa54ff53a5f1d36f1U,
> >> 0x510e527fade682d1U, 0x9b05688c2b3e6c1fU,
> >> 0x1f83d9abfb
>> static const uint64_t blake2b_IV[8] =
>> {
>> 0x6a09e667f3bcc908U, 0xbb67ae8584caa73bU,
>> 0x3c6ef372fe94f82bU, 0xa54ff53a5f1d36f1U,
>> 0x510e527fade682d1U, 0x9b05688c2b3e6c1fU,
>> 0x1f83d9abfb41bd6bU, 0x5be0cd19137e2179U
>> };
>>
>> I've run into this before, but in C++. I think
>> static const uint64_t blake2b_IV[8] =
>> {
>> 0x6a09e667f3bcc908U, 0xbb67ae8584caa73bU,
>> 0x3c6ef372fe94f82bU, 0xa54ff53a5f1d36f1U,
>> 0x510e527fade682d1U, 0x9b05688c2b3e6c1fU,
>> 0x1f83d9abfb41bd6bU, 0x5be0cd19137e2179U
>> };
>>
>> I've run into this before, but in C++. I think
On Sun, Mar 13, 2016 at 07:15:52AM -0400, Jeffrey Walton wrote:
> On Sun, Mar 13, 2016 at 6:57 AM, Kurt Roeckx via RT wrote:
> > On Sun, Mar 13, 2016 at 10:30:54AM +, noloa...@gmail.com via RT wrote:
> >> crypto/blake2/blake2b.c:27: warning: integer constant is too large for
> >> 'unsigned lon
> static const uint64_t blake2b_IV[8] =
> {
> 0x6a09e667f3bcc908U, 0xbb67ae8584caa73bU,
> 0x3c6ef372fe94f82bU, 0xa54ff53a5f1d36f1U,
> 0x510e527fade682d1U, 0x9b05688c2b3e6c1fU,
> 0x1f83d9abfb41bd6bU, 0x5be0cd19137e2179U
> };
>
> I've run into this before, but in C++. I think you need
On Sun, Mar 13, 2016 at 07:15:52AM -0400, Jeffrey Walton wrote:
> On Sun, Mar 13, 2016 at 6:57 AM, Kurt Roeckx via RT wrote:
> > On Sun, Mar 13, 2016 at 10:30:54AM +, noloa...@gmail.com via RT wrote:
> >> crypto/blake2/blake2b.c:27: warning: integer constant is too large for
> >> 'unsigned lon
> static const uint64_t blake2b_IV[8] =
> {
> 0x6a09e667f3bcc908U, 0xbb67ae8584caa73bU,
> 0x3c6ef372fe94f82bU, 0xa54ff53a5f1d36f1U,
> 0x510e527fade682d1U, 0x9b05688c2b3e6c1fU,
> 0x1f83d9abfb41bd6bU, 0x5be0cd19137e2179U
> };
>
> I've run into this before, but in C++. I think you need
On Sun, Mar 13, 2016 at 6:48 AM, Richard Levitte via RT
wrote:
> Could you check again? I believe it should have been fixed when I did away
> with
> `sed` for dependency post-processing.
>
Yes, you're right. My bad.
Close it.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4421
On Sun, Mar 13, 2016 at 6:48 AM, Richard Levitte via RT
wrote:
> Could you check again? I believe it should have been fixed when I did away
> with
> `sed` for dependency post-processing.
>
Yes, you're right. My bad.
Close it.
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org
On Sun, Mar 13, 2016 at 6:57 AM, Kurt Roeckx via RT wrote:
> On Sun, Mar 13, 2016 at 10:30:54AM +, noloa...@gmail.com via RT wrote:
>> crypto/blake2/blake2b.c:27: warning: integer constant is too large for
>> 'unsigned long' type
>
> That's a uint64_t. Why do you have an "unsigned long" as 64
On Sun, Mar 13, 2016 at 6:57 AM, Kurt Roeckx via RT wrote:
> On Sun, Mar 13, 2016 at 10:30:54AM +, noloa...@gmail.com via RT wrote:
>> crypto/blake2/blake2b.c:27: warning: integer constant is too large for
>> 'unsigned long' type
>
> That's a uint64_t. Why do you have an "unsigned long" as 64
Thank you. Closing
Vid Sun, 13 Mar 2016 kl. 10.58.12, skrev noloa...@gmail.com:
> On Sun, Mar 13, 2016 at 6:14 AM, Richard Levitte via RT
> wrote:
> > Identified and corrected, waiting to pass internal review. I've
> > attached the
> > fix for your viewing and application before it lands in maste
On Sun, Mar 13, 2016 at 6:14 AM, Richard Levitte via RT
wrote:
> Identified and corrected, waiting to pass internal review. I've attached the
> fix for your viewing and application before it lands in master.
>
It looks like the change was pushed with 6d505f2.
It tested OK under both 32-bit and
On Sun, Mar 13, 2016 at 6:14 AM, Richard Levitte via RT
wrote:
> Identified and corrected, waiting to pass internal review. I've attached the
> fix for your viewing and application before it lands in master.
>
It looks like the change was pushed with 6d505f2.
It tested OK under both 32-bit and
On Sun, Mar 13, 2016 at 10:30:54AM +, noloa...@gmail.com via RT wrote:
> crypto/blake2/blake2b.c:27: warning: integer constant is too large for
> 'unsigned long' type
That's a uint64_t. Why do you have an "unsigned long" as 64 bit
uint64_t?
Kurt
--
Ticket here: http://rt.openssl.org/Tick
Could you check again? I believe it should have been fixed when I did away with
`sed` for dependency post-processing.
Vid Sun, 13 Mar 2016 kl. 10.22.15, skrev noloa...@gmail.com:
> $ make clean && find . -name '*tmp.bak' | wc -l
> rm -f
> rm -f
> rm -f libcrypto.a libssl.a
> ...
> rm -f `find . -n
Great, thank you. Closing ticket.
Vid Sun, 13 Mar 2016 kl. 04.41.20, skrev noloa...@gmail.com:
> I think this was closed earlier... retesting at 4c1cf7e confirmed the
> issue was cleared.
>
> On Thu, Mar 10, 2016 at 3:41 PM, noloa...@gmail.com via RT
> wrote:
> > Working from Master on a BeagleBo
> ...
> Another potential pain point is PERL:
>
> grep -iIR perl * | grep '#' | grep -v 'env' | wc -l
> 232
>
> It looks like most uses of PERL are expected to be at
> /usr/local/bin/perl. 160 of them use /usr/bin/env, but 230 or so use
> the potentially incorrect path.
This is testing OK
> ...
> Another potential pain point is PERL:
>
> grep -iIR perl * | grep '#' | grep -v 'env' | wc -l
> 232
>
> It looks like most uses of PERL are expected to be at
> /usr/local/bin/perl. 160 of them use /usr/bin/env, but 230 or so use
> the potentially incorrect path.
This is testing OK
I just witnessed it freeze when pressing ^C, never getting out of read. That
fix seems to be to add `exit 0` in the trap string. That fix is currently in
review.
Vid Sun, 13 Mar 2016 kl. 04.27.06, skrev noloa...@gmail.com:
> When running a naked "./config" on Apple platforms (both Intel and
> Powe
cc -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_THREADS
-DOPENSSL_NO_DYNAMIC_ENGINE -DOPENSSL_PIC -DOPENSSL_BN_ASM_MONT
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DAES_ASM -DVPAES_ASM
-DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\""
-DENGINESDIR="\"/usr/local/lib/engines\"" -O3 -D_REENTRANT -arch ppc
-DB_ENDIAN
$ make clean && find . -name '*tmp.bak' | wc -l
rm -f
rm -f
rm -f libcrypto.a libssl.a
...
rm -f `find . -name '*.d'`
rm -f `find . -name '*.o'`
rm -f core
rm -f tags TAGS
rm -f openssl.pc libcrypto.pc libssl.pc
rm -f `find . -type l`
rm -f ../openssl-1.1.0-pre4-dev.tar
755
--
Ticket here: http
Identified and corrected, waiting to pass internal review. I've attached the
fix for your viewing and application before it lands in master.
Cheers,
Richard
Vid Sun, 13 Mar 2016 kl. 04.47.04, skrev noloa...@gmail.com:
> The issue is present under 64-bit OS X PowerPC builds, also.
>
> On Sat, Mar
On Sun, Mar 13, 2016 at 06:29:14AM +, noloa...@gmail.com via RT wrote:
> >> 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?
> >
> >
> >
47 matches
Mail list logo
