Privacy

[Lindenaar, D.J.W.]

> -----Original Message-----
> From: Josh Sled [mailto:jsled-gnucash at asynchronous.org]
> Sent: woensdag 17 maart 2004 3:00
> To: Lindenaar, D.J.W.
> Cc: gnucash-user at lists.gnucash.org
> Subject: RE: Privacy
> 
> On Fri, 2004-03-12 at 15:04, Lindenaar, D.J.W. wrote:
> 
> > 1. create a user (probably 'bookkeeper' or something)
> > 2. move all bookkeeping info from the default user's home to
> > bookkeepers' home.
> > 3. tell KDE or GNOME to run gnucash as a different user (being
> > 'bookkeeper') or change the command from /usr/bin/gnucash to su
> > bookkeeper -c /usr/bin/gnucash.
> >
> > Like this it can be done. The OS asks the password for 'bookkeeper'
and
> > if correct fires up gnucash. If your son starts gnucash he doesn't
know
> > the password and so can't start gnucash nor can he delete the
> > accountfile or anything.
> 
> FWIW, there's also the program 'xsu' and 'gnomesu' which allow a GUI
> mechanism to ask for the password.
> 
> http://sourceforge.net/projects/xsu/
> 
> % gnomesu gnucash -u gnucash &
> # dialog box appears...
> 
> It's already in portage, on gentoo at least...
and redhat, debian, slackware, suse, caldera ,..etcetc
On some distributions, though, gmonesu is called gksu, but (it think)
it's exactly the same one. Or at least is has the same functionality

Greetz Daniel


> 
> ...jsled
> 
> --
> http://www.asynchronous.org/ - `a=jsled; b=asynchronous.org; echo
> ${a}@${b}`
> # A: Because it breaks the flow of normal conversation.
> # Q: Why don't we put the response before the request?