Releases: cavejay/Strippy
Strippy v2.4.0
This release is focused on sensitive data parsing for lists of information. If your logs contain a list of servers and each of those servers are found elsewhere in the logs Strippy can now interpret the list and Sanitise each item rather than the list as one immutable piece of sensitive information.
Changelog
Bug Fixes
- Regex searches that include start and end of line characters now actually work.
^
and$
now work as expected. - Newline characters provided to the configuration parameters SanitisedFileFirstLine and KeyListFirstLine were not parsed correctly. This was a problem because the default included these not-working newline characters. Strippy will now replace {1} in these configuration parameters with newline characters during processing. Defaults have been updated to match.
- Using old config styles with new scripts should not create any issues.
New Features
- Lists of sensitive data can now be processed into individual items by including a delimiter after the alias. Briefly:
Input: 2020-02-10 INFO ConnectedServers abc,def,bgf
Rule: "INFO ConnectedServers (.+?)$"="Server",","
Output: 2020-02-10 INFO ConnectedServers Server1,Server2,Server3
- There are now 3 different types of Rules that can be described to Strippy.
- Delete Rules:
"<regex>"=\delete
- Remove the entire line that they match. This is for very difficult to sanitise information or overly-plentiful lines that provide little information (and clog up processing)
- Basic Rules, the 'normal' kind:
"<regex>"="<alias>"
- found once and the first regex group is replaced with a numbered alias everywhere.
- List Rules - new in v2.4.0:
"<regex>"="<alias>","<delimiter>"
- Lists of Sensitive information - found, split on the delimiter (delimiter can be regex) and then each element is given a different numbered alias and replaced everywhere.
- Delete Rules:
Product Support
- Added additional rules to the dt-managed.conf file.
Strippy v2.3.0
Updates:
- Refreshed get-help text (found at the top of the script file)
- zero-filled key names eg. Hostname02 or Address030 for better sorting and limiting key-in-key replacement problems
- Slightly re-organised script body (keeping functions together etc)
Strippy v2.2.0
Initial Release of Archive (zip, gz) support.
Targeting a .zip or .gz file will immediately unpack the file into a <name>-zip
directory and Sanitise from there. Only the top level archive will be unpacked unless the -recurse
switch is used.
To unpack any potential archives inside a normal folder you will need to use the -unpackZip
switch. This works with -recurse
to unpack any archive files that would be explored as folders during normal operation.
This is the initial release, so while I do my best to prevent any bugs, there may be one or too.
Other Changes:
- all logs made by strippy are forced to UTF-8 encoding
- specific file types are now ignored.
- Updated various default config settings (ignorestrings and make-config output)
Strippy v2.1.5
Small patches.
Check closed issues and previous tags/releases for details on changes.
Strippy v2.1.3
New release that closes out a potential code execution vulnerability.
Strippy v2.1.2
Fixes problems that v2.1.1 didn't catch with #23
Strippy v2.1.1
The -MakeConfig flag did not create a valid file. This was covered by #23 and fixed in this release
Strippy v2.1.0
Logging to file has been added with this release. Enable logging with the -log
flag and show additional debug logging with the -showdebug
flag.
There are a few new flags that relate to logging as well. These flags have explanations in get-help but are also outlined below:
-log
Enables logging for this particular instance of Strippy-showDebug
Enables further 'debug' level logging messages. This switch will produce a log of data-logfile
(Default: ".\strippy.log") Specifies where to log all the information too-MaxLogFileSize
(Default: 10MB) Specifies the maximum size a log file will reach-LogHistory
(Default: 5) Specifies how many 'historical' log files will be kept. eg strippy.1.log etc
Strippy v2.0.1
Small Bug fix from #18. Using a config you've created your own shouldn't break everything now