Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
1–10 of 60 posts
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#2You do not need to put keys on the web sever’s disk to SSH onward from it. Use agent forwarding instead.
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#3You do not need to put keys on the web sever’s disk to SSH onward from it. Use agent forwarding instead.
Or even use `ProxyJump`, which doesn’t put as much trust on the jump host!
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#4Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#5This is what I have learned in many years of work: people who know systems should be let to handle those systems.
This is what happens when a developer is left to do the work that a system administrator should be trained to do - not all are -.
For a developer, in most cases, "just works" is the end goal, when referring to systems. Not "how it works", and what are the implications of making it work like this.
This really makes me sad.
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#6This is what I have learned in many years of work: people who know systems should be let to handle those systems. This is what happens when a developer is left to do the work that a system administrator should be trained to do - not all are -. For a developer, in most cases, "just works" is the end goal, when referring to systems. Not "how it works", and what are the implications of making it work like this. This rea…
I'm glad I can do both, but being the pivot point is less than stellar sometimes and can stick you with odd tasks (or way more than you want).
For too many developers "i shouldn't be blocked" is the highest virtue and that's when things like this happen.
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#7You really have to go out of your way to make the www-data user available through ssh, weird some do this.
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#8Exposing a private key to the world is a security problem? No kidding?
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#9The files in ~/.ssh are usually initialized with restrictive permissions, so how do they end up getting exposed? The only way I can think off-the-bat is that someone absent-mindedly commits them to their git dotfiles and ends up copying them over to another machine when they do a `git clone` command.
Re: Pwning your web server the easy way or why exposing –/.ssh/ is a bad idea
#10You really have to go out of your way to make the www-data user available through ssh, weird some do this.
My thoughts exactly. For someone responsible for a system to do this is such an act of gross negligence, and demonstrates such a lack of competency I would be remiss to keep the person at the company were they my employee.