1 |
Lindsay Haisley <fmouse-gentoo@×××.com> posted |
2 |
1192831388.10036.7.camel@××××××××××.com, excerpted below, on Fri, 19 Oct |
3 |
2007 17:03:08 -0500: |
4 |
|
5 |
> I researched this, and solved the problem. The correct solution was |
6 |
> posted at |
7 |
> http://www.linuxquestions.org/questions/slackware-14/12.0-and-hal-read- |
8 |
this-566862/ |
9 |
> |
10 |
> Basically, I had to do 2 things: |
11 |
> |
12 |
> 1. Add myself to the group plugdev in /etc/group 2. Reload the Dbus |
13 |
> config with /etc/init.d/dbus reload |
14 |
> |
15 |
> It would be a Good Thing if new local accounts could be added to group |
16 |
> plugdev when they're created. |
17 |
|
18 |
Adding users you wish to have this access to the plugdev group is indeed |
19 |
the correct solution, and indeed, mentioned in the log messages for the |
20 |
hal package when you merge it. Check your portage messages log, or see |
21 |
the elog at the end of the hal ebuilds if necessary. So the instructions |
22 |
were there for you to read if you wanted to. |
23 |
|
24 |
However, security-wise, you've hit a bit of a raw nerve here, so excuse |
25 |
me while I rant a bit... |
26 |
|
27 |
It would *NOT* be a "Good Thing" (r), and in fact, would be a very "Bad |
28 |
Thing" (r) to do this automatically when new users are created, as that |
29 |
kills important aspects of the Unix/Linux security model, the entire |
30 |
reason the generic "users" group isn't used in the first place. There |
31 |
are good reasons sysadmins may not WANT every user to have automount |
32 |
rights, and it's already possible to expand your newuser scripts locally |
33 |
to automatically add a user to various groups, if you as sysadmin decide |
34 |
that's what you want to do. |
35 |
|
36 |
Among other possible security issues is the fact that it's not always |
37 |
possible to cleanly give a user the rights necessary to mount a volume, |
38 |
without also giving them generically the rights to overwrite system |
39 |
devices, and if you have potentially malicious users, or even simply |
40 |
naive "innocent" users that don't understand security and don't see any |
41 |
reason why they should /have/ to understand it, clicking on anything that |
42 |
comes their way... With what you're advocating, why not do away with |
43 |
logins and have everybody run as root, thereby avoiding the permissions |
44 |
problem entirely? After all, MS did effectively that for years with the |
45 |
their 9x series, and we all know how problem free /that/ was. |
46 |
|
47 |
So... please think before you make requests for automating procedures |
48 |
that effectively automate the creation of security holes. If you want |
49 |
platforms that do such things, they are available; no need to make Gentoo |
50 |
into one of them by default. |
51 |
|
52 |
-- |
53 |
Duncan - List replies preferred. No HTML msgs. |
54 |
"Every nonfree program has a lord, a master -- |
55 |
and if you use the program, he is your master." Richard Stallman |
56 |
|
57 |
-- |
58 |
gentoo-desktop@g.o mailing list |