You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Enrique Rodriguez (JIRA)" <ji...@apache.org> on 2005/09/14 18:09:55 UTC

[jira] Updated: (DIRKERBEROS-4) Refactor domain objects to better encapsulate crypto behavior

     [ http://issues.apache.org/jira/browse/DIRKERBEROS-4?page=all ]

Enrique Rodriguez updated DIRKERBEROS-4:
----------------------------------------

    Fix Version: 0.5.1
                     (was: 0.4.0)
    Description: 
We currently have the following domain objects, which either may be in an encrypted or decrypted state:

EncASRepPart
EncTGSRepPart
AuthorizationData
EncryptedTimestamp
Authenticator
Ticket

Currently, the AS or TGS perform crypto operations on these objects, in 12 places.  I would like to better encapsulate this behavior, along the lines of how jGSS provides simple wrap and unwrap operations.  I should be able to move this behavior into 1 encrypt and 1 decrypt operation.


  was:
We currently have the following domain objects, which either may be in an encrypted or decrypted state:

EncASRepPart
EncTGSRepPart
AuthorizationData
EncryptedTimestamp
Authenticator
Ticket

Currently, the AS or TGS perform crypto operations on these objects, in 12 places.  I would like to better encapsulate this behavior, along the lines of how jGSS provides simple wrap and unwrap operations.  I should be able to move this behavior into 1 encrypt and 1 decrypt operation.


    Environment: 

> Refactor domain objects to better encapsulate crypto behavior
> -------------------------------------------------------------
>
>          Key: DIRKERBEROS-4
>          URL: http://issues.apache.org/jira/browse/DIRKERBEROS-4
>      Project: Directory Kerberos
>         Type: Improvement
>   Components: Kerberos Protocol Provider
>     Reporter: Enrique Rodriguez
>     Assignee: Enrique Rodriguez
>     Priority: Minor
>      Fix For: 0.5.1

>
> We currently have the following domain objects, which either may be in an encrypted or decrypted state:
> EncASRepPart
> EncTGSRepPart
> AuthorizationData
> EncryptedTimestamp
> Authenticator
> Ticket
> Currently, the AS or TGS perform crypto operations on these objects, in 12 places.  I would like to better encapsulate this behavior, along the lines of how jGSS provides simple wrap and unwrap operations.  I should be able to move this behavior into 1 encrypt and 1 decrypt operation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira