Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Releases shouldn't tarbomb #92

Closed
kinghajj opened this issue May 31, 2018 · 1 comment
Closed

Releases shouldn't tarbomb #92

kinghajj opened this issue May 31, 2018 · 1 comment
Labels
🐛 bug "Houston, we've had a problem."

Comments

@kinghajj
Copy link

Got:

$ tar xf wtf_0.0.3_darwin_amd64.tar.gz
$ rm wtf_0.0.3_darwin_amd64.tar.gz
$ ls
LICENSE.md      README.md       wtf

Expected:

$ tar xf wtf_0.0.3_darwin_amd64.tar.gz
$ rm wtf_0.0.3_darwin_amd64.tar.gz
$ ls
wtf-0.0.3
$ ls wtf-0.0.3
LICENSE.md      README.md       wtf
@senorprogrammer senorprogrammer added 🐛 bug "Houston, we've had a problem." medium labels May 31, 2018
@senorprogrammer
Copy link
Collaborator

This should be resolved when release v0.0.8 goes out. Thanks for the bug report!

senorprogrammer pushed a commit that referenced this issue Jun 13, 2018
Close #92. Wrap the release files in a directory to prevent tar-bombi…
696c8ad 
…ng the local dir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 bug "Houston, we've had a problem."
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kinghajj @senorprogrammer