[Bug 206220] mail/mutt: GSSAPI not using Heimdal from Ports, leads to environ corruption
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jan 14 01:57:24 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206220
Bug ID: 206220
Summary: mail/mutt: GSSAPI not using Heimdal from Ports, leads
to environ corruption
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: freebsd at phil.spodhuis.org
CC: Udo.Schweigert at siemens.com
Flags: maintainer-feedback?(Udo.Schweigert at siemens.com)
CC: Udo.Schweigert at siemens.com
Created attachment 165535
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165535&action=edit
mail/mutt Makefile patch for GSSAPI Uses system
mail/mutt rolls its own GSSAPI handling system, looking for installed
libraries, rather than employing the "Uses" knobs (which probably post-date the
mutt Port's GSSAPI support).
When linking against OpenSSL from Ports, this results in one mutt process
pulling in both libcrypto.so.8 from Ports and libcrypto.so.7 from the base
system (FreeBSD 10.1), leading to environ corruption problems when running
external commands, which complain at startup (libc routines detect the
corruption). These look like:
sh: environment corrupt; missing value for SOME_VAR
and can be seen when, eg, viewing a PGP-signed mail with GnuPG integration
turned on.
This patch switches mail/mutt to use the GSSAPI "Uses" system, and has been
verified to work for me with Heimdal from Ports. I haven't tested the other
variants, but they're textbook copy/paste.
I previously reported this via mail to the port maintainer on 2015-05-24 (at
which time, the maintainer was out-of-office) and haven't chased between then
and now.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list