[jira] Resolved: (SHIRO-34) Cipher refactoring

["Les Hazlewood (JIRA)" <ji...@apache.org>]

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

Les Hazlewood resolved SHIRO-34.
--------------------------------

         Assignee: Les Hazlewood
    Fix Version/s: 1.0.0
       Resolution: Fixed

The Cipher interface has been renamed to CipherService in the 1.0 release to reflect its stateless nature.  Ciphers retain state, so our previous name was not the best.  CipherService as a name better represents its function.

> Cipher refactoring
> ------------------
>
>                 Key: SHIRO-34
>                 URL: https://issues.apache.org/jira/browse/SHIRO-34
>             Project: Shiro
>          Issue Type: Task
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>             Fix For: 1.0.0
>
>
> The Cipher interface should be refactored to have two methods:
> byte[] encrypt( byte[] raw);
> and
> byte[] decrypt( byte[] encrypted);
> Since almost all usages of Ciphers in JSecurity don't expect the key to change across method invocations.  But for the few cases that do require such a requirement, we need to move the existing two methods into a new interface:
> VariableKeyCipher or DynamicKeyCipher that contains the existing two methods:
> byte[] encrypt( byte[] raw, byte[] encryptionKey);
> and
> byte[] decrypt( byte[] encrypted, byte[] decryptionKey);

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