On Wed, Jul 16, 2003 at 07:01:06PM +0200, Buchan Milne wrote:
> I think, going back to it, the users would prefer some tool that is more
> interactive.

If they want interactive they'd be running MandrakeUpdate on their own
IMHO.  However, on my todo list is the possiblity of making urpmc prompt
to go ahead and install the packages it lists if being run
interactively.  But I haven't implemented it because I'm not sure I want
to open that can of worms.

The problem with doing this interactively is how?  fpons suggested
putting MandrakeUpdate on xinit.d...  That assumes the user logs in and
out of X on a regular basis.  So let's say we put something on a cron
that looks for updates, pops up and says hey there are updates.  Which
user should we display that for?  We strongly suggest that users not run
as root.  We can't assume that any user that is logged in is an
appropriate person to display this to.  We could use the security
administrator from msec, but that field could also be an email address
not on the same machine.

Ultimately, what we want is something that lets users know that there
are updates and that they ought to run MandrakeUpdate.  urpmc on a cron
job mailing the security administrator selected during the install seems
like the simplest solution at the moment.  It may not be ideal but it's
better than nothing.  And if we're going to go into beta soon now is not
the time to try and write a new program.

> Remember, it's for *users*, not *cookers*. The kind of thing a new user
> who has never used linux before will notice (yes, I did notice the
> update applet in Windows XP the first time I had ever used it, and it's
> not like I use Windows much anymore) and be able to administer (ie set
> when it runs, what it does etc etc etc) without having to read a man
> page, run it with --help, adjust a config file or anything else. The
> kind of tool you have to be an idiot not to use sucessfully (even when
> trying to make it not work).
>
> Is that a bit clearer??? If you are still in doubt, install either RH9
> or Windows XP (your choice ;-)) ...

*nod* that's why I suggested integrating it into msec.  And making msec
send the report to the security admin for all security levels.  draksec
is already easy to find in mcc.  

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

"What upsets me is not that you lied to me, but that from now on I can
no longer believe you." -- Nietzsche

Reply via email to