sssd2.git/src/db/sysdb.c, branch sssd-1-8

sysdb: try dealing with binary-content attributes

2013-02-26T16:22:16+00:00

https://fedorahosted.org/sssd/ticket/1818

I have here a LDAP user entry which has this attribute

	loginAllowedTimeMap::
	 AAAAAAAAAP///38AAP///38AAP///38AAP///38AAP///38AAAAAAAAA

In the function sysdb_attrs_add_string(), called from
sdap_attrs_add_ldap_attr(), strlen() is called on this blob, which is
the wrong thing to do. The result of strlen is then used to populate
the .v_length member of a struct ldb_val - and this will set it to
zero in this case. (There is also the problem that there may not be
a '\0' at all in the blob.)

Subsequently, .v_length being 0 makes ldb_modify(), called from
sysdb_set_entry_attr(), return LDB_ERR_INVALID_ATTRIBUTE_SYNTAX. End
result is that users do not get stored in the sysdb, and programs like
`id` or `getent ...` show incomplete information.

The bug was encountered with sssd-1.8.5. sssd-1.5.11 seemed to behave
fine, but that may not mean that is the absolute lower boundary of
introduction of the problem.

SYSDB: Make sysdb_attrs_get_el_int() public

2012-08-21T10:33:15+00:00

Also rename it to sysdb_attrs_get_el_ext()

Save alias of the primary name, too

2012-03-21T15:22:39+00:00

SYSDB: Save only lowercased aliases in case-insensitive domains

2012-03-16T18:06:50+00:00

https://fedorahosted.org/sssd/ticket/1253

SYSDB: index sudoUser

2012-02-01T01:30:25+00:00

Most of the the searches in the Sudo responder include the sudoUser
attribute. Indexing it will make the responder faster.

SYSDB: Add sysdb_attrs_get_uint16_t

2012-01-31T14:37:40+00:00

SYSDB: Add indexes for servicePort and serviceProtocol

2012-01-27T14:02:01+00:00

SYSDB: Redundant check is redundant.

2012-01-21T17:47:57+00:00

Coverity 12480

sysdb_get_bool() and sysdb_get_bool() functions

2012-01-17T16:38:16+00:00

SUDO Integration review issues

2012-01-17T16:38:15+00:00