News for hackers. Stuff that matters.
Re:Detecting the use of "curl | bash" server-side by sigjuice on Saturday July 28, 2018 @11:04PM (#17636290)
Not sure what you mean. I don’t think apt-get install foo involves transferring GPG keys.
Re:Detecting the use of "curl | bash" server-side by cjbprime on Saturday July 28, 2018 @11:20PM (#17636342)
We're comparing the security properties of

`curl https://somesite.com/foo.sh | bash`

with

`curl https://somesite.com/foo.deb`

and

`curl https://somesite.com/apt.key | sudo apt-key add - && sudo apt-get update && sudo apt-get install some-software`

I don't think there are very meaningful differences in the security properties -- I don't think it's more difficult to become compromised by one than by one of the others.

Re:Detecting the use of "curl | bash" server-side by hueving on Sunday July 29, 2018 @01:47AM (#17636722)
No, you're deliberately choosing a bad way to get a key to try to prove your point. You shouldn't be fetching a key from the site that might be compromised.
Re:Detecting the use of "curl | bash" server-side by geocar on Sunday July 29, 2018 @02:56AM (#17636900)
> You shouldn't be fetching a key from the site that might be compromised.

You shouldn't, but people do, and are being directed to do so increasingly as Linux becomes more popular. Software developers want to be software publishers so bad that they're just going to keep pushing, and therein lies the risk: If people get the impression that packages are somehow more secure than shell scripts, then these kinds of attacks will simply become more prevalent.

To you it's obvious that packages aren't more secure, it's how you get them that makes their normal use more secure. That's apparently too subtle a point for even big companies like Microsoft.

https://pydio.com/en/docs/v8/ed-debianubuntu-systems

https://docs.docker.com/install/linux/docker-ce/ubuntu/#inst...

https://www.spotify.com/uk/download/linux/

https://www.elastic.co/guide/en/apm/server/current/setup-rep...

https://ring.cx/en/download/gnu-linux

http://docs.grafana.org/installation/debian/

https://support.plex.tv/articles/235974187-enable-repository...

https://stack-of-tasks.github.io/pinocchio/download.html

http://download.mantidproject.org/ubuntu.html

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli... (!!!)

Re:Detecting the use of "curl | bash" server-side by dcbadacd on Sunday July 29, 2018 @07:33AM (#17637583)
I've always said the same, but what's the solution here?
Re:Detecting the use of "curl | bash" server-side by geocar on Sunday July 29, 2018 @05:00PM (#17640250)
There's three that I can see:

1. Walled Garden: Developers don't self-publish. Call it an app store, call it everything-in-apt.

2. Encapsulate everything so that developers can't do anything. Don't use anything unless it comes in a docker instance. Or a FreeBSD jail. Or something else. Qubes maybe.

3. Smarter users. Good luck with that one.

Re:Detecting the use of "curl | bash" server-side by twr on Sunday July 29, 2018 @02:02AM (#17636745)
No, there's no effective difference between those examples, apart from maybe post mortem analysis. It's also a poor method of key discovery, as hueving said.