public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wiktor <victorjan@poczta.onet.pl>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFD] 'nice' attribute for executable files
Date: Fri, 01 Apr 2005 17:26:25 +0200	[thread overview]
Message-ID: <424D6821.4010709@poczta.onet.pl> (raw)
In-Reply-To: <yw1xhdisx3th.fsf@ford.inprovide.com>

Måns Rullgård wrote:
> 
> So you are proposing the addition of a per-file attribute, with
> restricted access, and potentially dangerous effects if set
> incorrectly.  This, combined with the fact that is unlikely to receive
> much testing, all speaks against it.
> 

Almost every attribute can be dangerous if set incorrectly. Bot it is 
really no problem - simply let's turn to fat12 as root filesystem, and 
no attribute will be dangerous any more... See that acl-s also are not 
used for every file, only for some files, ones of thousands files in the 
filesystem. They are not set and reset every ten minutes - they are set 
one time and used, used and used. The same applies to nice attribute. Is 
it dangerous to not modify attribute all the time? And why restricted 
access is riskfull and evil? If restriction of sccess makes system more 
vurnable to attacks, maybe the good solution will be to set 755 
attributes on enery inode (expecially /etc/shadow) - then everyone will 
be able to do everything and system as whole will be more secure...

I really don't catch your mind.

--
wixor
May the Source be with you.

  reply	other threads:[~2005-04-01 15:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ed33rit.1e148rh@ifi.uio.no>
2005-03-29 20:45 ` [RFD] 'nice' attribute for executable files Bodo Eggert
2005-03-30 16:07   ` Wiktor
2005-03-30 16:55     ` Måns Rullgård
2005-03-30 17:27       ` Wiktor
2005-03-30 19:03         ` Måns Rullgård
2005-03-30 20:16           ` Wiktor
2005-03-30 20:43             ` Måns Rullgård
2005-04-01 15:26               ` Wiktor [this message]
2005-04-01 16:07                 ` Måns Rullgård
2005-03-31  5:46             ` Jan Engelhardt
2005-03-31 15:56       ` Horst von Brand
2005-03-31 16:05         ` Måns Rullgård
2005-04-01 15:40         ` Wiktor
2005-04-01 16:12           ` Måns Rullgård
2005-04-01 17:27           ` Horst von Brand
2005-03-30 19:40     ` Bodo Eggert
2005-03-30 21:03     ` Lee Revell
2005-03-29 19:55 Wiktor
2005-03-29 21:02 ` Lee Revell
2005-03-30 19:55 ` Bill Davidsen
2005-03-31  5:51 ` Matt Mackall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=424D6821.4010709@poczta.onet.pl \
    --to=victorjan@poczta.onet.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@inprovide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox