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

2017-09-22 Thread Lucas Gabriel Vuotto
You forgot to shit about vulkan in your rampage. (/s) Maybe you could be helpful and provide an idea for the problem Kamil is asking, instead of ranting about not using C. I still remember the words of arg, FRIGN & co after slcon4 stating that they'll start moderating the community. All I've se

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

2017-09-22 Thread sylvain . bertrand
On Fri, Sep 22, 2017 at 02:25:54PM +0200, Laslo Hunhold wrote: > On Fri, 22 Sep 2017 06:00:51 + > sylvain.bertr...@gmail.com wrote: > > Hey Sylvain, > > > go is not suckless. > > > > Should have written your PoC using simple C. > > what are you talking about? Go is an adequate language for

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

2017-09-22 Thread Antenore Gatta
On Fri, 22 Sep 2017 23:15:35 +0200 Kamil Cholewiński wrote: > On Fri, 22 Sep 2017, Antenore Gatta wrote: > > Well, I hope it's what you are looking for. > > It's totally not, but I see where you're coming from :) > > You may want to look at Ansible Tower, Rundeck, or similar stuff. > They al

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

2017-09-22 Thread Kamil Cholewiński
On Fri, 22 Sep 2017, Antenore Gatta wrote: > Well, I hope it's what you are looking for. It's totally not, but I see where you're coming from :) You may want to look at Ansible Tower, Rundeck, or similar stuff. They all suck, but they do solve this kind of problem in a much more manageable manne

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

2017-09-22 Thread Antenore Gatta
Back to real life with a real keyboard and a real system!!! I keep the previous answer to have a context. On Fri, 22 Sep 2017 16:21:08 + Antenore wrote: > >Now back to PrivEsc, I actually found Antenore's suggestion > >inspiring. It would work if we could force only part of the command > >to

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

2017-09-22 Thread Antenore
>Now back to PrivEsc, I actually found Antenore's suggestion inspiring. >It would work if we could force only part of the command to remain >constant, and use the constant part to perform non-interactive >authentication (e.g. by verifying a provided secret). Essentially >delegate authentication to

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

2017-09-22 Thread Kamil Cholewiński
I love how every discussin here eventually derails into "XYZ sucks". Yes, XYZ sucks. But FGH sucks more. I want to do what FGH does, because while FGH sucks, it solves a real-world problem. Now back to PrivEsc, I actually found Antenore's suggestion inspiring. It would work if we could force only

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

2017-09-22 Thread Laslo Hunhold
On Fri, 22 Sep 2017 06:00:51 + sylvain.bertr...@gmail.com wrote: Hey Sylvain, > go is not suckless. > > Should have written your PoC using simple C. what are you talking about? Go is an adequate language for certain higher-level-applications. The only beef I have about it is the large binar

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

2017-09-22 Thread sylvain . bertrand
On Fri, Sep 22, 2017 at 10:35:26AM +0200, Kamil Cholewiński wrote: > > go is not suckless. > > > > Should have written your PoC using simple C. > > Does C magically solve my design problem? > At PoC stage, implementation language absolutely does not matter. > I'd write it in PL/SQL if that solved

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

2017-09-22 Thread Kamil Cholewiński
> go is not suckless. > > Should have written your PoC using simple C. Does C magically solve my design problem? At PoC stage, implementation language absolutely does not matter. I'd write it in PL/SQL if that solved the problem at hand. <3,K.