[Top][All Lists]

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

Re: [Gnumed-devel] Restoring a database under Debian

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Restoring a database under Debian
Date: Thu, 15 Jan 2015 17:03:15 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Thu, Jan 15, 2015 at 03:42:51PM +0000, Jim Busser wrote:

> > "postgres" is is not supposed to have any password on Debian.
> > In fact, that is one of the defences against anyone actually
> > logging in as postgres. Root can always become "postgres"
> > without need for a password.
> Would there be case where database support personnel who is trusted with sudo 
> access (but not root) would be unable to fully enough become "postgres" thus 
> necessitating to assign a password to postgres in order that the support 
> personnel can do what may be necessary?

Not that I can think of.

> And since I do not have such support personnel, is there anyway to revoke 
> ("unset") having set a password on a system account?

        passwd -l postgres

as root should work.

> > But postgres won't have any permissions to look inside the
> > parent paths (/root/gnumed). That's why the default is
> > /tmp/gnumed :-)
> This default "is" (or would best be set by users) to be
>       /tmp/gnumed
> where … in the restore conf?

Yes. The tarball .conf.example already has that value. It
didn't propagate into the installed .conf on Debian so far,

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]