Date: Tue, 21 Jul 2020 14:14:36 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 244648] security/samhain: update to 4.4.1 Message-ID: <bug-244648-7788-z07pON1XMv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244648-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-244648-7788@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=3D244648 --- Comment #3 from Greg Veldman <freebsd@gregv.net> --- This appears to be an upstream bug. Between 4.3 and 4.4, Samhain added sup= port for OpenBSD signify to sign the database. Because of that, the samhainadmi= n.pl script was split out into two variants, one for GnuPG and one for signify. = The configure script contains logic to figure out which one is actually in use = and copy it to the actual samhainadmin.pl script, which the build process expec= ts to be present with the network server option: +if test "x${mysignify}" !=3D x +then + cp -a scripts/samhainadmin-sig.pl scripts/samhainadmin.pl +fi +if test "x${mygpg}" !=3D x +then + cp -a scripts/samhainadmin-gpg.pl scripts/samhainadmin.pl +fi + + The problem is the default port build options don't use GnuPG. Based on th= at configure logic, in this case neither variant gets copied to samhainadmin.p= l, which breaks the install-program make target. I've created an updated patch which adds a fix to the configure script to d= eal with this case. I'm not sure if using server mode without either GnuPG or signify is an unsupported configuration, but I'll also submit this upstream= to see if this can be fixed there. --=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-244648-7788-z07pON1XMv>