Date: Thu, 27 Jun 1996 10:36:11 +0200 (MESZ) From: "Hr.Ladavac" <lada@ws2301.gud.siemens.co.at> To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Cc: vince@mercury.gaianet.net, ejs@bfd.com, mark@grumble.grondar.za, hackers@FreeBSD.org, security@FreeBSD.org, chad@mercury.gaianet.net, jbhunt@mercury.gaianet.net Subject: Re: I need help on this one - please help me track this guy down! Message-ID: <199606270836.AA158394572@ws2301.gud.siemens.co.at> In-Reply-To: <199606270321.UAA01884@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jun 26, 96 08:21:02 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In his e-mail Michael L. VanLoon -- HeadCandy.com wrote: > > > >> > It was a remote login so he had to transfer it over somehow... > > >> Well, *if* that's true, it still wouldn't be setuid root just from the > >> transfer. He'd *still* have to get root some other way to make this > >> binary setuid root. > >> But if he's going to do that, why bother copying a binary over the > >> network -- it would just be easier to just snag a copy of your own > >> /bin/sh and mark it setuid root. > > > Hmmm, what happens if he tars it first and then sends it over? > > Try it. :-) That's the only way to figure all this stuff out... > > Seriously, you must be root to create a setuid root file. It doesn't > matter *how* you try to create it. A five dollar question Vince: does root have .rhosts in his home directory? What is to be found there? If he does, throw it away; it's enormously insecure. Similar with /etc/host.equiv et cetera. /Marino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606270836.AA158394572>