List Binary Objects Archive Contents

This node lists the contents of a binary object column of archives using the selected archiving algorithm. Individual archive entries are output on individual rows

This node was developed by Vernalis Research (Cambridge, UK) . For feedback and more information, please contact knime@vernalis.com

Options

Column Options

Binary Objects Column
Select the incoming binary object column
Remove input column
Should the input column be removed?

Archive Options

Archive Format
Select the archive format
Archive Options
Additional format-specific options will be shown here depending on the selected format
Keep Directories
If this option is checked, then a row with the directory path within the archive will be added. This may only occur with empty directories within the archive, depending on how the file was created. This option is not available for some archive formats
Restore Defaults
Restore the default options for the specified archive format

Path Filter Options

Filter Paths
Should paths within the archive be filtered?
Wildcard
The path filter uses wildcards ('*' for multiple characters, '?' for single characters)
Regular expression
The path filter uses a regular expression
Case Sensitive
Is the filter pattern case-sensitive
Pattern
The wildcard or regular expression pattern to use to filter paths

Security Options

Compressed files and archives can be exploited by attackers using carefully crafted files which can cause issues on expansion, either by generating extremely large files from a small compressed file, or by generating large numbers of files from an innocuously small looking file. The following settings. See the Wikipedia article ' Zip Bomb ' for further details. The default settings here should be suitable to extract most files whilst limiting attack vectors

Maximum number of expanded files
The maximum allowed number of entries a multi-file archive binary object will expand to. A negative value indicates no limit. Option only available to compression formats supporting concatenation
Fail on explosive expansion
Should the node fail if explosive decompression is detected by any of the settings supplied? If not, then a warning will be set and at least one row for each input row will be present in the table. In the event that the first output row triggered the warning, then missing values will be added to the output row

Input Ports

Icon
Incoming data table

Output Ports

Icon
The input table with the expanded binary objects

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.