Did you do an "nmake clean" after switching to the correct compiler? You need
to get rid of those 32-bit objects, or you'll continue to have a machine-type
mismatch.
--
Michael Wojcik
Rocket Software
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Walt
> From: openssl-users On Behalf Of Dennis
> Clarke via openssl-users
> Sent: Thursday, 30 May, 2024 07:29
>
> OKay, thank you. I guess today is a good day to test on a few oddball
> system architectures. I suspect there are very very few people out there
> running actual HPE Itanium hardware or bi
We recently debugged, and found a workaround for, a GCC [###version]
code-generation error when compiling OpenSSL 3.0.8 for 32-bit on Intel x86.
This error resulted in a use of a misaligned memory operand with a
packed-quadword instruction, producing a SIGSEGV on RedHat 8. (I'm a bit
surprised
> From: Steven_M.irc
> Sent: Thursday, November 24, 2022 21:21
> > This is not true in the general case. There are applications which are
> > available on Linux which do not use the
> > distribution's package manager. There are applications which use their own
> > OpenSSL build, possibly link
> From: openssl-users on behalf of
> Steven_M.irc via openssl-users
> Sent: Monday, November 21, 2022 15:56
> However, I am running Windows 10, and since (unlike Linux) every piece of
> software outside of Windows itself
> needs to be updated individually, I don't know how to track down every
> From: openssl-users On Behalf Of raf via
> openssl-users
> Sent: Friday, 4 November, 2022 18:54
>
> On Wed, Nov 02, 2022 at 06:29:45PM +, Michael Wojcik via openssl-users
> wrote:
>
> >
> > I'm inclined to agree. While there's an argum
> From: openssl-users On Behalf Of Matt
> Caswell
> Sent: Friday, 4 November, 2022 06:43
>
> This looks like something environmental rather than a problem with
> OpenSSL itself. /usr/lib/gcc/x86_64-linux-gnu/8/include-fixed/limits.h
> is clearly a system include file, trying to include some other
> From: Felipe Gasper
> Sent: Thursday, 3 November, 2022 10:43
> >
> > And your description looks wrong anyway: shutdown(SHUT_RD) has
> > implementation-defined behavior for TCP sockets (because TCP does not
> > announce the read side of half-close to the peer), and on Linux causes
> > blocked rec
> From: Felipe Gasper
> Sent: Thursday, 3 November, 2022 08:51
>
> You probably know this, but: On Linux, at least, if a TCP socket close()s
> with a non-empty read buffer, the kernel sends TCP RST to the peer.
Yes, that's a conditional-compliance (SHOULD) requirement from the Host
Requirements
> From: Felipe Gasper
> Sent: Thursday, 3 November, 2022 07:42
>
> It sounds, then like shutdown() (i.e., TCP half-close) is a no-no during a
> TLS session.
Um, maybe. Might generally be OK in practice, particularly with TLSv1.3, which
got rid of some of the less-well-considered ideas of earlie
> From: openssl-users On Behalf Of
> Steven_M.irc via openssl-users
> Sent: Wednesday, 2 November, 2022 17:18
>
> I'm really worried about the vulnerabilities recently found in OpenSSL
> versions 3.0.0 - 3.0.6.
Why? What's your threat model?
> If I understand things correctly (and please do
> c
> From: Felipe Gasper
> Sent: Wednesday, 2 November, 2022 12:46
>
> I wouldn’t normally expect EPIPE from a read operation. I get why it happens;
> it just seems odd. Given that it’s legitimate for a TLS peer to send the
> close_notify and then immediately do TCP close, it also seems like EPIPE i
> From: openssl-users On Behalf Of Phillip
> Susi
> Sent: Wednesday, 2 November, 2022 11:45
>
> The only thing to fix is don't put your compiler in strict C90 mode.
I'm inclined to agree. While there's an argument for backward compatibility,
C99 was standardized nearly a quarter of a century ag
> From: openssl-users On Behalf Of Felipe
> Gasper
> Sent: Wednesday, 26 October, 2022 11:15
>
> I’m seeing that OpenSSL 3, when it reads empty on a socket, sends some
> sort of response, e.g.:
>
> - before read
> [pid 42417] read(7276781]>, "", 5) = 0
> [pid 42417] sendmsg(7276781]>,
> From: openssl-users On Behalf Of ???
> Sent: Friday, 21 October, 2022 02:39
> Subject: Re: openssl-users Digest, Vol 95, Issue 27
Please note the text in the footer of each openssl-users digest message:
> When replying, please edit your Subject line so it is more specific
> than "Re: Cont
> From: openssl-users On Behalf Of David
> Harris
> Sent: Saturday, 22 October, 2022 09:02
>
> I now have wireshark captures showing the exchanges between the working
> instance and the non-working instance respectively; the problem is definitely
> happening after STARTTLS has been issued and dur
> From: David Harris
> Sent: Friday, 21 October, 2022 01:42
>
> On 20 Oct 2022 at 20:04, Michael Wojcik wrote:
>
> > I think more plausible causes of this failure are things like OpenSSL
> > configuration and interference from other software such as an endpoint
> > firewall. Getting SYSCALL from
> From: openssl-users On Behalf Of David
> Harris
> Sent: Wednesday, 19 October, 2022 18:54
>
> Do recent versions of OpenSSL 1.1.1 have dependencies on some Windows
> facility (winsock and wincrypt seem likely candidates) that might work on
> Server 2019 but fail on Server 2012?
OpenSSL on Wind
> From: openssl-users On Behalf Of ???
> Sent: Tuesday, 18 October, 2022 11:58
> I have downloaded perl strawberry, but I have no clue how to get rid of the
> built-in perl that comes in cygwin, and point cygwin to use the strawberry
> perl.
You don't have to remove the Cygwin version of p
> From: רונן לוי
> Sent: Monday, 17 October, 2022 12:03
Send messages to the list, not directly to me.
> And, in which header file am I expected to find the Definition for LONG?
That's a question about the Windows SDK, not OpenSSL.
It's in WinNT.h, per Microsoft's documentation (which is read
> From: רונן לוי
> Sent: Monday, 17 October, 2022 11:12
> see attached file for cygwin details.
I'm afraid I have no comment on that. I merely mentioned that for some OpenSSL
releases, using a POSIXy perl implementation such as Cygwin's to configure
OpenSSL for a Windows build did not work.
> From: רונן לוי
> Sent: Monday, 17 October, 2022 11:16
Please send messages to the list, not to me directly.
> And for the question with regard to the Windows style, are you referring to
> CRLF as
> opposed to LF from linux?
No, to Windows-style file paths, with drive letters and backslashes
> From: openssl-users On Behalf Of ???
> Sent: Saturday, 15 October, 2022 15:48
> I have tried to build openssl using cygwin:
> Both options starts compiling, but end up with error:
> In file included from providers/implementations/storemgmt/winstore_store.c:27:
> /usr/include/w32api/wincry
> From: openssl-users On Behalf Of Dmitrii
> Odintcov
> Sent: Sunday, 2 October, 2022 21:15
>
> This is where the confusion begins: if ‘bar’, the certificate requestor,
> itself
> wants to be a CA (basicConstraints = CA:true),
I assume here you mean bar is going to be a subordinate CA for foo,
> From: openssl-users On Behalf Of Tomas
> Mraz
> Sent: Friday, 30 September, 2022 00:22
>
> unfortunately I do not see anything wrong with the code. Does the
> EVP_DigestVerifyFinal return 0 or negative value? I do not think this
> is a bug in OpenSSL as this API is thoroughly tested and it is h
> From: openssl-users On Behalf Of Michael
> Ströder via openssl-users
> Sent: Sunday, 18 September, 2022 04:27
>
> On 9/18/22 06:09, Philip Prindeville wrote:
> >> On Sep 15, 2022, at 4:27 PM, Michael Wojcik via openssl-users us...@openssl.org> wrote:
> >&
> From: openssl-users On Behalf Of Philip
> Prindeville
> Sent: Thursday, 15 September, 2022 15:41
> I was thinking of the case where the directory containing the keys (as
> configured) is correctly owned, but contains a symlink pointing outside of
> that directory somewhere else... say to a file
> From: openssl-users On Behalf Of Philip
> Prindeville
> Sent: Tuesday, 13 September, 2022 14:17
>
> I'm working on a bug in an application where the application config is given
> the directory path in which to find a key-store, which it then loads.
>
> My issue is this: a regular UNIX file is
> From: openssl-users On Behalf Of Matt
> Caswell
> Sent: Tuesday, 24 May, 2022 07:43
> To: openssl-users@openssl.org
> Subject: Re: using TLS (>1.2) with more than one certificate
>
> On 24/05/2022 13:52, tobias.w...@t-systems.com wrote:
> > I’ve a server application and need to support RSA and
29 matches
Mail list logo
