Ralph Seichter

I added a local workaround to my ebuild, but it relies on the user specifying a USE flag, which is quite inelegant.

I found a better workaround for my Gentoo Linux ebuild that does not depend on the user knowing how libncurses was built, but overall it would be nice to have...

> This has been "fixed" in a newer version of the Mercury compiler. (not a real bug) Are you referring to Mercury's [issue 379](https://bugs.mercurylang.org/view.php?id=379)? This was supposedly "fixed in commit...

I ran into the same issue. NGINX and OpenLDAP running on the same host, the latter only providing a Unix domain socket for access, so "ldap:" and "ldaps:" are currently...

@davama Thanks a lot for pointing out authelia. It looks very interesting, and given that it is actively maintained, it might be the better choice.

We need `UserID opendkim:dkimsocket` because this is currently the only way to specify a group (shared with the MTA) for the local socket file. Alas, if we use this setting,...

> Why `UserID opendkim` does not help? As I already wrote, we need to specify the group for the local socket, and that can only be done using `UserID opendkim:dkimsocket`....

> You wrote, that with just UserId opendkim the process has two runtime groups and this implies that the process can access both keys and socket. If no group is...

> The primary group is shared with the socket file, the secondary group is shared with the dkim key files. How difficult would it be to add a config parameter...

Thanks, but like I already wrote, adding workarounds for multiple init systems is not a practical solution. I hope @mskucherawy will eventually comment on this issue.