Date: Thu, 20 Mar 2025 20:05:23 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 285565] security/p5-Net-SSLeay 1.94 fails to find specific constants that IO::Socket::SSL needs Message-ID: <bug-285565-14331@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285565 Bug ID: 285565 Summary: security/p5-Net-SSLeay 1.94 fails to find specific constants that IO::Socket::SSL needs Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: perl@FreeBSD.org Reporter: dave@jetcafe.org Flags: maintainer-feedback?(perl@FreeBSD.org) Assignee: perl@FreeBSD.org (for real this time, apologies about the last snafu) On FreeBSD 13 I've built p5-Net-SSLeay against 2025Q1 (and LibreSSL 4.0) recently. We've discovered an issue with this build and IO::Socket::SSL. The issue can be illustrated by this perl one-liner: > perl -MNet::SSLeay -e 'eval { $x = Net::SSLeay::SSL3_MT_MESSAGE_HASH() }; print "[$x][$@]\n";' [][Your vendor has not defined SSLeay macro SSL3_MT_MESSAGE_HASH at -e line 1. ] This is an example of "correct" behavior: > perl -MNet::SSLeay -e 'eval { $x = Net::SSLeay::SSL3_VERSION() }; print "[$x][$@]\n"; [768][] No clue as to any responsible upstream party. At first I thought that the constant is no longer supported by LibreSSL and hence not included, but then I did this > strings /usr/local/lib/perl5/site_perl/mach/5.36/auto/Net/SSLeay/SSLeay.so | grep SSL3_MT_MESSAGE_HASH and it found that string. Not quite sure how to proceed from here. Thanks in advance for any cogent replies. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285565-14331>