The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The unanswered Question

Christoph Lameter <clameter@waterf.org> writes:

> That is just the problem. Could you please read the original message again
> and then PLEASE REPLY TO THE ISSUE!

Christoph, I looked back at what you asked, and I realized that it was
late and I did miss a couple of salient points to your questions, and
so my response wasn't quite as appropriate to your questions as it
could have been, but there's no need to shout.

Given your particular setup (and my limited understanding of security
issues), it looks like those binaries should be just as safe as any
other root binaries, as long as you are willing to assume that making
someone a member of admin is potentially tantamount to giving them the
root password.  This of course depends on whether or not there are
bugs in these binaries that can be exploited to gain root access.

In your particular setup, it sounds like you do expect admin to be
(roughly) the equivalent of root, and so this is probably fine.  For
other people's setups this could be very risky.

> osiris >#!/bin/bash
> osiris >chmod u+s /usr/sbin/statnet
> osiris >chmod u+s /usr/sbin/strobe
> osiris >etc...
> 
> I would never allow such risky binaries on any of my systems.

This is just a shell script.  I don't see how it's risky.  If you have
the appropriate permissions, you can chmod those files, if not, then
you can't.  Since these two programs are owned by root, only root can
do this.

This script wasn't intended to be suid root if that's what you're
thinking, but even if it was, it's my understanding that on a Linux
system, suid root scripts don't actually run suid (Disclaimer: don't
count on this), so it still wouldn't be dangerous.

--
Rob

--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com