[
https://issues.apache.org/jira/browse/CRYPTO-162?focusedWorklogId=781003&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-781003
]
ASF GitHub Bot logged work on CRYPTO-162:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/22 07:02
Start Date: 14/Jun/22 07:02
Worklog Time Spent: 10m
Work Description: jochenw commented on PR #164:
URL: https://github.com/apache/commons-crypto/pull/164#issuecomment-1154795891
My impression is, that you wish to extend Crypto from a pure random
generator towards a decoding/encoding engine.
While this seems interesting, I am nevertheless opposed to it: The native
parts of Crypto are already a heavy maintenance burden, as they are. Mostly,
due to the need to support multiple binary platforms. (Most of us have
typically a single one, or two at the most.)
So, sorry!
Issue Time Tracking
-------------------
Worklog Id: (was: 781003)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
