Re: Privacy


Jody, sorry, I'll try to recap succinctly:

-- User is running gnome or kde desktop at home, and shares the
   desktop with the rest of the family.
-- User wants to password-protect thier gnucash data sets (and/or
   thier word docs and or thier pornography/or whatever) so that
   the rest of the family (or at least the kids) don't get access.

-- To acheive the above, logging in/out of gdm/xdm/kdm sessions 
   is impractical for a variety of reasons.
-- To achieve the above, running multiple x servers & xlock
   is impratical/inelegant.
-- To acheive the above, throwing the burden on the app writer
   leads to hacks and inconsistent GUI's, as each app implements
   thier own obscure, hard-to-maintain solution.
-- To acheive the above, calling it a "sysadmin issue" or
   "solving" it with a HOWTO is impractical/inelegant.

Conclude: there needs to be a standardized, architected, 
desktop-seal-of-approval'ed way of dealing with granular
security levels from the gnome or KDE desktops.

-- linas

> > -- one should stick to OS-provided security mechanisms for many good reasons
> Agreed.
> > -- yes, one could run multiple x servers on different desktops using
> >    ctrl-alt-PFn to toggle between them and use xlock on these,
> >    but this is wasteful of RAM, and is not a pretty solution for other 
> >    reasons.
> Huh?  What does that have to do with the price of yakk droppings ?
> We're clearly missing part of this conversation.  Can you point us
> back to the start of the thread get a feel for what you are trying
> to do ?
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel lists gnucash org

pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas linas org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]