sssd - System Security Services Daemon

Age	Commit message (Collapse)	Author	Files	Lines
2013-01-08	SYSDB: Split a function to read all SELinux maps	Jakub Hrozek	1	-23/+43

2012-09-13	SELinux: Always use the default if it exists on the server	Jakub Hrozek	1	-2/+9
	https://fedorahosted.org/sssd/ticket/1513 This is a counterpart of the FreeIPA ticket https://fedorahosted.org/freeipa/ticket/3045 During an e-mail discussion, it was decided that * if the default is set in the IPA config object, the SSSD would use that default no matter what * if the default is not set (aka empty or missing), the SSSD would just use the system default and skip creating the login file altogether
2012-09-13	DB: Always write the SELinux object to sysdb	Jakub Hrozek	1	-70/+8
	There's no point in checking if the object already exists because we always wipe the whole sysdb subtree. We were also immediatelly cancelling the transaction because we'd jump to goto, even though it was with EOK.
2012-09-04	Unify usage of sysdb transactions (part 2).	Michal Zidek	1	-13/+15

2012-08-16	Only create the SELinux login file if there are mappings on the server	Jakub Hrozek	1	-6/+1
	https://fedorahosted.org/sssd/ticket/1455 In case there are no rules on the IPA server, we must simply avoid generating the login file. That would make us fall back to the system-wide default defined in /etc/selinux/targeted/seusers. The IPA default must be only used if there are rules on the server, but none matches.
2012-07-20	Fix sysdb_search_selinux_usermap_by_username return value	Jakub Hrozek	1	-0/+1
	There was a logic bug in sysdb_search_selinux_usermap_by_username that resulted in returning the value the variable "ret" had after the last call to sysdb_attrs_get_uint32_t, which in cases the last rule processed did not have the requested attributes led to using the default user context.
2012-07-18	Fix uninitialized values	Nick Guay	1	-2/+2
	https://fedorahosted.org/sssd/ticket/1379
2012-07-18	SYSDB: Delete SELinux mappings	Jakub Hrozek	1	-0/+17

2012-07-18	Modify priority evaluation in SELinux user maps	Jan Zeleny	1	-1/+33
	The functionality now is following: When rule is being matched, its priority is determined as a combination of user and host specificity (host taking preference). After the rule is matched in provider, only its host priority is stored in sysdb for later usage. When rules are matched in the responder, their user priority is determined. After that their host priority is retrieved directly from sysdb and sum of both priorities is user to determine whether to use that rule or not. If more rules have the same priority, the order given in IPA config is used. https://fedorahosted.org/sssd/ticket/1360 https://fedorahosted.org/sssd/ticket/1395
2012-05-02	SYSDB: return EOK if empty message is passed into get_rm_msg	Jakub Hrozek	1	-0/+1
	If the code never entered the loop in get_rm_message, we would return arbitrary return value.
2012-02-06	Added some SELinux-related sysdb routines	Jan Zeleny	1	-0/+471