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
remove heading? #22
Comments
hi! you can just delete the header after the encryption. In this case when decrypting you have to manually select the exact options that were used for the encryption. If you both times use "default options" this should not be a problem. BUT: good encryption options need randomly created values ( called "salt" for key creation out of the password, and "Initialization vector" as a "start" for block ciphers ). These values are also stored in the header. If you want to remove the header you would have to save these values some other way and provide them when decrypting. The thing is: "Hiding" the encryption method does not really make the encryption safer, therefore in my option using the header is just more convenient. |
hi, tanxs for your reply. i understand your reasoning, however there are examples like this site https://aesencryption.net/ which has no header... |
to be honest, i just don't know how the site you mentioned handles key creation and IV. |
those keys you are talking about cannot be INSIDE the encrypted text? so you would avoid a header.... maybe that site is structured like this. and I would like to use it, but you need to be online to refresh the code, instead I want to use it offline. yours, for my purpose, is excellent, but those 5 header lines leave me dumbfounded, having seen how work aesencryption.net .... |
hi, congratulations for your very nice plugin for np++ but i hope on next version that the header part can be removed... (i mean the one included in the values ....
i have try many other program to encrypt text but nobody has a header, only the text is encrypted.
this improvement it's possible on future version? thanks, greeting.
The text was updated successfully, but these errors were encountered: