[ http://issues.apache.org/jira/browse/DIRKERBEROS-4?page=all ]
Enrique Rodriguez closed DIRKERBEROS-4:
---------------------------------------
Resolution: Fixed
The primary goal of improving exception handling by consoliding error-prone
seal() and unseal() operations from multiple places has been achieved.
Committed to kerberos-common on revisions 280934, 280935, 280936, and 280945.
Committed to kerberos-protocol on revision 280958.
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280934
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280935
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280936
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280945
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280958
> 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
