Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
bye, Sumit
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in.
simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.
EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2
SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in. simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
bye, Sumit
On Thu, Feb 25, 2010 at 08:50:43PM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in. simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
Hi,
I forgot to include a hunk in the Makefile.am patch. New version attached.
bye, Sumit
Sumit Bose wrote:
On Thu, Feb 25, 2010 at 08:50:43PM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in. simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
Hi,
I forgot to include a hunk in the Makefile.am patch. New version attached.
bye, Sumit
Should allowing access override denying access in the interests of good security practices? e.g., if I'm in both Allow and Deny lists, I'd expect to be denied access.
On Thu, Mar 04, 2010 at 12:38:43PM +1000, David O'Brien wrote:
Sumit Bose wrote:
On Thu, Feb 25, 2010 at 08:50:43PM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in. simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
Hi,
I forgot to include a hunk in the Makefile.am patch. New version attached.
bye, Sumit
Should allowing access override denying access in the interests of good security practices? e.g., if I'm in both Allow and Deny lists, I'd expect to be denied access.
If both list contain some user names it does not makes sense to evaluate both list, because if you are not in the Allow list you will be denied anyway. We have decided to ignore the Deny list if the Allow list is defined and not the other way round, because this way it is easier to deny users. E.g. think of a "typical" environment with 50000 users. If you want to allow only 10 users access to your machine you put these 10 in the Allow list and you are done. Otherwise you would have to put 49990 users in the Deny List.
It would be possible to add an order parameter and a default rule, but this would make the configuration much more complex and error prone. If more complex access control is needed it should not be done on the client but e.g. with IPA HBAC.
bye, Sumit
--
David O'Brien Red Hat Asia Pacific Pty Ltd
He who asks is a fool for five minutes, but he who does not ask remains a fool forever." ~ Chinese proverb _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel
On Mon, Mar 01, 2010 at 11:04:25AM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 08:50:43PM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
NAME sssd-simple - the configuration file for SSSD's 'simple' access-control provider
DESCRIPTION This manual page describes the configuration of the simple access-control provider for sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT” section of the sssd.conf(5) manual page.
The simple access provider grants or denies access based on an access or deny list of user names. Here the following rules apply:
· If both lists are empty, access is granted
· If simple_allow_users is set, only users from this list are allowed access. This setting supersedes the simple_deny_users list (which would be redundant.
· If the simple_allow_users list is empty, users are allowed access unless they appear in the simple_deny_users list
CONFIGURATION OPTIONS Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration of an SSSD domain.
simple_allow_users (string) Comma separated list of users who are allowed to log in. simple_deny_users (string) Comma separated list of users who are rejected if simple_allow_users is not set.EXAMPLE The following example assumes that SSSD is correctly configured and example.com is one of the domains in the [sssd] section. This examples shows only the simple access provider-specific options.
[domain/example.com] access_provider = simple simple_allow_users = user1, user2SEE ALSO sssd.conf(5), sssd(8)
AUTHORS The SSSD upstream - http://fedorahosted.org/sssd
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
Hi,
I forgot to include a hunk in the Makefile.am patch. New version attached.
bye, Sumit
rebased version attached.
bye, Sumit
On Mon, Mar 08, 2010 at 02:07:00PM +0100, Sumit Bose wrote:
On Mon, Mar 01, 2010 at 11:04:25AM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 08:50:43PM +0100, Sumit Bose wrote:
On Thu, Feb 25, 2010 at 01:27:34PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/25/2010 12:31 PM, Sumit Bose wrote:
Hi,
this is the second try to fix #392. This patch adds a new provider called simple wuth na access target which can allow/deny access based on a list of user names.
Nack.
You didn't update the SSSDConfigTest.py. It's failing.
The manpages are very hard to follow. Might I suggest that they read:
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/
iEYEARECAAYFAkuGwRYACgkQeiVVYja6o6NDHQCeOpet+8kppGGyxVUkhCm+Za4I J74AoJN6Koz74cdXKsNEz6qE0kQhy9D8 =7923 -----END PGP SIGNATURE-----
new version attached.
Hi,
I forgot to include a hunk in the Makefile.am patch. New version attached.
bye, Sumit
rebased version attached.
This new version makes it a configuration error if both lists are defined in the config file.
bye, Sumit
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/08/2010 08:40 AM, Sumit Bose wrote:
This new version makes it a configuration error if both lists are defined in the config file.
bye, Sumit
Nack (though these are nitpicks)
I'd prefer it if the simple provider had its own subdirectory like the LDAP, KRB5 and IPA providers.
Also, I'd rather that the interface for simple_access_check was passed the simple_ctx, rather than the allow_users and deny_users lists. This way, if we decide to add an additional feature (like resolution order), we're already carrying anything that the context might require.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
On Mon, Mar 08, 2010 at 11:50:38AM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/08/2010 08:40 AM, Sumit Bose wrote:
This new version makes it a configuration error if both lists are defined in the config file.
bye, Sumit
Nack (though these are nitpicks)
I'd prefer it if the simple provider had its own subdirectory like the LDAP, KRB5 and IPA providers.
Also, I'd rather that the interface for simple_access_check was passed the simple_ctx, rather than the allow_users and deny_users lists. This way, if we decide to add an additional feature (like resolution order), we're already carrying anything that the context might require.
new version attached.
bye, Sumit
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/
iEYEARECAAYFAkuVKt4ACgkQeiVVYja6o6MG9gCfdoX+aOs9QghSnGvoIhJhA4bp KJQAoJPWFEevho5mxv3lJ5LPLWKAg4vD =A0CV -----END PGP SIGNATURE----- _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/08/2010 03:37 PM, Sumit Bose wrote:
On Mon, Mar 08, 2010 at 11:50:38AM -0500, Stephen Gallagher wrote: On 03/08/2010 08:40 AM, Sumit Bose wrote:
This new version makes it a configuration error if both lists are defined in the config file.
bye, Sumit
Nack (though these are nitpicks)
I'd prefer it if the simple provider had its own subdirectory like the LDAP, KRB5 and IPA providers.
Also, I'd rather that the interface for simple_access_check was passed the simple_ctx, rather than the allow_users and deny_users lists. This way, if we decide to add an additional feature (like resolution order), we're already carrying anything that the context might require.
new version attached.
bye, Sumit
Ack.
- -- 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/08/2010 05:07 PM, Stephen Gallagher wrote:
On 03/08/2010 03:37 PM, Sumit Bose wrote:
On Mon, Mar 08, 2010 at 11:50:38AM -0500, Stephen Gallagher wrote: On 03/08/2010 08:40 AM, Sumit Bose wrote:
This new version makes it a configuration error if both lists are defined in the config file.
bye, Sumit
Nack (though these are nitpicks)
I'd prefer it if the simple provider had its own subdirectory like the LDAP, KRB5 and IPA providers.
Also, I'd rather that the interface for simple_access_check was passed the simple_ctx, rather than the allow_users and deny_users lists. This way, if we decide to add an additional feature (like resolution order), we're already carrying anything that the context might require.
new version attached.
bye, Sumit
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
-
David O'Brien -
Stephen Gallagher -
Sumit Bose