Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/microsoft/recursiveextractor

RecursiveExtractor is a .NET Standard 2.0 archive extraction Library, and Command Line Tool which can process 7zip, ar, bzip2, deb, gzip, iso, rar, tar, vhd, vhdx, vmdk, wim, xzip, and zip archives and any nested combination of the supported formats.
https://github.com/microsoft/recursiveextractor

archive disc-image extractor nuget recursion

Last synced: 5 days ago
JSON representation

RecursiveExtractor is a .NET Standard 2.0 archive extraction Library, and Command Line Tool which can process 7zip, ar, bzip2, deb, gzip, iso, rar, tar, vhd, vhdx, vmdk, wim, xzip, and zip archives and any nested combination of the supported formats.

Awesome Lists containing this project

README 

        
# About

![CodeQL](https://github.com/microsoft/RecursiveExtractor/workflows/CodeQL/badge.svg) ![Nuget](https://img.shields.io/nuget/v/Microsoft.CST.RecursiveExtractor?link=https://www.nuget.org/packages/Microsoft.CST.RecursiveExtractor/&link=https://www.nuget.org/packages/Microsoft.CST.RecursiveExtractor/) ![Nuget](https://img.shields.io/nuget/dt/Microsoft.CST.RecursiveExtractor?link=https://www.nuget.org/packages/Microsoft.CST.RecursiveExtractor/&link=https://www.nuget.org/packages/Microsoft.CST.RecursiveExtractor/)



Recursive Extractor is a Cross-Platform [.NET Standard 2.0 Library](#library) and [Command Line Program](#cli) for parsing archive files and disk images, including nested archives and disk images.



# Supported File Types

| | | |

|-|-|-|

| 7zip+ | ar    | bzip2 |

| deb   | dmg** | gzip  | 

| iso   | rar^  | tar   | 

| vhd   | vhdx  | vmdk  | 

| wim*  | xzip  | zip+  |



Details




* Windows only


+ Encryption Supported


^ Encryption supported for Rar version 4 only


** Limited support. Unencrypted HFS+ volumes with certain compression schemes.



# Variants



## Command Line

### Installing

1. Ensure you have the latest [.NET SDK](https://dotnet.microsoft.com/download).

2. Run `dotnet tool install -g Microsoft.CST.RecursiveExtractor.Cli`



This adds `RecursiveExtractor` to your path so you can run it directly from your shell.



### Running

Basic usage is: `RecursiveExtractor --input archive.ext --output outputDirectory`



Detailed Usage




    

        
  • 

    input: The path to the Archive to extract.
    • 

        
  • 

    output: The path a directory to extract into.
    • 

        
  • 

    passwords: A comma separated list of passwords to use for archives.
    • 

        
  • 

    allow-globs: A comma separated list of glob patterns to require each extracted file match.
    • 

        
  • 

    deny-globs: A comma separated list of glob patterns to require each extracted file not match.
    • 

        
  • 

    raw-extensions: A comma separated list of file extensions to not recurse into.
    • 

        
  • 

    no-recursion: Don't recurse into sub-archives.
    • 

        
  • 

    single-thread: Don't attempt to parallelize extraction.
    • 

        
  • 

    printnames: Output the name of each file extracted.
    • 

        




For example, to extract only ".cs" files:

```

RecursiveExtractor --input archive.ext --output outputDirectory --allow-globs **/*.cs

```



Run `RecursiveExtractor --help` for more details.



## .NET Standard Library

Recursive Extractor is available on NuGet as [Microsoft.CST.RecursiveExtractor](https://www.nuget.org/packages/Microsoft.CST.RecursiveExtractor/). Recursive Extractor targets netstandard2.0+ and the latest .NET, currently .NET 6.0, .NET 7.0 and .NET 8.0.



### Usage



The most basic usage is to enumerate through all the files in the archive provided and do something with their contents as a Stream.



```csharp

using Microsoft.CST.RecursiveExtractor;



var path = "path/to/file";

var extractor = new Extractor();

foreach(var file in extractor.Extract(path))

{

    doSomething(file.Content); //Do Something with the file contents (a Stream)

}

```



Extracting to Disk




This code adapted from the Cli extracts the contents of given archive located at `options.Input` to a directory located at `options.Output`, including extracting failed archives as themselves.



```csharp

using Microsoft.CST.RecursiveExtractor;



var extractor = new Extractor();

var extractorOptions = new ExtractorOptions()

{

    ExtractSelfOnFail = true,

};

extractor.ExtractToDirectory(options.Output, options.Input, extractorOptions);

```



Async Usage




This example of using the async API prints out all the file names found from the archive located at the path.



```csharp

var path = "/Path/To/Your/Archive"

var extractor = new Extractor();

try {

    IEnumerable results = extractor.ExtractFileAsync(path);

    await foreach(var found in results)

    {

        Console.WriteLine(found.FullPath);

    }

}

catch(OverflowException)

{

    // This means Recursive Extractor has detected a Quine or Zip Bomb

}

```



The FileEntry Object




The Extractor returns `FileEntry` objects.  These objects contain a `Content` Stream of the file contents.



```csharp

public Stream Content { get; }

public string FullPath { get; }

public string Name { get; }

public FileEntry? Parent { get; }

public string? ParentPath { get; }

public DateTime CreateTime { get; }

public DateTime ModifyTime { get; }

public DateTime AccessTime { get; }

```



Extracting Encrypted Archives




You can provide passwords to use to decrypt archives, paired with a Regular Expression that will operate against the Name of the Archive to determine on which archives to try the passwords in each List.



```csharp

var path = "/Path/To/Your/Archive"

var directory

var extractor = new Extractor();

try {

    IEnumerable results = extractor.ExtractFile(path, new ExtractorOptions()

    {

        Passwords = new Dictionary>()

        {

            { new Regex("\.zip"), new List(){ "PasswordForZipFiles" } },

            { new Regex("\.7z"), new List(){ "PasswordFor7zFiles" } },

            { new Regex(".*"), new List(){ "PasswordForAllFiles" } }



        }

    });

    foreach(var found in results)

    {

        Console.WriteLine(found.FullPath);

    }

}

catch(OverflowException)

{

    // This means Recursive Extractor has detected a Quine or Zip Bomb

}

```



## Exceptions

RecursiveExtractor protects against [ZipSlip](https://snyk.io/research/zip-slip-vulnerability), [Quines, and Zip Bombs](https://en.wikipedia.org/wiki/Zip_bomb).

Calls to Extract will throw an `OverflowException` when a Quine or Zip bomb is detected and a `TimeOutException` if `EnableTiming` is set and the specified time period has elapsed before completion.



Otherwise, invalid files found while crawling will emit a logger message and be skipped.  You can also enable `ExtractSelfOnFail` to return the original archive file on an extraction failure.



## Notes on Enumeration



### Multiple Enumeration

You should not iterate the Enumeration returned from the `Extract` and `ExtractAsync` interfaces multiple times, if you need to do so, convert the Enumeration to an in memory collection first.



### Parallel Enumeration

If you want to enumerate the output with parallelization you should use a batching mechanism, for example:



```csharp

var extractedEnumeration = Extract(fileEntry, opts);

using var enumerator = extractedEnumeration.GetEnumerator();

ConcurrentBag entryBatch = new();

bool moreAvailable = enumerator.MoveNext();

while (moreAvailable)

{

    entryBatch = new();

    for (int i = 0; i < BatchSize; i++)

    {

        entryBatch.Add(enumerator.Current);

        moreAvailable = enumerator.MoveNext();

        if (!moreAvailable)

        {

            break;

        }

    }



    if (entryBatch.Count == 0)

    {

        break;

    }



    // Run your parallel processing on the batch

    Parallel.ForEach(entryBatch, new ParallelOptions() { CancellationToken = cts.Token }, entry =>

    {

        // Do something with each FileEntry

    }

}

```



### Disposing During Enumeration

If you are working with a very large archive or in particularly constrained environment you can reduce memory and file handle usage for the Content streams in each FileEntry by disposing as you iterate.



```csharp

var results = extractor.Extract(path);

foreach(var file in results)

{

    using var theStream = file.Content;

    // Do something with the stream.

    _ = theStream.ReadByte();

// The stream is disposed here by the using statement

} 

```



# Feedback



If you have any issues or feature requests (for example, supporting other formats) you can open a new [Issue](https://github.com/microsoft/RecursiveExtractor/issues/new).  



If you are having trouble parsing a specific archive of one of the supported formats, it is helpful if you can include an sample archive with your report that demonstrates the issue.



# Dependencies



Recursive Extractor aims to provide a unified interface to extract arbitrary archives and relies on a number of libraries to parse the archives.



* [SharpZipLib](https://github.com/icsharpcode/SharpZipLib)

* [SharpCompress](https://github.com/adamhathcock/sharpcompress)

* [LTRData/DiscUtils](https://github.com/LTRData/discutils)



# Contributing



This project welcomes contributions and suggestions.  Most contributions require you to agree to a

Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us

the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.



When you submit a pull request, a CLA bot will automatically determine whether you need to provide

a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions

provided by the bot. You will only need to do this once across all repos using our CLA.



This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).

For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or

contact [[email protected]](mailto:[email protected]) with any additional questions or comments.