pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Wolfgang Walther <walther@technowledgy.de>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: User with BYPASSRLS privilege can't change password
Date: Tue, 3 Nov 2020 13:06:42 -0500
Message-ID: <20201103180641.GX16415@tamriel.snowman.net> (raw)
In-Reply-To: <956994.1604425451@sss.pgh.pa.us>
References: <a5548a9f-89ee-3167-129d-162b5985fcf8@technowledgy.de>
	<923005.1604420579@sss.pgh.pa.us>
	<956994.1604425451@sss.pgh.pa.us>

Greetings,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> I wrote:
> > Wolfgang Walther <walther@technowledgy.de> writes:
> >> CREATE USER bob BYPASSRLS;
> >> SET ROLE bob;
> >> ALTER USER bob PASSWORD 'x';
> >> -- ERROR: must be superuser to change bypassrls attribute
> 
> > Yeah, duplicated here on HEAD.  The error message seems to think
> > the command is trying to remove the BYPASSRLS privilege, which
> > suggests somebody forgot to copy that flag somewhere where it needs
> > to be copied.  Haven't dug further than that.
> 
> It's a little more subtle than that, but not much.  Commit 491c029db
> copied-and-pasted the logic used to deny non-superusers the privilege
> to change anything about a superuser role.  That was certainly not the
> intention, because the error message was phrased differently from the
> superuser case, but that was the effect.  I propose the attached.
> 
> (Hm, looks like this behavior is undocumented, too.)

The intent was certainly that non-superusers shouldn't be able to tweak
the BYPASSRLS bit, but it wasn't intended to prevent users who have
BYPASSRLS from being able to change their own password.

I certainly recall the discussion about that requirement and we should
document it.

> diff --git a/src/backend/commands/user.c b/src/backend/commands/user.c
> index 9ce9a66921..5cd479a649 100644
> --- a/src/backend/commands/user.c
> +++ b/src/backend/commands/user.c
> @@ -709,8 +709,10 @@ AlterRole(AlterRoleStmt *stmt)
>  	roleid = authform->oid;
>  
>  	/*
> -	 * To mess with a superuser you gotta be superuser; else you need
> -	 * createrole, or just want to change your own password
> +	 * To mess with a superuser or replication role in any way you gotta be
> +	 * superuser.  We also insist on superuser to change the BYPASSRLS
> +	 * property.  Otherwise, if you don't have createrole, you're only allowed
> +	 * to change your own password.
>  	 */
>  	if (authform->rolsuper || issuper >= 0)
>  	{
> @@ -726,7 +728,7 @@ AlterRole(AlterRoleStmt *stmt)
>  					(errcode(ERRCODE_INSUFFICIENT_PRIVILEGE),
>  					 errmsg("must be superuser to alter replication users")));
>  	}
> -	else if (authform->rolbypassrls || bypassrls >= 0)
> +	else if (bypassrls >= 0)
>  	{
>  		if (!superuser())
>  			ereport(ERROR,

This change looks correct, we shouldn't be worrying about what's already
been set on the role.

> @@ -739,7 +741,6 @@ AlterRole(AlterRoleStmt *stmt)
>  			  createrole < 0 &&
>  			  createdb < 0 &&
>  			  canlogin < 0 &&
> -			  isreplication < 0 &&
>  			  !dconnlimit &&
>  			  !rolemembers &&
>  			  !validUntil &&

This seems like an independent change..?  Not saying it's wrong though.

Thanks,

Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (14+ messages)  latest in thread

Message-ID: <20201103180641.GX16415@tamriel.snowman.net>
Permalink:  ../20201103180641.GX16415@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20201103180641.GX16415@tamriel.snowman.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: sfrost@snowman.net, tgl@sss.pgh.pa.us, walther@technowledgy.de, pgsql-bugs@lists.postgresql.org
  Subject: Re: User with BYPASSRLS privilege can't change password
  In-Reply-To: <20201103180641.GX16415@tamriel.snowman.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox