From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giovanni Biscuolo Subject: bug#38198: missing shell for postgresql system user Date: Thu, 14 Nov 2019 11:02:15 +0100 Message-ID: <878soiojx4.fsf@roquette.mug.biscuolo.net> References: <87k183oeyz.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41282) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVBxw-00087D-Em for bug-guix@gnu.org; Thu, 14 Nov 2019 05:03:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iVBxu-0008Hp-Ml for bug-guix@gnu.org; Thu, 14 Nov 2019 05:03:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:52157) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iVBxu-0008Hj-JZ for bug-guix@gnu.org; Thu, 14 Nov 2019 05:03:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iVBxu-0008Ln-Ed for bug-guix@gnu.org; Thu, 14 Nov 2019 05:03:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: =?UTF-8?Q?G=C3=A1bor?= Boskovits Cc: 38198-done@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello G=C3=A1bor, G=C3=A1bor Boskovits writes: [...] >> To access a database server on localhost for the first time as the user >> postgres (the superuser) a person should use: >> >> --8<---------------cut here---------------start------------->8--- >> sudo su postgres -c 'psql' >> --8<---------------cut here---------------end--------------->8--- [...] > I would not mind this change, I think it is ok. However it is easy to > work around this with su -s. > I usually do that. Oh, that's the real solution: thanks! (I should study more...) sudo su postgres -s psql Since giving a shell to the postgres user is **not** the solution, I'm closing this bug. I'll try to send a patch to the relevant documentation in the manual, since now that we changed "trust" to "peer" a regular user cannot connect to a newly initialized database using `psql -U postgres` (and is good for security reasons); the user must be part of the "wheel" group (or be authorized via sudoers in other ways) to be able to use `sudo su postgres -s psql` [...] Thanks! Gio' =2D-=20 Giovanni Biscuolo Xelera IT Infrastructures --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAl3NJicACgkQ030Op87M ORLflg//dH52VvP654R5GcF56eQxmJFEzLguTfPTQRan9dHFPeZqKX8O8CiEyUW7 5miKDRYXJJl5BpZzq+bqnh6HE5ALIl/uXYZeqeMhiYmQPDcv4pT7Odk4bMmLjOIc 4IA9y06tZukdWnORXJ70V2Uf4Bkzlcka4JOTE3VdsZYWyIqdNJedwZL4zaclkGz1 MfDbH2ukRToksGSGDg0M8+9hZka99t8s9Wo+iPOy7Gqt4Ngdd8fYP7fihoZrfLoh H+UAQMz5Je5VPcSVczjTMHDYPJY2beRc6TY6zMWhQAA00cT7B0Rf7+roFCN1t9sI Iu5RJKD4tc2afGV+eLWf6AzRwyw4+LxkJrnUtLMMOEOim933xw0e/Dvt8NCKaPjd nf2OCNHWtLRpb1neWcZPeo5bVu52rUwZt0iU/j2lcHIwcBhn7RUVWZqtNVmNA7gc W1Jq3hqP/9JtdiDitJii/NPe5gUHMQiM/dABskUBpAi8YAkgUXVRJU/DuGZxyCKG R632iLDQBQwRGTb9KUM6IQbl78LNThPYd+IMabpi9hYm8ldOywrezG1dk595Lmwg pVq1p8mKqjIzxBuU8jR+R9a3wpv8AjDvuLBX2cCcwDV/jFvOYPAFERNUvWXTMFiH A2lLKnvHVEyW/wOkljGBtCntzpR991nGar1E5GMA+pibmheaedQ= =ywpI -----END PGP SIGNATURE----- --=-=-=--