The GOALS:
1. KISS
2. Don't dictate to the system admin (i.e. if he wants to use groups to
control access fine, we should be able to still live with or without his
inteference)
3. We should be able to function properly when no one is logged on.
The PLAN:
1. When starting check if
On Tue, 7 Nov 2006 09:51:31 -0600 Brian Mattern [EMAIL PROTECTED]
babbled:
On Mon, Nov 06, 2006 at 03:50:32PM -0500, Michael Jennings wrote:
On Monday, 06 November 2006, at 16:30:16 (+0100),
Essien Ita Essien wrote:
I'm just putting out feelers for ideas (a.k.a. best practices if
Michael Jennings wrote:
On Monday, 06 November 2006, at 16:30:16 (+0100),
Essien Ita Essien wrote:
I'm just putting out feelers for ideas (a.k.a. best practices if
such exist), for how to implement Priviledged Execution for
Entrance_Edit_GUI
Best practice: Don't do it.
The
On Tue, 07 Nov 2006 09:27:44 +0100 Essien Ita Essien
[EMAIL PROTECTED] wrote:
Michael Jennings wrote:
On Monday, 06 November 2006, at 16:30:16 (+0100),
Essien Ita Essien wrote:
I'm just putting out feelers for ideas (a.k.a. best practices if
such exist), for how to implement
On Mon, Nov 06, 2006 at 03:50:32PM -0500, Michael Jennings wrote:
On Monday, 06 November 2006, at 16:30:16 (+0100),
Essien Ita Essien wrote:
I'm just putting out feelers for ideas (a.k.a. best practices if
such exist), for how to implement Priviledged Execution for
Entrance_Edit_GUI
On 11/7/06, Brian Mattern [EMAIL PROTECTED] wrote:
He still needs a solution to his problem. Namely How do I let people
configure entrance from a gui without having to touch the command line.
One possibility is to have an entrance group that has write
permissions to the config file. Then
On Tuesday, 07 November 2006, at 09:27:44 (+0100),
Essien Ita Essien wrote:
this brings up the problem of what happens when we try to launch it from
the entrance login screen (ala GDM).
At that point, no one is logged in (i.e. no one is root yet).
That's a good thing. Authenticate root
On 11/7/06, Michael Jennings [EMAIL PROTECTED] wrote:
You're making this problem far too difficult. Distribution-level and
OS-level changes/enhancements to, or fuckups of (like SELinux),
authentication and authorization schemes are not our problem. They
are a distro/OS problem. X must run
Nathan Ingersoll wrote:
On 11/7/06, Michael Jennings [EMAIL PROTECTED] wrote:
snip
K.I.S.S. -- Keep It Simple, for fuck's Sake.
Heh, that's what I thought I was arguing. If we add complexity at this
level, then it just gets compounded by all the other layers of
complexity that
Ahem...
I'm just putting out feelers for ideas (a.k.a. best practices if such
exist), for how to implement Priviledged Execution for Entrance_Edit_GUI
The problem is that, the config file is /etc/entrance_config.cfg, which
is protected file, but all users *can* run entrance_edit_gui for now.
On Monday, 06 November 2006, at 16:30:16 (+0100),
Essien Ita Essien wrote:
I'm just putting out feelers for ideas (a.k.a. best practices if
such exist), for how to implement Priviledged Execution for
Entrance_Edit_GUI
Best practice: Don't do it.
The problem is that, the config file is
11 matches
Mail list logo
