Re: [dev] Privilege escalation on remote hosts. MANY remote hosts.

2017-09-21 Thread Rendov Norra
> On Sep 22, 2017, at 2:00 AM, sylvain.bertr...@gmail.com wrote: > > go is not suckless. Why not? I don't see the issue with go for occasional use or security critical applications. Is go hard to maintain? > Should have written your PoC using simple C. > > -- > Sylvain >

Re: [dev] Privilege escalation on remote hosts. MANY remote hosts.

2017-09-21 Thread sylvain . bertrand
go is not suckless. Should have written your PoC using simple C. -- Sylvain

Re: [dev] Privilege escalation on remote hosts. MANY remote hosts.

2017-09-21 Thread Kamil Cholewiński
> What about using custom public SSH keys that force the execution of a > specific command/script instead of the default login shell? The operational principle is that first you scp a script with arbitrary content, written in an arbitrary language, to the remote box(es), then execute the said scri

Re: [dev] Privilege escalation on remote hosts. MANY remote hosts.

2017-09-21 Thread Antenore
Sorry I'm on my mobile. What about using custom public SSH keys that force the execution of a specific command/script instead of the default login shell? If you're interested I can give you more details later. I've a suid script that is used instead of the login shell and it parses the paramet

[dev] Privilege escalation on remote hosts. MANY remote hosts.

2017-09-21 Thread Kamil Cholewiński
Hi list, TL;DR: passwordless sudo is same as making $USER equal to root at all times. Requiring a password is a royal PITA when trying to run one command on many many hosts. Scripting interactive password input sucks. Other methods are non-portable. Practical ideas? Long version: I've been worki