1 |
On 08:55 Fri 25 Apr , Robin H.Johnson wrote: |
2 |
> On Fri, Apr 25, 2003 at 09:06:35PM +0800, Daniel Armyr wrote: |
3 |
> > OK, immediately I notice that ufed does not check if it has |
4 |
> > authorisation to change any of the files it is made to change. I don't |
5 |
> > believe one should not be able to run it as non-root, but a warning or |
6 |
> > some "Read only mode" sign should definately be issued. |
7 |
> Hmm. Good point. I think we should throw an error and not start UFED. |
8 |
|
9 |
I've implemented this check in a subroutine for euse. When we implement the |
10 |
common API for both ufed and euse, we could use this subroutine. |
11 |
|
12 |
User may start ufed just to see the flags set (++-) and also to see the |
13 |
description of a particular USE flag. So *not* starting UFED for non-root users |
14 |
is not quite correct. They should see a read only UFED, with SAVE button |
15 |
disabled. Euse currently implements it this way. So, when non-root users access |
16 |
euse all the read only functions -i, -c, -d, -e is available. The -E and -D are |
17 |
not allowed. It does a check at the beginning and shows a warning if there is |
18 |
not enough permissions. |
19 |
|
20 |
Just my thoughts. |
21 |
|
22 |
Arun |
23 |
|
24 |
|
25 |
-- |
26 |
gentoo-dev@g.o mailing list |