-
Notifications
You must be signed in to change notification settings - Fork 39
All path separators needs to be normalized to forward slash #48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Fixed in module version 1.2.3.0 |
3b
added a commit
to 3b/zip
that referenced
this issue
Dec 13, 2021
some .NET and powershell versions create invalid files using \ as path separator, so try to handdle them as expected. PowerShell/Microsoft.PowerShell.Archive#48 https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/mitigation-ziparchiveentry-fullname-path-separator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even on Windows, the archive contents should only use forward slash as directory separator otherwise it causes problems on non-Windows systems where backslash is a valid character in a filename.
According to the Zip file spec section 4.4.17.1, the path MUST only use forward slashes
The text was updated successfully, but these errors were encountered: