It looks like ordinals are changing and/or being removed for functions
exported by the Windows DLL. Its causing pain points for users in the
field, and it appears to be trending. Confer:
* WAMP OpenSSL ordinal 372 error, http://stackoverflow.com/q/36238887
* The Ordinal 112 could not be located
Updated to print the options used when a failure occurs; add
additional test configurations, like "no-asm -ansi".
The QA/Testing team should try the script. Its very revealing. Here's
what I am seeing:
$ grep '!!' openssl-result.txt
!!FAILED (no-aes)!!
!!FAILED
Using Strawberry PERL from a typical Windows user desktop and working
from Master at c828cd7...
> cls && perl Configure VC-WIN32
...
> nmake
Microsoft (R) Program Maintenance Utility Version 11.00.61030.0
Copyright (C) Microsoft Corporation. All rights reserved.
NMAKE : fatal error U1073:
There's a somewhat dirty compile under Windows 7 Pro x64 and Visual Studio 2012.
cl -DDSO_WIN32 -DOPENSSL_THREADS -DOPENSSL_NO_DYNAMIC_ENGINE -DOPENSSL_P
IC -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENS
SL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM
> # if defined(OPENSSL_SYS_UEFI) && !defined(ssize_t) # define ossl_ssize_t
> int # define OSSL_SSIZE_MAX INT_MAX # endif
It's testing for a #define, not a typedef.
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On Fri, Mar 25, 2016 at 7:05 PM, Richard Levitte via RT
wrote:
> I've attached a tentative patch for test/recipes/bc.pl. Would you be willing
> to
> try it out?
OpenSSL master (c828cd7) experienced what appeared to be the same
issue under Windows 7 Pro x64 with Strawberry
On Fri, Mar 25, 2016 at 7:05 PM, Richard Levitte via RT
wrote:
> I've attached a tentative patch for test/recipes/bc.pl. Would you be willing
> to
> try it out?
OpenSSL master (c828cd7) experienced what appeared to be the same
issue under Windows 7 Pro x64 with Strawberry
Is this a real problem or a theoretical one?
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On Fri, Mar 25, 2016 at 8:10 AM, Hanno Boeck via RT wrote:
> Attached is a sample code that will test various inputs for the
> Poly1305 functions of openssl...
I'm seeing compiler conversion warnings about size_t to int
truncation. Do you have any vectors that cross the 2GB
On Fri, Mar 25, 2016 at 8:10 AM, Hanno Boeck via RT wrote:
> Attached is a sample code that will test various inputs for the
> Poly1305 functions of openssl...
I'm seeing compiler conversion warnings about size_t to int
truncation. Do you have any vectors that cross the 2GB
In message
On 27/03/2016 14:59, Salz, Rich wrote:
# if defined(OPENSSL_SYS_UEFI) && !defined(ssize_t) # define ossl_ssize_t
int # define OSSL_SSIZE_MAX INT_MAX # endif
It's testing for a #define, not a typedef.
Then I suppose this comes down to understanding precisely what the test
is trying to
And merged, commit ce84456ddf4e57c18a84858755b8b90c183a270e.
Closing this ticket.
Vid Sat, 26 Mar 2016 kl. 06.35.55, skrev levitte:
> Frankly, you did all the work. With your analysis, it became very easy to
> figure out what needed to be done. Low hanging fruit ;-)
>
> So, thank you!
>
>
On 27/03/16 00:16, Jeffrey Walton wrote:
> Is this a supported configuration (no-ui and apps)?
Co-incidentally, Richard has a patch for no-ui that fixes these problems
that is currently in review.
Matt
>
> There's a fair number of warnings when configuring with no-ui:
>
>
On Mon, Mar 07, 2016 at 10:03:20PM +, David Benjamin via RT wrote:
> Session resumption involves a version check, so version negotiation must
> happen first. Currently, the DTLS implementation cannot do session
> resumption in DTLS 1.0 because the ssl_version check always checks against
> 1.2.
>> noloader> I don't believe you can test for a type by using 'defined(t)'. Also
>> noloader> see
>> http://stackoverflow.com/questions/12558538/how-can-i-check-a-certain-type-is-already-defined-in-c-compiler.
>>
>> ... unless it's defined with a macro
>
> Yeah, I kind of knew about that. But a
I'm thinking this should be closed because the compile problem can be
worked around with "./config no-async". "./config no-async" worked on
both CentOS 5 and BSD 5.7 (both lack the headers).
I suppose it can be kept open if someone feels Configure should
auto-detect the feature. I'm in this camp
On Sun, Mar 27, 2016 at 10:41 AM, Salz, Rich wrote:
> Is this a real problem or a theoretical one?
UEFI will be a problem on non 32-bit systems as it assume 32-bit
environment. I don't know if there are any of them in the wild,
however.
non-UEFI code is a problem in some
> # if defined(OPENSSL_SYS_UEFI) && !defined(ssize_t) # define ossl_ssize_t
> int # define OSSL_SSIZE_MAX INT_MAX # endif
>
> It's testing for a #define, not a typedef.
>
>
> Then I suppose this comes down to understanding precisely what the test is
> trying to achieve. Do you mean it's
19 matches
Mail list logo