Date: Sat, 29 Feb 2020 17:45:39 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 244518] emulators/linux_base-c7: missing ca-certificates Message-ID: <bug-244518-4077-hcl5HgsvVE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244518-4077@https.bugs.freebsd.org/bugzilla/> References: <bug-244518-4077@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244518 Byron Grobe <grobe0ba@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grobe0ba@gmail.com --- Comment #1 from Byron Grobe <grobe0ba@gmail.com> --- <jell48> finally got the traces out with "truss chroot /compat/linux curl https://google.com 2>&1". almost all of the files are found, except for "linux_open("/proc/sys/crypto/fips_enabled",0x0,0666) ERR#-2 'No such file = or directory'". not sure how relevant is that crypto for curl to function (or = is that a real cause)? Recent versions of OpenSSL and other SSL libraries on Linux check for a kernel/userland setup that operates in a FIPS certified mode, which whether= or not it is used, it includes a sysctl visible under /proc/sys/crypto/fips_enabled. When the system is not in this mode, /proc/sys/crypto/fips_enabled should h= ave a content of ASCII 0 (for false), which it should always be under emulation since we don't do FIPS certified crypto under linux emulation. --=20 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-244518-4077-hcl5HgsvVE>