You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by GitBox <gi...@apache.org> on 2022/06/13 12:26:43 UTC
[GitHub] [commons-crypto] wenwj0 opened a new pull request, #164: CRYPTO-162 openSslCipher support engine
wenwj0 opened a new pull request, #164:
URL: https://github.com/apache/commons-crypto/pull/164
https://issues.apache.org/jira/projects/CRYPTO/issues/CRYPTO-162
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [commons-crypto] jochenw commented on pull request #164: CRYPTO-162 openSslCipher support engine
Posted by GitBox <gi...@apache.org>.
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!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [commons-crypto] wenwj0 closed pull request #164: CRYPTO-162 openSslCipher support engine
Posted by GitBox <gi...@apache.org>.
wenwj0 closed pull request #164: CRYPTO-162 openSslCipher support engine
URL: https://github.com/apache/commons-crypto/pull/164
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [commons-crypto] wenwj0 commented on pull request #164: CRYPTO-162 openSslCipher support engine
Posted by GitBox <gi...@apache.org>.
wenwj0 commented on PR #164:
URL: https://github.com/apache/commons-crypto/pull/164#issuecomment-1154827771
Thanks for replying.
I know that it's diffcult to maintain the native parts, I understand your choice.
Besides, if you need any help, i can do it :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [commons-crypto] garydgregory commented on pull request #164: CRYPTO-162 openSslCipher support engine
Posted by GitBox <gi...@apache.org>.
garydgregory commented on PR #164:
URL: https://github.com/apache/commons-crypto/pull/164#issuecomment-1154544718
Please rebase on git master.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [commons-crypto] garydgregory commented on pull request #164: CRYPTO-162 openSslCipher support engine
Posted by GitBox <gi...@apache.org>.
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org