#2199 Text file attachment with null character

[Ryan Steed]

Hi,

There appears to be a bug with the File Attachment feature. If a text file containing a null character is attached, only data preceding the null character is included, not the entire file.

Thanks,

Ryan

[Paul]

I can reproduce the problem on KeePass 2.34 using "binary (no conversion)" encoding - W8.1.

cheers, Paul

[Dominik Reichl]

Well, the text editing controls of Windows don't support null characters in texts. I've now added code such that KeePass automatically replaces null characters by spaces, which is the behavior of Notepad (on Windows 10).

Here's the latest development snapshot for testing:
http://keepass.info/filepool/KeePass_161101b.zip

Moving to closed feature requests.

Thanks and best regards,
Dominik

[Dominik Reichl]

Ticket moved from /p/keepass/bugs/1582/

[Ryan Steed]

Thanks, I've confirmed that build 161101b fixes the problem. What is funny is that Microsoft's own Bitlocker Recovery Key text file has a null character! This is what brought it to my attention.

[Paul]

Does that mean you can't use the recovery key after the null has been replaced by a space?

cheers, Paul

[Ryan Steed]

I'm not sure, this might affect the "automatic" USB recovery method. However as long as the remainder of the data within the recovery text file is intact, you can simply read the key and enter it in manually.

[Paul]

How do you enter a nul character?
Are you able to test it?

cheers, Paul

[Ryan Steed]

You'll never have to manually enter the null character. It is only at the head of the file. Here is a sample:

BitLocker Drive Encryption recovery key[NULL]

To verify that this is the correct recovery key, compare the start of the following identifier with the identifier value displayed on your PC.

Identifier:

A1234567-B123-C123-D123-E1234567890F

If the above identifier matches the one displayed by your PC, then use the following key to unlock your drive.

Recovery Key:

123456-123456-123456-123456-123456-123456-123456-123456

If the above identifier doesn't match the one displayed by your PC, then this isn't the right key to unlock your drive.
Try another recovery key, or refer to http://go.microsoft.com/fwlink/?LinkID=260589 for additional assistance.