Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AES of openABE's performance is not normal #37

Open
sploving opened this issue Jul 6, 2020 · 0 comments
Open

AES of openABE's performance is not normal #37

sploving opened this issue Jul 6, 2020 · 0 comments

Comments

@sploving
Copy link

sploving commented Jul 6, 2020

When encrypt and decrypt large files using AES of openABE, it costs a lot of time than normal AES. Here is the performance I debugeed:
decrypt: EVP_DecryptInit_ex0.002 ms
decrypt: EVP_DecryptUpdate 1 0 ms
decrypt: EVP_DecryptUpdate 2 50.797 ms
decrypt: pt_buf.appendArray 89.899 ms
decrypt: EVP_CIPHER_CTX_ctrl0.002 ms
decrypt: pt_buf.toString() 2006.45 ms
decrypt: 2212.04 ms

This is because openABE use its own string type "OpenABEByteString". Its toString API and appendArray cost a lot of time.

So I have a question: in the following API

OpenABE_ERROR
OpenABESymKeyAuthEnc::encrypt(const string& plaintext, OpenABEByteString *iv, OpenABEByteString *ciphertext, OpenABEByteString *tag)
{

bool
OpenABESymKeyAuthEnc::decrypt(string& plaintext, OpenABEByteString* iv, OpenABEByteString* ciphertext, OpenABEByteString* tag)
{

Why not use standard string instead of OpenABEByteString?

Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant