freeipa.git/daemons/ipa-slapi-plugins, branch platform-master FreeIPA project Fix typos 2011-09-07T11:20:42+00:00 Yuri Chornoivan yurchor@ukr.net 2011-09-05T14:30:05+00:00 1785d0a7c1fb5d90945e187b2e94fddf95ead13a Fix "The the" and "classses" in FreeIPA code and messages. https://fedorahosted.org/freeipa/ticket/1480 
Fix "The the" and "classses" in FreeIPA code and messages.

https://fedorahosted.org/freeipa/ticket/1480
ipa-pwd-extop: Allow kadmin to set krb keys 2011-08-26T12:24:50+00:00 Simo Sorce ssorce@redhat.com 2011-07-07T17:30:15+00:00 35e15f6c91be21715d33ae0f06b5629f63289e8f Prevent the ipa-pwd-extop plugin from re-generating keys when kadimn is storing a new set of keys. Only generate the userPassword and sambaXXPassword hashes. Also avoid checking policies in this case and if history is provided avoid regenerating the passwordHistory too. 
Prevent the ipa-pwd-extop plugin from re-generating keys when kadimn is storing
a new set of keys. Only generate the userPassword and sambaXXPassword hashes.
Also avoid checking policies in this case and if history is provided avoid
regenerating the passwordHistory too.
ipa-pwd-extop: Use common password policy code 2011-08-26T12:24:50+00:00 Simo Sorce ssorce@redhat.com 2011-07-01T17:32:57+00:00 7ea0b5d56e2b157d7bcc15610d076e44f02beeda 






ipa-pwd-extop: make encsalt parsing function common
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-22T20:23:52+00:00

7d41e7b4d43d882eb4cc99f0600078e0f34f1774

It is going to be used by the ipa-kdb module too.





It is going to be used by the ipa-kdb module too.







ipa-pwd-extop: Move encoding in common too
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-20T15:55:13+00:00

eed401306c400ae938e2d328de22da6f729c8f3f

Also to be used by ipa-kdb





Also to be used by ipa-kdb







ipa-pwd-extop: Move encryption of keys in common
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-20T14:46:11+00:00

49282290938c735c566c7d0abf57c67b69945cce

This way we can reuse the same code from ipa-kdb later





This way we can reuse the same code from ipa-kdb later







ipa-pwd-extop: Use common krb5 structs from kdb.h
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-20T13:23:37+00:00

b4aab3d98d68bfa79323b216320b1d3dcc1941c9

This removes custom structures and allows easier sharing of code with ipa-kdb





This removes custom structures and allows easier sharing of code with ipa-kdb







ipa-pwd-extop: re-indent code using old style
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-14T15:33:02+00:00

672035cbbac649b74cbe2d8396466d18e3e81130












ipa-pwd-extop: Use the proper mkvno number in keys
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-10T18:24:18+00:00

229b9a209cabc0f9dbdd630c0753cb565fab99c5

Setting 0 will work as MIT KDCs assume the current master key when that is
found. But it is a legacy compatibility mode and we should instead set the
proper mkvno number on keys so changeing master key becomes possible w/o
having to do a dump reload and stopping the service. This is especially
important in replicated environments.





Setting 0 will work as MIT KDCs assume the current master key when that is
found. But it is a legacy compatibility mode and we should instead set the
proper mkvno number on keys so changeing master key becomes possible w/o
having to do a dump reload and stopping the service. This is especially
important in replicated environments.







ipa-pwd-extop: do not append mkvno to krbExtraData
2011-08-26T12:24:49+00:00

Simo Sorce
ssorce@redhat.com

2011-06-02T15:59:51+00:00

5746bbe92a82946a6fa8d8db2be54e075564535d

mkvno is actually available as part of the key material.
There is no need to store it in the krbExtraData field as it is unused there.





mkvno is actually available as part of the key material.
There is no need to store it in the krbExtraData field as it is unused there.