[SSSD] [PATCH] Ensure the SSSDConfig creates sssd.conf with the correct mode

Stephen Gallagher sgallagh at redhat.com
Fri Mar 19 18:09:39 UTC 2010


-----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 SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkujveMACgkQeiVVYja6o6OHhACfaW5sz1rZ9VEzzxSZDx61lN9U
z9gAnirpI/Lv65znOLyOuEGoJD21KT3T
=FCDq
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Ensure-the-SSSDConfig-creates-sssd.conf-with-the-cor.patch
Type: text/x-patch
Size: 4898 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20100319/03619d33/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Ensure-the-SSSDConfig-creates-sssd.conf-with-the-cor.patch.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20100319/03619d33/attachment.sig>


More information about the sssd-devel mailing list