Ensure login via "local" UNIX Domain Socket is configured correctly

MediumLevel 1Manual reviewyugabytedb

Description

A remote host login, via SSH, is arguably the most secure means of remotely accessing and administering the YugabyteDB server. Once connected to the YugabyteDB server, using the ysqlsh client, via UNIX DOMAIN SOCKETS, while using the peer authentication method is the most secure mechanism available for local database connections.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

As the yugabyte OS user run ./bin/ysqlsh -U yugabyte -d yugabyte (should succeed), then as another OS user (su - user1) run the same command: it must fail (e.g. Peer authentication failed). Review local rules in --ysql_hba_conf_csv / pg_hba_file_rules: no trust for local connections other than the intended superuser path.

How it is fixed

Fix method: Guidance or infrastructure patch

Creation of a database account that matches the local account allows PEER authentication: # ./bin/ysqlsh -c "CREATE ROLE user1 WITH LOGIN;" CREATE ROLE Execute the following as the UNIX user account, the default authentication rules should now permit the login: # su - user1 # whoami user1 # ./bin/ysqlsh -d yugabyte yugabyte=# As per the host-based authentication rules in $PGDATA/pg_hba.conf, all login attempts via UNIX DOMAIN SOCKETS are ...

Properties

Operating systems: Any
Tags: yugabytedbauthentication
Reference: CIS YugabyteDB Benchmark v2.0.0 - 6.1 Ensure login via "local" UNIX Domain Socket is configured correctly