On 10/20/07, <b class="gmail_sendername">Eric Hameleers (SBo)</b> <<a href="mailto:alien@slackbuilds.org">alien@slackbuilds.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Eric Hameleers (SBo) schreef:</blockquote><div><br>[ as rsync'd, some of folders in SW 12.0 sbo repo have the SGID on them ] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Thanks for reporting.</blockquote><div><br>Thank you. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>> Eric<br>
<br><br>It is even more widespread - in the 11.0 repository as well, and also<br>in some of the directories used by the admins. Might it be a "feature"<br>of the server we are working on?</blockquote><div><br>Well, that's what I was wondering -- that is, if it were a "feature" and thus I should not report it -- or, heaven forbid, what if it turned out that there were some "feature" on *my* computer/system that, unknown to me, was operating secretly in the background doing abra cadabra or secret magic.
<br><br>(although, next is the command that I ran) (and its output showed [to my intermediate level sys admin eyes] that my file sys appeared normal elsewhere except for in the rsync'd sbo 12 repo)<br><br>find / -perm +02000 -exec ls -ld {} ; 2> /dev/null > /tmp/SGID.files
<br><br>What started all of this is twofold. ie both my curiosity and that I had been following a thread on either comp.os.linux.security or on comp.os.linux.networking<br><br>They were having a security related discussion and the topic turned to SUID and SGID file permissions. Someone posted the above command and the next command
<br><br>find / -perm +04000 -exec ls -ld {} ; 2> /dev/null > /tmp/SUID.files<br>--<br><br>(The specific mentioned SGID on *some* issue) It should be harmless though? Right?<br><br>That is, no harm can happen, even if given a worse case scenario? ie someone from a different group logs on -- and, what can they do? -- the worst is to build a Slackware package (I'm of course guessing since this maybe probably stretches my sys admin skills).
<br></div></div><br>-- <br>Alan.<br><br>