You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to process some Tar files that contain the LongLink header type. Specially, they contain both a LongLink and a LongName header type for a hard link entry. Currently, SharpCompress will not handle the LongLink header properly and accidentally consume the following block as a file instead of as the long link name, resulting in an empty file named @././LongLink, at least, with the Tar file we are dealing with.
The text was updated successfully, but these errors were encountered:
DannyBoyk
added a commit
to DannyBoyk/sharpcompress
that referenced
this issue
Jun 3, 2024
We have to process some Tar files that contain the LongLink header type. Specially, they contain both a LongLink and a LongName header type for a hard link entry. Currently, SharpCompress will not handle the LongLink header properly and accidentally consume the following block as a file instead of as the long link name, resulting in an empty file named
@././LongLink
, at least, with the Tar file we are dealing with.The text was updated successfully, but these errors were encountered: