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
Yeah, I did think about asking for that when the PR was merged but I always prefer more verbosity for things like curl|bash that make some people uncomfortable. Although a set -x in the script would probably do a more helpful job on that!
Open a PR against the instructions to add the s if you like, I'll +1 it.
Nah, I don't think that's necessary. I'm personally not concerned about the security of this curl|bash because (a) we control it and (b) it's over https from a trusted site. It's just that a lot of programmers have been programmed to think curl|bash is inherently evil and is an indicator of bad security attitudes. But there's really nothing to be done about that other than be firm when people show up with criticism.
For now let's go with the s in the curl
Activity
rvagg commentedon Jun 4, 2020
Yeah, I did think about asking for that when the PR was merged but I always prefer more verbosity for things like
curl|bashthat make some people uncomfortable. Although aset -xin the script would probably do a more helpful job on that!Open a PR against the instructions to add the
sif you like, I'll +1 it.weiliddat commentedon Jun 4, 2020
Yeah I get that too.
set -xwould help, or maybe just aecho "Disclaimer about this being downloaded from the Internet"?rvagg commentedon Jun 5, 2020
Nah, I don't think that's necessary. I'm personally not concerned about the security of this
curl|bashbecause (a) we control it and (b) it's over https from a trusted site. It's just that a lot of programmers have been programmed to thinkcurl|bashis inherently evil and is an indicator of bad security attitudes. But there's really nothing to be done about that other than be firm when people show up with criticism.For now let's go with the
sin thecurl