You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/12/13 08:31:07 UTC

[jira] Updated: (DIRKRB-5) Support Kerberos key provisioning (export)

     [ https://issues.apache.org/jira/browse/DIRKRB-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRKRB-5:
-----------------------------------

    Fix Version/s: 2.0.0-RC2

> Support Kerberos key provisioning (export)
> ------------------------------------------
>
>                 Key: DIRKRB-5
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-5
>             Project: Directory Kerberos
>          Issue Type: New Feature
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>             Fix For: 2.0.0-RC2
>
>
> Today we have no easy way to get Kerberos keys out of the directory.  We should develop a client that uses LDAP to read keys from the directory and write them to a keytab file.  Authentication and message privacy would use the SASL GSSAPI mechanism.
> Additionally, to prevent a client from reading all the keys in the directory with a compromised administrative account, the server needs to generate a new random key on each read and increment the key version number (kvno).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.