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. deatha+la[view] [source] 2018-07-29 05:30:30
>>fulafe+K6
Aren't keyserver lookups usually keyed off a 32-bit key ID though? (Whose space isn't big enough to avoid someone brute-force generating a key with a certain key ID s.t. you think you got the right key.) You're supposed to check the fingerprint, but you need to get the fingerprint, and for that you need a secure channel, and you're right back to square one.

For that matter, where did you get the key ID.

[go to top]