[
https://issues.apache.org/jira/browse/CRYPTO-162?focusedWorklogId=781121&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-781121
]
ASF GitHub Bot logged work on CRYPTO-162:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/22 11:56
Start Date: 14/Jun/22 11:56
Worklog Time Spent: 10m
Work Description: garydgregory commented on PR #164:
URL: https://github.com/apache/commons-crypto/pull/164#issuecomment-1155085762
Since Crypto is a thin wrapper over OpenSSL, I don't see why we would not
wrap more of its APIs, so this seems ok to me, if there were suitable tests.
Issue Time Tracking
-------------------
Worklog Id: (was: 781121)
Time Spent: 1h 10m (was: 1h)
> openSslCipher support engine
> ----------------------------
>
> Key: CRYPTO-162
> URL: https://issues.apache.org/jira/browse/CRYPTO-162
> Project: Commons Crypto
> Issue Type: New Feature
> Components: Cipher
> Reporter: wenweijian
> Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The engine is the hardware or software implementation used for performing
> cryptographic operations.
>
> Assume we have a hardware device with a super fast implementation of AES. Now
> when we use AES encryption we can set the engine to that hardware device
> (instead of {{{}NULL{}}}), which means that the operations are now computed
> by the hardware device instead of the default OpenSSL software layer.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
