Notepad++ encryption cuts of a lot of text...

Benya

Notepad++ v7.7 (64-bit)
Build time : May 19 2019 - 13:05:35
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll nppcrypt.dll
nppcrypt version: 1.0.1.5

I added keyboard shortcut for encryption (CTRL + E) and decrypt on (CTRL + D), i highlight everything before i encrypt it by doing CTRL + A then CTRL + E -> basic cipher AES CAND. rijndael256 mode gcm key: 256, blocksize: 128bit, IV 128bit. Encoding: Base64 options line breaks windows line length 64 key: add salt 16 scrypt N: 2^ 14 P: 1 iterations R: 8 IV: (psuedo)random.

on top of the cutted text document with my decrpytion it starts with 01(it has broken the entire line and just the 01TEXTEXTEXT is left.

I usually save the text document after i have encrypted it.

dinkumoil

@Benya

FYI: The latest version of the NppCrypt plugin is v1.0.1.6 (see >>> here <<<). Unfortunately, it brings some changes in its encryption system again. If you decide to update you will have to decrypt all your currently (with v1.0.1.5) encrypted files and re-encrypt them with the new version (see >>> the FAQ <<<).

PeterJones

@dinkumoil said:

The latest version of the NppCrypt plugin is v1.0.1.6

Yes, but Notepad++ v7.7 Plugins Admin still downloads v1.0.1.5.

@Benya said:

on top of the cutted text document with my decrpytion it starts with 01(it has broken the entire line and just the 01TEXTEXTEXT is left.

Unfortunately, you didn’t give an example file, so we cannot replicate exactly. That’s why I asked for the example data.

I installed v1.0.1.5 in my NPP 7.7-64-bit.

If I start with

This is a dummy file 23456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
Here is more 456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
And yet more goes here...! 89 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789

And then select all, Plugins > NppCrypt > Encrypt and use those same options you showed, with the password test, I get:

<nppcrypt version="1015">
<encryption cipher="rijndael256" mode="gcm" encoding="base64" tag="oxh621MHy0qrQNsHjFS7kA==" />
<random iv="IH+VG1N/tIYs4a7oIgxErg==" salt="4ZgFfJL8OFHwO9/RIl+dUA==" />
<key algorithm="scrypt" N="16384" r="8" p="1" />
</nppcrypt>
aFLkayffTzsYIE1bmTGC+POG7yFbHJicBvl/icNDIi2LruL43Hya6mo1xKfK8kym
YUJi5wHmDT7Mk1qp5/0Bo3C0/Uo39m7cIdS7OuEk+9DfqweyPYL4bj7o0AAIxPMl
wbU13lTFQzDNSEgkJXxyd6s14fwLAcO1eYm9sY+m7O42JzrLNd6K74kiKwZQWS5y
htnkqlZBBfC3PPLGltztF2TNOObxetaPFf2ZTT1W04iRFsLVNrH41Z9AIIm09C/t
FSALiGX0f6a1i3GTQfJY304xr9uwkU3a37aksGhJF+v3MlFOI1GYzNYYn2ZNJ31/
WS72sXoLdvFFs90MpHR94+PLzF9qs9+ljq6eQiw21EDXJ3ALMxyRJ2J4tTN8d+9P
g1Sotq2KbD2xAYgi5n0E2X/G7s28A4q2ffQAoV1fD2g8PswDQqEvmZMcEA==

I saved the results. Then selected all. Then Plugins > NppCrypt > Decrypt, password = test. Now I have

This is a dummy file 23456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
Here is more 456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
And yet more goes here...! 89 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789

Which matches my initial results.

Like I said before, please find a minimum set of text that will show your exact problem, then paste it in your response, between lines that are ~~~,

Here is exactly what I used to embed my sample text:

~~~
This is a dummy file 23456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
Here is more 456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
And yet more goes here...! 89 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
~~~

dinkumoil

@PeterJones said:

@dinkumoil said:

The latest version of the NppCrypt plugin is v1.0.1.6

Yes, but Notepad++ v7.7 Plugins Admin still downloads v1.0.1.5.

Nope, Notepad++ v7.7 is shipped with PluginList v1.0.9, released at May 11th, 2019, whereas v1.0.1.6 of the NppCrypt plugin was added to the list at March 31st, 2019 (see >>> here <<<).

My comment was meant to be a warning for @Benya that an update of NppCrypt would not be a possible solution.

PeterJones

@dinkumoil said:

Nope, Notepad++ v7.7 is shipped with PluginList v1.0.9, released at May 11th, 2019

Sorry, you’re right. I was actually in my v7.6.6 at the time, and didn’t notice.

Benya

@PeterJones I can’t paste my important text files that i encrypt to keep out of leeching eyes…

I’m not sure why this happens, it happens not all the time just randomly sometimes. If i encrypt a regular text file now it will work probably but this happened about three times now and i explained my steps for you.

And i will update the nppcrypt but i guess there was no fix for this issue with the updated version.

PeterJones

@Benya ,

I can’t paste my important text files that i encrypt to keep out of leeching eyes…

Note that in my first post, I said:

Can you share a sample text? Feel free to come up with dummy text that replicates the problem if you want to avoid sharing proprietary text.

I’m not asking for your super-secret text. I am asking for you to figure out some dummy text that shows the same problem. As it is, I cannot replicate your problem using the exact version of nppcrypt that you were using, using the exact text I showed above. If you cannot show us some sample/dummy text that evidences the problem, and we cannot replicate your problem with the random text we come up with, then we’re at an impasse. If you want our help, you’re going to have to figure out a way to show us the problem, because all our experiments show that there is no problem.

And i will update the nppcrypt

As @dinkumoil pointed out,

My comment was meant to be a warning for @Benya that an update of NppCrypt would not be a possible solution.

If you upgrade to nppcrypt v1.0.1.6, then any file you encrypted using v1.0.1.5 will be IMPOSSIBLE TO DECRYPT, because the two versions are mutually incompatible.

but i guess there was no fix for this issue with the updated version.

Since so far, you haven’t shown us how to replicate the issue, we are still left wondering whether there really is an issue with the plugin, or whether there’s a workflow or environment uniqueness causing your problem. But yes, if it’s any of those as the culprit, it is likely that updating nppcrypt will not fix the problem.

Hopefully, you’ll either solve it on your own, or figure out some way to show us data and a workflow that actually replicates your problem. Because without more details and example text from you, I cannot help you.

Alan Kilborn

@PeterJones said:

I’m not asking for your super-secret text. I am asking for you to figure out some dummy text that shows the same problem. As it is, I cannot replicate your problem using the exact version of nppcrypt that you were using, using the exact text I showed above. If you cannot show us some sample/dummy text that evidences the problem, and we cannot replicate your problem with the random text we come up with, then we’re at an impasse. If you want our help, you’re going to have to figure out a way to show us the problem, because all our experiments show that there is no problem.

PERFECT. Where do all the people that can’t write a decent problem statement, or follow simple directions and answer simple questions, come from? Tolerance for same is getting low. Sure I could tune out…but then I’d miss the gems. :)

Benya

As i can’t replicate the problem, this wont be able to go further. As you guys haven’t had this problem or heard about it i guess it’s a fault at my end somehow.

@Alan Kilborn i did write exactly what i have done, couldn’t do any more explanation that that as i already explained this happens randomly at times. This should have been understood by my first post as i mentioned it there already.

Alan Kilborn

@Benya

If you want more help, then you have to keep trying until you can get a reproducible scenario. Your other choice is to stop encrypting data this way. Sorry.