3 ms·
That's an interesting use case! The development so far has focused on security-related uses, especially finding hardcoded credentials in source code and log fi
by SnowflakeOnIce 4y ago
That's an interesting use case!
The development so far has focused on security-related uses, especially finding hardcoded credentials in source code and log files. For the serial number and license spelunking you describe, Nosey Parker would need a couple more pieces to work well:
(1) Regex rules that would match serial numbers. I think it would be tough to write a regex for this that would match precisely and with good recall, i.e., producing few false positives and few false negatives. Not a showstopper, but not ideal.
(2) Built-in unarchiving support. Nosey Parker will handle textual files on disk just fine, but won't do useful things for many binary file types such as zip files. Your old external drives probably have tons of non-textual files like that. I would like to eventually add built-in unarchiving support to Nosey Parker; this would allow a way for textual content to be extracted from binary files and then scanned like the rest.
- tyingq 4y agoMany "product key / serial number" schemes include things that could keep the false positives down, like specific encoding (base24 is common), and built-in checksums.