Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ogvMk-0004EE-Rm for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Oct 2022 21:58:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ogvMj-00085U-Iw for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Oct 2022 21:58:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ogvMj-00085L-41 for pgsql-hackers@lists.postgresql.org; Fri, 07 Oct 2022 21:58:45 +0000 Received: from mail-pj1-x1036.google.com ([2607:f8b0:4864:20::1036]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ogvMg-0001ML-1k for pgsql-hackers@postgresql.org; Fri, 07 Oct 2022 21:58:44 +0000 Received: by mail-pj1-x1036.google.com with SMTP id p3-20020a17090a284300b0020a85fa3ffcso8374274pjf.2 for ; Fri, 07 Oct 2022 14:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=hNX3Ia/RhlUojVVg0UdOBLEMNRENP4ti/m7blydf32c=; b=qiL5lUGe5tW4Wc1CLyPthvrad14/cSKfQNnENflTnqmaL4TaYUdsMbybHOxqqHsNbE tbvaIDUnm9xJWEMZzIUoYtb1JpfAcMf7XEhXGtZZT7GKiST/kdr9H22G030HCj3O9swt c8FW8y7Gn8WIjv7gzA8iQEnlQudFjphe801aRRZZKnw5UnkkQ3ODrNLJoMkdwFif4Cat +EnOS5FeE8Cqe/EgnNgFogQW7D7mPS5DXvXATuX3VSdMIremuk8KThRejAT7NveSUcQV STLoayjPtuD7bPFsiM13H2vHs8jDWR852q8AB5iAzky1thqreM2GWR1cA/MsY4CdDsz7 OVzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=hNX3Ia/RhlUojVVg0UdOBLEMNRENP4ti/m7blydf32c=; b=lZARLKeqNeSU/RVJoo/0anLiZuNXdIw0JjkDlFSGWEQoUo3anbO1OY8Ui2fePlUrj4 4a8UfjECqOC37GVuD1nJE/rbQ0NMiy0H57j3WE1TtvwoZn0vNX8xittoyWnXsi4wp21c SQrUnlwma0YXd9/MXkrlsFVcJOaUqYepM0d6EJBgKTxsQh7W1yjxzEZQQ0QpCBqH3QAP JMVLf77sp3xbFHqWCTAeNfZmT1rq8zpUhqKHyxO2OeehtGJ0jllDoy7mKqTcxH71tsmy H9KCQC6yB6i8U68VSePaPRgd8Gcx+LsjCloyhBJQKuU82nP1uFmeDQLUMubBUU62nNyM ASNQ== X-Gm-Message-State: ACrzQf0BpN+54lFRXSyAHFMxeNg+jvB/GoL1c0QPTRFGaNy+qORjZNzS 3wOkADmP2hCCSzadG6s93N8= X-Google-Smtp-Source: AMsMyM6XSPD3aRjNXj8G81NppH6LksLE1MxFT29B7ccSOgiB5qZAZDBPx8BGkFFyKigm0nXH6QNOKg== X-Received: by 2002:a17:902:7290:b0:17f:d04b:bf57 with SMTP id d16-20020a170902729000b0017fd04bbf57mr5614094pll.147.1665179920935; Fri, 07 Oct 2022 14:58:40 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id a11-20020a170902900b00b00179c99eb815sm1992379plp.33.2022.10.07.14.58.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 07 Oct 2022 14:58:40 -0700 (PDT) Date: Fri, 7 Oct 2022 14:58:36 -0700 From: Nathan Bossart To: Tom Lane Cc: Michael Paquier , Joe Conway , Joshua Brindle , PostgreSQL-development Subject: Re: use has_privs_of_role() for pg_hba.conf Message-ID: <20221007215836.GB814385@nathanxps13> References: <20220404142551.GB663209@nathanxps13> <491dba16-55df-d5fd-1ae7-01b5140987f0@joeconway.com> <20221006174343.GA444656@nathanxps13> <20221007032711.GA499771@nathanxps13> <20221007194430.GA550749@nathanxps13> <3347532.1665173939@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="eAbsdosE1cNLO4uF" Content-Disposition: inline In-Reply-To: <3347532.1665173939@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --eAbsdosE1cNLO4uF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Oct 07, 2022 at 04:18:59PM -0400, Tom Lane wrote: > There's another problem there, which is that buildfarm animals > using -DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS will complain > about role names that don't start with "regress_". Huh, I hadn't noticed that one before. It looks like roles must start with "regress_" and database names must include "regression", so I ended up using "regress_regression_group" for the samegroup/samerole tests. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com --eAbsdosE1cNLO4uF Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v5-0001-Use-has_privs_of_role-for-samerole-samegroup-and-.patch" From 6fe6da4ec1fe6792aa991721b77d6c2adb27697b Mon Sep 17 00:00:00 2001 From: Nathan Bossart Date: Fri, 1 Apr 2022 11:40:51 -0700 Subject: [PATCH v5 1/1] Use has_privs_of_role for samerole, samegroup, and + in pg_hba.conf. 6198420 ensured that has_privs_of_role() is used for predefined roles, which means that the role privilege inheritance hierarchy is checked instead of mere role membership. However, inheritance is still not respected for pg_hba.conf. This change alters the authentication logic to consider role privileges instead of just role membership. Do not back-patch. Author: Nathan Bossart --- doc/src/sgml/client-auth.sgml | 18 ++++----- src/backend/libpq/hba.c | 19 ++++----- src/backend/utils/adt/acl.c | 23 +++++++++++ src/include/utils/acl.h | 1 + src/test/authentication/t/001_password.pl | 48 +++++++++++++++++++++++ 5 files changed, 91 insertions(+), 18 deletions(-) diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index c6f1b70fd3..b06b57f169 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -221,12 +221,12 @@ hostnogssenc database usersameuser specifies that the record matches if the requested database has the same name as the requested user. The value samerole specifies that - the requested user must be a member of the role with the same + the requested user must have privileges of the role with the same name as the requested database. (samegroup is an obsolete but still accepted spelling of samerole.) - Superusers are not considered to be members of a role for the - purposes of samerole unless they are explicitly - members of the role, directly or indirectly, and not just by + Superusers are not considered to have privileges of a role for the + purposes of samerole unless they explicitly have + privileges of the role, directly or indirectly, and not just by virtue of being a superuser. The value replication specifies that the record matches if a physical replication connection is requested, however, it @@ -252,10 +252,10 @@ hostnogssenc database user+. (Recall that there is no real distinction between users and groups in PostgreSQL; a + mark really means - match any of the roles that are directly or indirectly members + match any of the roles that directly or indirectly have privileges of this role, while a name without a + mark matches only that specific role.) For this purpose, a superuser is only - considered to be a member of a role if they are explicitly a member + considered to have privileges of a role if they explicitly have privileges of the role, directly or indirectly, and not just by virtue of being a superuser. Multiple user names can be supplied by separating them with commas. @@ -788,9 +788,9 @@ host all all 192.168.0.0/16 ident map=omicro # If these are the only three lines for local connections, they will # allow local users to connect only to their own databases (databases # with the same name as their database user name) except for administrators -# and members of role "support", who can connect to all databases. The file -# $PGDATA/admins contains a list of names of administrators. Passwords -# are required in all cases. +# and roles with privileges of role "support", who can connect to all +# databases. The file $PGDATA/admins contains a list of names of +# administrators. Passwords are required in all cases. # # TYPE DATABASE USER ADDRESS METHOD local sameuser all md5 diff --git a/src/backend/libpq/hba.c b/src/backend/libpq/hba.c index 4637426d62..faa675f4af 100644 --- a/src/backend/libpq/hba.c +++ b/src/backend/libpq/hba.c @@ -547,13 +547,13 @@ tokenize_auth_file(const char *filename, FILE *file, List **tok_lines, /* - * Does user belong to role? + * Does user have privileges of role? * * userid is the OID of the role given as the attempted login identifier. - * We check to see if it is a member of the specified role name. + * We check to see if it has privileges of the specified role name. */ static bool -is_member(Oid userid, const char *role) +has_privs(Oid userid, const char *role) { Oid roleid; @@ -566,11 +566,12 @@ is_member(Oid userid, const char *role) return false; /* if target role not exist, say "no" */ /* - * See if user is directly or indirectly a member of role. For this - * purpose, a superuser is not considered to be automatically a member of - * the role, so group auth only applies to explicit membership. + * See if user directly or indirectly has privileges of role. For this + * purpose, a superuser is not considered to automatically have + * privileges of the role, so group auth only applies to explicit + * privileges. */ - return is_member_of_role_nosuper(userid, roleid); + return has_privs_of_role_nosuper(userid, roleid); } /* @@ -587,7 +588,7 @@ check_role(const char *role, Oid roleid, List *tokens) tok = lfirst(cell); if (!tok->quoted && tok->string[0] == '+') { - if (is_member(roleid, tok->string + 1)) + if (has_privs(roleid, tok->string + 1)) return true; } else if (token_matches(tok, role) || @@ -628,7 +629,7 @@ check_db(const char *dbname, const char *role, Oid roleid, List *tokens) else if (token_is_keyword(tok, "samegroup") || token_is_keyword(tok, "samerole")) { - if (is_member(roleid, dbname)) + if (has_privs(roleid, dbname)) return true; } else if (token_is_keyword(tok, "replication")) diff --git a/src/backend/utils/adt/acl.c b/src/backend/utils/adt/acl.c index 4fac402e5b..cb5587d926 100644 --- a/src/backend/utils/adt/acl.c +++ b/src/backend/utils/adt/acl.c @@ -4928,6 +4928,29 @@ has_privs_of_role(Oid member, Oid role) } +/* + * Does member have the privileges of role, not considering superuserness? + * + * This is identical to has_privs_of_role except we ignore superuser + * status. + */ +bool +has_privs_of_role_nosuper(Oid member, Oid role) +{ + /* Fast path for simple case */ + if (member == role) + return true; + + /* + * Find all the roles that member has the privileges of, including + * multi-level recursion, then see if target role is any one of them. + */ + return list_member_oid(roles_is_member_of(member, ROLERECURSE_PRIVS, + InvalidOid, NULL), + role); +} + + /* * Is member a member of role (directly or indirectly)? * diff --git a/src/include/utils/acl.h b/src/include/utils/acl.h index 9a4df3a5da..eded5e0f96 100644 --- a/src/include/utils/acl.h +++ b/src/include/utils/acl.h @@ -209,6 +209,7 @@ extern AclMode aclmask(const Acl *acl, Oid roleid, Oid ownerId, extern int aclmembers(const Acl *acl, Oid **roleids); extern bool has_privs_of_role(Oid member, Oid role); +extern bool has_privs_of_role_nosuper(Oid member, Oid role); extern bool is_member_of_role(Oid member, Oid role); extern bool is_member_of_role_nosuper(Oid member, Oid role); extern bool is_admin_of_role(Oid member, Oid role); diff --git a/src/test/authentication/t/001_password.pl b/src/test/authentication/t/001_password.pl index 93df77aa4e..abbf310d3e 100644 --- a/src/test/authentication/t/001_password.pl +++ b/src/test/authentication/t/001_password.pl @@ -200,4 +200,52 @@ append_to_file( test_conn($node, 'user=md5_role', 'password from pgpass', 0); +unlink($pgpassfile); +delete $ENV{"PGPASSFILE"}; + +# Create database and roles for inheritance tests +reset_pg_hba($node, 'all', 'all', 'trust'); +$node->safe_psql('postgres', "CREATE DATABASE regress_regression_group;"); +$node->safe_psql('postgres', "CREATE ROLE regress_regression_group LOGIN PASSWORD 'pass';"); +$node->safe_psql('postgres', "CREATE ROLE regress_member_inherit LOGIN SUPERUSER INHERIT IN ROLE regress_regression_group PASSWORD 'pass';"); +$node->safe_psql('postgres', "CREATE ROLE regress_member_noinherit LOGIN SUPERUSER NOINHERIT IN ROLE regress_regression_group PASSWORD 'pass';"); + +# Test role inheritance is respected for + +$ENV{"PGPASSWORD"} = 'pass'; +reset_pg_hba($node, 'all', '+regress_regression_group', 'scram-sha-256'); +test_conn($node, 'user=regress_regression_group', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_regression_group" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_inherit', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_member_inherit" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_noinherit', 'scram-sha-256', 2, + log_unlike => + [qr/connection authenticated: identity="regress_member_noinherit" method=scram-sha-256/]); + +# Test role inheritance is respected for samerole +$ENV{"PGDATABASE"} = 'regress_regression_group'; +reset_pg_hba($node, 'samerole', 'all', 'scram-sha-256'); +test_conn($node, 'user=regress_regression_group', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_regression_group" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_inherit', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_member_inherit" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_noinherit', 'scram-sha-256', 2, + log_unlike => + [qr/connection authenticated: identity="regress_member_noinherit" method=scram-sha-256/]); + +# Test role inheritance is respected for samegroup +reset_pg_hba($node, 'samegroup', 'all', 'scram-sha-256'); +test_conn($node, 'user=regress_regression_group', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_regression_group" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_inherit', 'scram-sha-256', 0, + log_like => + [qr/connection authenticated: identity="regress_member_inherit" method=scram-sha-256/]); +test_conn($node, 'user=regress_member_noinherit', 'scram-sha-256', 2, + log_unlike => + [qr/connection authenticated: identity="regress_member_noinherit" method=scram-sha-256/]); + done_testing(); -- 2.25.1 --eAbsdosE1cNLO4uF--