-
Notifications
You must be signed in to change notification settings - Fork 222
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
Signature and classification for NSF Lotus Notes files #547
Comments
Although I have already tried to use https://github.com/libyal/libnsfdb to parse Lotus Notes NSF files unsuccessfully in the past, for sure we can at least classify NSF files, thanks. |
We are using "kernel for lotus notes to outlook" to convert NSF to PST and after this, we analyse the PST files The classification would minimize the risk to miss such files. |
Nice suggestion, good to know. Unfortunately we need an open source library with compatible license to include in this project
For sure. |
According to this https://github.com/libyal/libnsfdb/blob/main/documentation/Notes%20Storage%20Facility%20(NSF)%20database%20file%20format.asciidoc#4-the-file-header file signature is just 2 bytes: 0x1A 0x00 Maybe we could check format version at offset 6 (4 bytes length) to try avoiding false positives (https://github.com/libyal/libnsfdb/blob/main/documentation/Notes%20Storage%20Facility%20(NSF)%20database%20file%20format.asciidoc#511-format-version). @gaffinet could you check in your files if the 4 bytes value (little-endian) at offset 6 is in {16, 17, 20, 41, 43, 48, 51} set? |
Actually I found one sample here and format version seems big-endian. |
I added a check for this format versions, valid for Lotus Notes 1.x to 8.5 according to libnsfdb docs. If anyone could confirm the numbers for versions 9, 10 & 11, we can add later. Anyway, currently extension is used as fallback if signature doesn't match. |
Hi
I have noticed, that NSF files (Lotus Notes Databases) aren't listed in the category of the mailboxes.
Yves
The text was updated successfully, but these errors were encountered: