Summary: | net/netatalk3: installation problem due pam config missing in files | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | nick.rozhkov |
Component: | Individual Port(s) | Assignee: | Joe Marcus Clarke <marcus> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | feld, marcus, ports-secteam |
Priority: | --- | Flags: | koobs:
maintainer-feedback?
koobs: merge-quarterly? |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
nick.rozhkov
2016-10-10 01:05:45 UTC
Fixed in the latest commit. A commit references this bug: Author: marcus Date: Mon Oct 10 03:46:59 UTC 2016 New revision: 423633 URL: https://svnweb.freebsd.org/changeset/ports/423633 Log: * Fix PAM installation [1] * Fix build with mDNSResponder [2] PR: 213349 [1] 213350 [2] Changes: head/net/netatalk3/Makefile head/net/netatalk3/files/netatalk.pam head/net/netatalk3/pkg-message Many thanks for quick fix& Just checked it but netatalk.pam should contain: #%PAM-1.0 auth include system account include system password include system session include system Because the user can't get access to shares with his unix account in case when content of pam: netatalk auth required pam_unix.so try_first_pass netatalk account required pam_unix.so try_first_pass netatalk session required pam_permit.so Assign to maintainer and correctly set summary (which would have ensured the former). Also, revision 423633 (see comment 2) and any subsequent commit after re-opening (comment 3) should be MFH'd to the latest quarterly branch Not sure how ports-secteam was added to this, but I have a proper fix. There was a rollback due to concerns of overwriting PAM configs, but PAM option must certainly have been broken as pkg-plist was not altered to remove it. By using @sample it will avoid overwriting anyone's custom pam config. A commit references this bug: Author: feld Date: Tue Oct 18 17:45:48 UTC 2016 New revision: 424189 URL: https://svnweb.freebsd.org/changeset/ports/424189 Log: net/netatalk3: Fix PAM option Previous rollback of PAM changes didn't update pkg-plist, so the PAM option was broken. By using @sample if PAM option is enabled we can install a default PAM config that inherits the system PAM configuration while allowing custom configs to remain untouched. PR: 213349 MFH: 2016Q4 Changes: head/net/netatalk3/Makefile head/net/netatalk3/files/pam.conf head/net/netatalk3/pkg-message head/net/netatalk3/pkg-plist I'm actually going to cancel the MFH to 2016Q4 as this version wasn't in quarterly. |