Hello,
crypto/x86_64cpuid.s generated by perl
32 bit (has problem) & 64 bit (no problem) are attached.
Regards,
--- Kiyoshi
>
>> I'm sorry to be late.
>> I was too busy and had to prepare 64 bit gdb (& 64 bit perl).
>>
>> It seems to be 32 bit perl
--On Wednesday, August 24, 2016 5:47 PM -0700 Quanah Gibson-Mount
wrote:
this is clearly a TLS client-side stack trace. Why is nginx acting
as an SSL/TLS client?
It's a proxy server... so it's proxying between the client connecting to
nginx on the IMAPS port and the
Note that a 32-bit Perl can be compiled with or without support for 64-bit
integers.
That fact hit me once doing OpenSSL builds, some 64-bit constants were not
calculated correctly, however that showed up at build time so not likely
to be the case here. However, it might be helpful checking if
On Thu, Sep 01, 2016 at 01:58:00PM -0700, Quanah Gibson-Mount wrote:
> >The issue only happens when proxying IMAP on port 143 with startTLS or
> >993 (IMAPS). It does not occur on POP w/ starttls or web traffic (443).
> >It also is only happening with this one particular client, as we have
>
Note that a 32-bit Perl can be compiled with or without support for 64-bit
integers.
That fact hit me once doing OpenSSL builds, some 64-bit constants were not
calculated correctly, however that showed up at build time so not likely
to be the case here. However, it might be helpful checking if
> Note that a 32-bit Perl can be compiled with or without support for 64-bit
> integers.
> That fact hit me once doing OpenSSL builds, some 64-bit constants were not
> calculated correctly, however that showed up at build time so not likely
> to be the case here. However, it might be helpful
Dear Richard,
On Thu, Sep 1, 2016 at 5:39 PM, Richard Levitte wrote:
> In message gmail.com> on Thu, 1 Sep 2016 16:06:54 +0300, Dmitry Belyavsky <
> beld...@gmail.com> said:
>
> beldmit> Hello Openssl Team,
>
> I'm sorry to be late.
> I was too busy and had to prepare 64 bit gdb (& 64 bit perl).
>
> It seems to be 32 bit perl (perl-5.24.0) problem.
> (Generating 64 bit code with 32 bit perl.)
For reference, I'm using 32-bit perl version 5.10.1, minimally supported
version, by default, i.e. *all* the
I'm sorry to be late.
I was too busy and had to prepare 64 bit gdb (& 64 bit perl).
It seems to be 32 bit perl (perl-5.24.0) problem.
(Generating 64 bit code with 32 bit perl.)
Tested with openssl-1.1.0 instead of pre-6,
and on pure Solaris 10, without any VM.
(1) with 32 bit perl
Did
Hi Richard,
Here are more information.
I'm using two AIX 6.1 machines.
I built openssl 1.0.1* and 1.0.2* on first machine, compiled with GCC & -O .
I moved to second machine for 1.1.0 .
I have rebuilt/tested 1.0.2h , still with GCC & -O (same .spec file), on the
second machine and I got the
> Results:
>
>
> In short:
> - no issue with v1.0.2h on both machines
> - issue appears with:
> - XLC -O but only for 64bits
> - GCC -O for both 64bits and 32bits
> - issue disappears when building ppccap.c with -O0 .
>
> So, I think that the probability that both XLC and GCC
> About the possible "linker quirk", the same linker is used also for version
> 1.0.2h which runs perferctly.
Yes, but 1.0.2 and 1.1 ppccap's are different.
> Also, that does not explain why simply compiling ppccap.c only with -O0 makes
> the issue to dispappear.
Bugs seldom make sense. If
Before sending the last message i looked around on the website (it
has become particularly complicated to find the bug tracker), and
looking at the "go-back" list i saw dozens of "OpenSSL" entries,
rather than rt, "Getting started as a contributor", etc.
--steffen
--
Ticket here:
About the possible "linker quirk", the same linker is used also for version
1.0.2h which runs perferctly.
Also, that does not explain why simply compiling ppccap.c only with -O0 makes
the issue to dispappear.
I also tried to repeat the failing test several times: failure is consistent.
Here
Hello Openssl Team,
I'm currently working on a patch providing support of the
https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-00 draft.
I want to use functions from the libidn library to process the specified
conversion.
How do I add the linkage against libidn to the build system?
Hello.
>From the documentation i cannot tell what is wrong with the
following:
echo abc > a; echo def > b; echo ghi > c
openssl genpkey -algorithm RSA -out k.prv
openssl pkey -in k.prv -pubout -out k.pub
openssl dgst -sha512 -sign k.prv -out .sig a b c
openssl dgst -sha512 -verify
Hi Andy,
We need bugs !
Without bugs, no more job !! ;)
About openssl built/tested on AIX 7.1 , I have an AIX 7.1 machine.
Would you mind saying me which compiler was used ? GCC I guess. Which version ?
Thanks,
Tony
Le 01/09/2016 15:45, Andy Polyakov via RT a écrit :
About the possible
In message
on Thu, 1 Sep 2016 16:06:54 +0300, Dmitry Belyavsky said:
beldmit> Hello Openssl Team,
beldmit>
beldmit> I'm currently working on a patch providing support of the
beldmit>
> About openssl built/tested on AIX 7.1 , I have an AIX 7.1 machine.
> Would you mind saying me which compiler was used ? GCC I guess. Which version
> ?
The reason for why I said "I'll look at it a bit later today" is that
accessing that system is problematic for me for this very moment. And
On my AIX 7.1 machine, building/testing evp test of openssl 1.1.0 with:
- GCC 4.8.5 is: OK, 64 & 32 bits:
../test/recipes/30-test_evp.t .. ok
- GCC 5.4.0 is: OK, 64 & 32 bits:
../test/recipes/30-test_evp.t .. ok
- GCC 6.1.0 is: KO, 64 & 32 bits:
# Failed
updated the wiki, thanks.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4666
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Can you please provide some concrete examples, so I know what to look for and
fix? (I'm kinda slow sometimes)
Thanks!
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4668
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
22 matches
Mail list logo