Skip to content

Bad offset (option -s) can't count after 0xFFFFFFFF #13

@Emen0s

Description

@Emen0s

Hello !

I use Strings2 evryday for work.
I think I have found an issue with the -s parameter on very large file.

I use strings2 -s on full RAW disk images.

I found that the offset can't count after 0xFFFFFFFF.
It just go to 0x00000001 after.
So every offset after 0xFFFFFFFF on my result is bad, so my tools won't work (I use the offset from strings2 to automatically carve for files).

Thank you very much for your work !
A fix would be very very pleased !

Have a nice day !

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions