sssd - System Security Services Daemon

Age	Commit message (Collapse)	Author	Files	Lines
2012-05-10	Filter out IP addresses inappropriate for DNS forward records	Jakub Hrozek	1	-1/+57
	https://fedorahosted.org/sssd/ticket/949
2012-05-01	execv, excvp and exec_child never return EOK	Stef Walter	1	-5/+3
	* So don't need to handle that case
2012-03-29	Return correct resolv_status on resolver timeout	Jakub Hrozek	1	-1/+6
	https://fedorahosted.org/sssd/ticket/1274
2012-02-23	Save errno value before calling DEBUG	Jakub Hrozek	1	-2/+4

2012-02-21	Don't give memory context in confdb where not needed	Jan Zeleny	1	-1/+1

2012-01-17	IPA: Detect nsupdate support for the realm directive	Stephen Gallagher	1	-14/+40
	For older platforms, do not add the 'realm' line in the update message
2011-12-19	Move child_common routines to util	Stephen Gallagher	1	-1/+1

2011-11-23	New IPA ID context	Jan Zeleny	1	-8/+10

2011-11-22	Cleanup: Remove unused parameters	Jakub Hrozek	1	-2/+1

2011-08-25	IPA dyndns: do not segfault if the server cannot be resolved	Jakub Hrozek	1	-4/+2
	https://fedorahosted.org/sssd/ticket/963
2011-08-01	Remove incorrect private variable	Stephen Gallagher	1	-1/+1
	This caused no ill effects, since it wasn't used in the callback. However, it is a layering violation (especially since req is freed in the callback)
2011-07-11	Check DNS records before updating	Jakub Hrozek	1	-21/+463
	https://fedorahosted.org/sssd/ticket/802
2011-07-05	ipa_dyndns: Use sockaddr_storage for storing IP addresses	Jakub Hrozek	1	-12/+17
	https://fedorahosted.org/sssd/ticket/915
2011-06-21	Log nsupdate message	Jakub Hrozek	1	-0/+3
	https://fedorahosted.org/sssd/ticket/893
2011-03-03	Fixes for dynamic DNS update	Sumit Bose	1	-16/+87
	The current code assumed that only one server is given in the ipa_server config option and fails if multiple servers were given. To fix this nsupdate is first called without a server name assuming that nsupdate is able to find the name of the master DNS server of the zone by reading the SOA record. If this fails the IP address of the currently active LDAP server is used and nsupdate is called again. If there is no default realm given in /etc/krb5.conf nsupdate start trying to find a realm based on the DNS domain which might lead to wrong results. To be on the safe side the realm was added to the message send to nsupdate.
2010-07-09	Use new LDAP connection framework in IPA dynamic DNS forwarder.	eindenbom	1	-38/+122

2010-05-27	Remove signal event if child was terminated by a signal	Sumit Bose	1	-1/+8

2010-05-16	Add dynamic DNS updates to FreeIPA	Stephen Gallagher	1	-0/+580
	This adds two new options: ipa_dyndns_update: Boolean value to select whether this client should automatically update its IP address in FreeIPA DNS. ipa_dyndns_iface: Choose an interface manually to use for updating dynamic DNS. Default is to use the interface associated with the LDAP connection to FreeIPA. This patch supports A and AAAA records. It relies on the presence of the nsupdate tool from the bind-utils package to perform the actual update step. The location of this utility is set at build time, but its availability is determined at runtime (so clients that do not require dynamic update capability do not need to meet this dependency).
2010-05-07	Revert "Add dynamic DNS updates to FreeIPA"	Stephen Gallagher	1	-580/+0
	This reverts commit 973b7c27c0b294b8b2f120296f64c6a3a36e44b7. While this patch applied cleanly, it was uncompilable. Reverting until it can be properly merged.
2010-05-07	Add dynamic DNS updates to FreeIPA	Stephen Gallagher	1	-0/+580
	This adds two new options: ipa_dyndns_update: Boolean value to select whether this client should automatically update its IP address in FreeIPA DNS. ipa_dyndns_iface: Choose an interface manually to use for updating dynamic DNS. Default is to use the interface associated with the LDAP connection to FreeIPA. This patch supports A and AAAA records. It relies on the presence of the nsupdate tool from the bind-utils package to perform the actual update step. The location of this utility is set at build time, but its availability is determined at runtime (so clients that do not require dynamic update capability do not need to meet this dependency).