-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Previously, if the output file did not previously exist, the SSSDConfig API would create the new sssd.conf with the default umask. This would mean that it would not be loadable by the SSSD.
With this patch, we enforce the mode restrictions on the config API.
This is a blocker for authconfig.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/19/2010 07:09 PM, Stephen Gallagher wrote:
Previously, if the output file did not previously exist, the SSSDConfig API would create the new sssd.conf with the default umask. This would mean that it would not be loadable by the SSSD.
With this patch, we enforce the mode restrictions on the config API.
This is a blocker for authconfig.
ACK
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/22/2010 08:23 AM, Jakub Hrozek wrote:
On 03/19/2010 07:09 PM, Stephen Gallagher wrote:
Previously, if the output file did not previously exist, the SSSDConfig API would create the new sssd.conf with the default umask. This would mean that it would not be loadable by the SSSD.
With this patch, we enforce the mode restrictions on the config API.
This is a blocker for authconfig.
ACK
Pushed to master and 1-1-0
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
sssd-devel@lists.fedorahosted.org
-
Jakub Hrozek -
Stephen Gallagher