RE: looking for properly configured Windows VMs
> From: Michael Wojcik > Sent: Friday, 1 April, 2022 15:41 > > > > View results: https://github.com/openssl/openssl/actions/runs/2073285321 > > I'll take a look when I get a chance to see if anything jumps out. I > haven't had to deal with IPv6 raw or UDP programming in Windows yet, but I > do a fair bit with Windows networking development in general. Logs have been deleted, unfortunately.
RE: looking for properly configured Windows VMs
> From: openssl-users On Behalf Of > Michael Richardson > Sent: Friday, 1 April, 2022 07:34 > > Attempts to make bss_dgram.c compile with the right IPv6 include for > Windows > are not going well. > > Some of the jobs actually die before my test case even runs, but at least, > I > guess they compile bss_dgram.c > Others (the shared ones) seem to fail completely to compile bss_dgram.c > > I haven't run a compile on DOS since the days of djcpp... Well, to be fair, modern Windows isn't even slightly MS-DOS. But it is often a difficult and unnecessarily idiosyncratic environment. > I wonder if anyone has VM images with the right OS and compilation tools > installed? I don't have public ones. I do have assorted Windows platforms available, though, and I'll try to pull your branch (do I remember correctly that you posted a link a while back?) over the weekend and build it, if I can find the time. > The day-long cycle, making a change and then waiting for CI to give an > opinion is just too slow. (I didn't know WIN32 was still even thing... I > guess Windows ME still uses it maybe.) Many modern Windows applications are 32-bit programs. Modern Windows itself is a 64-bit OS, but runs 32-bit programs in a translation environment (WOW64, for "Windows on Windows"). About 10% of the processes currently running on my main Windows development system at the moment are 32-bit. Many of our flagship products install both 32- and 64-bit binaries because customers may be using either or both at the same time. So for Windows the 32-bit builds of OpenSSL are still quite important. Not that it really matters one way or the other, I suppose. If Win32 is a supported platform, it's a supported platform, and we'd like to fix this to build there (rather than just not supporting the feature). (Windows ME, on the other hand, is long dead. Last release was over 20 years ago. But Microsoft's parade of versions with different naming conventions makes this sort of thing tough to keep track of.) > Subject: Re: [openssl/openssl] PR run failed: Windows GitHub CI - > bio_dgram uses recvmsg/sendmsg to retrieve destination and set origin > address (41cc92c) > > View results: https://github.com/openssl/openssl/actions/runs/2073285321 I'll take a look when I get a chance to see if anything jumps out. I haven't had to deal with IPv6 raw or UDP programming in Windows yet, but I do a fair bit with Windows networking development in general. -- Michael Wojcik
RE: [openssl/openssl] bio_dgram vs IPv6
> From: Michael Richardson > Sent: Friday, 1 April, 2022 07:40 > > Michael Wojcik wrote: > > Actually, in the context of #if expressions, unrecognized tokens > expand to 0 anyway: > > > After all replacements due to macro expansion and the defined unary > > operator have been performed, all remaining identifiers are replaced > > with the pp-number 0... > > > (ISO 9899:1999 6.10.1 #3) > > Yes, but that generates a warning, and then error via -Werror with some > set > of compile options that at least one CI run uses. Oh, well. An implementation is allowed to generate any diagnostics it wishes, and is allowed to fail to translate even a conforming program. Ultimately we're at the mercy of the implementation, and GCC is not a particularly good C implementation. (Of course, in its default mode, it doesn't implement C; it implements a language similar to, but not, C.)
OpenSSL 3.0.2 PKCS12_parse Failure
Hello, Connection between a Openssl 3.0.2 server and a 1.1.1g client is proving to be unsuccessful. According to the logs collected we seem to be having an issue with the loading of the legacy providers. We are loading both the default and legacy providers programmatically as per the steps outlined in the Wiki for OpenSSL 3.0 - 6.2 Providers. We are seeing the following error.. error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:346:Global default library context, Algorithm (RC2-40-CBC : 0), Properties () PKCS12_parse() failed = 183. (Using GetLastError from errhandlingapi.h, the 183 error code is obtained) Worth mentioning that we are only seeing this issue occur when the server is a Windows 2012 server. Thank you, Victor C.
Re: [openssl/openssl] bio_dgram vs IPv6
Michael Wojcik wrote: > Actually, in the context of #if expressions, unrecognized tokens expand to 0 anyway: > After all replacements due to macro expansion and the defined unary > operator have been performed, all remaining identifiers are replaced > with the pp-number 0... > (ISO 9899:1999 6.10.1 #3) Yes, but that generates a warning, and then error via -Werror with some set of compile options that at least one CI run uses. signature.asc Description: PGP signature
looking for properly configured Windows VMs
Attempts to make bss_dgram.c compile with the right IPv6 include for Windows are not going well. Some of the jobs actually die before my test case even runs, but at least, I guess they compile bss_dgram.c Others (the shared ones) seem to fail completely to compile bss_dgram.c I haven't run a compile on DOS since the days of djcpp... I wonder if anyone has VM images with the right OS and compilation tools installed? (I think the license situation would be fine if run on EC2) The day-long cycle, making a change and then waiting for CI to give an opinion is just too slow. (I didn't know WIN32 was still even thing... I guess Windows ME still uses it maybe.) Subject: Re: [openssl/openssl] PR run failed: Windows GitHub CI - bio_dgram uses recvmsg/sendmsg to retrieve destination and set origin address (41cc92c) View results: https://github.com/openssl/openssl/actions/runs/2073285321 Jobs: * minimal (windows-2019) cancelled (12 annotations) * minimal (windows-2022) failed (12 annotations) * plain (windows-2019) cancelled (2 annotations) * plain (windows-2022) failed (1 annotation) * shared (windows-2019, win64, VC-WIN64A enable-fips) failed (1 annotation) * shared (windows-2019, win32, VC-WIN32 --strict-warnings no-fips) cancelled (2 annotations) * shared (windows-2022, win64, VC-WIN64A enable-fips) cancelled (2 annotations) * shared (windows-2022, win32, VC-WIN32 --strict-warnings no-fips) cancelled (2 annotations) signature.asc Description: PGP signature
