4 ms·
The author wrote the following concerning a curl option: """So, what can we do with all of this? We have a few options, but none of them are particularly appea
by eesmith 3y ago
The author wrote the following concerning a curl option:
"""So, what can we do with all of this? We have a few options, but none of them are particularly appealing. ...
Download the file with curl. Unix command-line tools like curl and tar don’t add the quarantine bit to the files they create on macOS, so it’s pretty easy to run software downloaded with them.
Unfortunately, the repository where this tool is developed is private, so unauthenticated curl downloads won’t work. I’m seriously considering asking the CTO if we can make the repository public solely so we can use curl as a distribution mechanism. I could even write a platform-detecting shell script!
"""
The "curl ... | sh" technique could get pass through the authentication information for a subsequent curl call, but then authentication becomes a facade.
- viraptor 3y agoThat's why I added the bit about downloading master/main.zip. You can do that from the logged in browser and it's still around the same number of steps as installing a custom package and running it. (Login. Download the package/script. Install the package or unzip the script. Run it.)
- josephg 3y agoJust add an authentication header to the curl command.
- jwalton 3y ago> Unfortunately, the repository where this tool is developed is private Have you thought about publishing the install.sh and final zip file through GitHub pages? Or Cloudflare pages? Then the repo stays private, but the built application can be accessed publicly, and behind a hard-to-guess url.