zlacker

[return to "Detecting the use of "curl | bash" server-side"]
1. cjbpri+e2[view] [source] 2018-07-29 02:26:42
>>rubyn0+(OP)
Neat! But it's not obviously a bad idea. You have a TLS connection with the site you're downloading from. `curl | bash` is no worse than downloading a .dmg or .deb from the same server would be.
◧◩
2. vbezhe+p2[view] [source] 2018-07-29 02:30:38
>>cjbpri+e2
deb/rpm is better because it's usually signed by maintainer with GPG keys. I think that it's harder to steal keys from maintainer than to infiltrate web server.
◧◩◪
3. cjbpri+r3[view] [source] 2018-07-29 02:52:00
>>vbezhe+p2
For the most part you receive the GPG keys over the same TLS connection, though.
◧◩◪◨
4. fulafe+K6[view] [source] 2018-07-29 04:01:12
>>cjbpri+r3
That's an antipattern, should use keyservers.
◧◩◪◨⬒
5. geocar+ne[view] [source] 2018-07-29 07:05:58
>>fulafe+K6
Where do you get the keyserver ID? From the website? You're back to square one, because anyone can upload anything to a keyserver. If they can modify the website (change files, etc) they can also change the keyserver ID they're telling people to use.

The "antipattern" is letting/expecting software developers also be software publishers.

[go to top]