[Bug 297667] ecurity/sssd2: Fix sssd.conf path substitution and file mode

[email protected]
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297667

            Bug ID: 297667
           Summary: ecurity/sssd2: Fix sssd.conf path substitution and
                    file mode
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 273915
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=273915&action=edit
Patch

The port passes neither --datadir nor --sysconfdir to configure. Autoconf then
substitutes the shell reference ${prefix}/share verbatim into
src/config/SSSDConfig/__init__.py, where nothing ever expands it. Any consumer
fails with:
[Errno 2] No such file or directory: '${prefix}/share/sssd/sssd.api.conf'

This breaks sss_obfuscate from the port itself, and it makes ipa-server-install
from net/freeipa-server abort. Passing both paths explicitly gives the same
values, just absolute instead of as a reference.

The @sample entry for sssd.conf.sample carries no mode, so pkg creates
sssd.conf with 0644 and sssd refuses to start:
[sssd] [access_check_file] (0x0020): Unexpected access to
'/usr/local/etc/sssd/sssd.conf' by other users
Can't read config: 'File ownership and permissions check failed'

Tested in poudriere (15.1 amd64) and on a running FreeIPA server. A byte
comparison of the old and new package shows identical file lists and no change
to any library, binary or pkg-config file, so the three consumers
(net/freeipa-server, net/slapi-nis, security/sudo) are unaffected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.