You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2009/03/06 14:59:57 UTC

[jira] Moved: (KI-33) Cipher refactoring

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

Alan Cabrera moved JSEC-36 to KI-33:
------------------------------------

        Fix Version/s:     (was: 1.0)
          Component/s:     (was: Cryptography & Hashing)
    Affects Version/s:     (was: 1.0)
                  Key: KI-33  (was: JSEC-36)
              Project: Ki  (was: JSecurity)

> Cipher refactoring
> ------------------
>
>                 Key: KI-33
>                 URL: https://issues.apache.org/jira/browse/KI-33
>             Project: Ki
>          Issue Type: Task
>            Reporter: Les Hazlewood
>
> 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.