On Fri, Dec 6, 2019 at 10:06 AM Jeffrey Fetterman
wrote:
>
> Ah. I don't think this mailing list is for me. Thank you for your time.
>
What are you expecting anyway?
1. It is normal for a tar program to reject a tarball with multiple layers of
gzip. Some tar implementations allows recurse
Ah. I don't think this mailing list is for me. Thank you for your time.
On Thu, Dec 5, 2019 at 7:31 PM Eli Schwartz wrote:
>
> On 12/5/19 8:03 PM, Jeffrey Fetterman wrote:
> > Hey, I'm not the one who decided that both zipballs and tarballs on
> > GitHub should use DEFLATE compression on random
On 12/5/19 8:07 PM, Jeffrey Fetterman wrote:
>> This is with GNU tar, how many different versions of tar did you try,
>> anyway???
>
> From my testing, GNU Tar doesn't need to use pipe gzip on tarballs,
> but can't handle zipballs.
My point was rather that the command line you ran did not work
On 12/5/19 8:03 PM, Jeffrey Fetterman wrote:
> Hey, I'm not the one who decided that both zipballs and tarballs on
> GitHub should use DEFLATE compression on random files.
I'm genuinely not sure if you're trolling. The url you used is an HTTP
302 redirect to
Location:
There was a Black Hat talk a couple of years ago where they presented this
sweet of files:
https://bomb.codes/
Good test cases for compression utilities.
On Thu, Dec 5, 2019, 19:07 Jeffrey Fetterman wrote:
> >This is with GNU tar, how many different versions of tar did you try,
> anyway???
>
>
Hey, I'm not the one who decided that both zipballs and tarballs on
GitHub should use DEFLATE compression on random files.
On Thu, Dec 5, 2019 at 4:37 PM Eli Schwartz wrote:
>
> On 12/5/19 5:25 PM, Jeffrey Fetterman wrote:
> > This does not work:
> > curl -sL
>This is with GNU tar, how many different versions of tar did you try, anyway???
>From my testing, GNU Tar doesn't need to use pipe gzip on tarballs,
but can't handle zipballs.
On Thu, Dec 5, 2019 at 7:03 PM Jeffrey Fetterman wrote:
>
> Hey, I'm not the one who decided that both zipballs and
On Friday, December 6, 2019, Eli Schwartz wrote:
> libarchive bsdtar works, which I guess means that libarchive permits you
> to wrap a tarball in *two* layers of gzip compression, then extract the
> contents. Personally, I would claim this is a buggy design goal, because
> you'd have to be nuts
On 12/5/19 5:25 PM, Jeffrey Fetterman wrote:
> This does not work:
> curl -sL https://api.github.com/repos/mirror/busybox/tarball/master |
> busybox64 gzip | busybox64 tar -xf -
>
> But this does (note the lack of using busybox64 on the last part):
> curl -sL
This does not work:
curl -sL https://api.github.com/repos/mirror/busybox/tarball/master |
busybox64 gzip | busybox64 tar -xf -
But this does (note the lack of using busybox64 on the last part):
curl -sL https://api.github.com/repos/mirror/busybox/tarball/master |
busybox64 gzip | tar -xf -
Tried
10 matches
Mail list logo
