| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
We were using the wrong principal in the s4u2proxy case.
Fixes: https://fedorahosted.org/freeipa/ticket/2504
|
|
|
|
|
|
|
| |
This was causing the failure count interval to not be applied so
the failure count was never reset to 0.
https://fedorahosted.org/freeipa/ticket/2540
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some of these are not real defects, because we are guaranteed to have valid
context in some functions, and checks are not necessary.
I added the checks anyway in order to silence Coverity on these issues.
One meleak on error condition was fixed in
daemons/ipa-kdb/ipa_kdb_pwdpolicy.c
Silence errors in ipa-client/ipa-getkeytab.c, the code looks wrong, but it is
actually fine as we count before hand so we never actually use the wrong value
that is computed on the last pass when p == 0
Fixes: https://fedorahosted.org/freeipa/ticket/2488
|
|
|
|
|
| |
We need to check for a matching acl only if one match hasn't already been
found, otherwise results are unpredictable and order dependent.
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2393
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2343
|
|
|
|
|
|
|
| |
These definitions were needed during development to be a le to build against
krb5 version < 1.10
These function headers and defintions are now available in 1.10 that is a hard
dependency for freeipa 3.0, so we can safely drop them.
|
| |
|
|
|
|
| |
This avoids one useless search if we already have the entry_dn.
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2334
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2170
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch requires a forthcoming change in MIT libraries which allows to pass
NULL for the server_key to the krb5_pac_verify() function.
In most cases we should always only check the KDC checksum to verify the PAC
validity.
The only exception is when we are releasing a ticket to a client from another
realm. In this case the only signature we can check is the server checksum, and
we use the cross-realm key to validate in this case.
The previous code was working for normal cases because the kdc uses the same
key to create the server and the kdc checksum for a TGT, but that is not true
for evidence tickets (s4u2proxy) or cross-realm TGTs.
Fixes: https://fedorahosted.org/freeipa/ticket/2169
|
| |
|
| |
|
|
|
|
|
| |
Allow to deref more than one attribute.
The attrs searched are the same for all deref attributes at this time.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2122
|
|
|
|
| |
Fake code for now, to be rebased later
|
| |
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
| |
|
|
|
|
|
|
|
|
|
| |
We were not searching for objectclass so the test to se if a user had the
posixAccount attribute was failing and the user was not marked as ipa_user.
This in turn caused us to not synchronize legacy hashes by not trying to store
the userPassword attribute.
Fixes: https://fedorahosted.org/freeipa/ticket/1820
|
|
|
|
|
|
|
|
|
|
|
| |
Expiration time should be enforced as per policy only for users and only when a
password change occurs, ina ll other cases we should just let kadmin decide
whther it is going to set a password expiration time or just leave it empty.
In general service tickts have strong random passwords so they do not need a
password policy or expiration at all.
https://fedorahosted.org/freeipa/ticket/1839
|
|
|
|
|
|
|
| |
We do the policy check so we are the only one that can calculate the new
pwd espiration time.
Fixes: https://fedorahosted.org/freeipa/ticket/1793
|
|
|
|
|
|
|
| |
Although the proper values for booleans from LDAP should be only uppercase,
389ds does allow wrong cased values without complaining. And we still have some
places where the wrong case is used.
Avoid getting frustrating errors when reading these values out.
|
|
|
|
| |
Use default policy for new principals created by kadmin
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Initialize module also on ipadb_create invocation. This is what
kdb5_util expects.
|
|
|
|
| |
limit exported symbols only to the ones actually needed by krb5kdc
|
|
|