Task #2949
closed
Adding libcrypto-based crypto support
Added by Yingdi Yu almost 9 years ago.
Updated almost 8 years ago.
Estimated time:
(Total: 0.00 h)
Description
CryptoPP is the crypto library used by ndn-cxx.
However, the support of CryptoPP is not very good (The code has not been updated for a long time). And it created several building issues in the past.
OpenSSL, though not perfect, keeps getting vulnerabilities fixed due to its larger user base. And we promised to people several years ago that we will eventually switch to OpenSSL when we have better understanding about crypto.
This implies that we need to provide crypto operation based on libcrypto, which is part of OpenSSL.
Usage of CryptoPP is mainly in TPM, so this issue will conflict with #2948.
What would be the ordering to resolve the conflict?
- Blocks Task #2948: Define new abstraction of Tpm added
The new TPM file will use openssl.
When you say "openssl", what do you mean exactly? Are you going to use libssl or libcrypto or both?
Davide Pesavento wrote:
When you say "openssl", what do you mean exactly? Are you going to use libssl or libcrypto or both?
libcrypto in most cases, I need to check which one supports PKCS, if it is also libcrypto, then we do not need libssl.
- Subject changed from Replace CryptoPP with OpenSSL to Adding libcrypto-based crypto support
- Description updated (diff)
- Status changed from New to Closed
All subtasks are done, we can close this issue.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by