You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[11:12]% cockroach sql --insecure -u nosuchuser
# Welcome to the cockroach SQL interface.
# All statements must be terminated by a semicolon.
# To exit: CTRL + D.
#
# Client version: CockroachDB CCL v1.2-alpha.20170901-2084-ge457f9a19 (darwin amd64, built 2017/11/30 14:50:40, go1.9.1)
# Server version: CockroachDB CCL v1.2-alpha.20171211-123-g6172ba8d6 (darwin amd64, built 2017/12/11 22:32:52, go1.9.1)
# Cluster ID: b6057ca9-c5ef-47f4-800c-60ebc3749eff
#
# Enter \? for a brief introduction.
#
nosuchuser@:26257/> select 1;
+---+
| 1 |
+---+
| 1 |
+---+
(1 row)
This problem is not present in secure mode:
[11:14]% ./cockroach sql -u nosuchuser
# Welcome to the cockroach SQL interface.
# All statements must be terminated by a semicolon.
# To exit: CTRL + D.
#
Enter password:
Error: pq: user nosuchuser does not exist
Failed running "sql"
The text was updated successfully, but these errors were encountered:
True. But existing sessions are different from login checks. Let's keep #20718 for the former and leave this issue for user existence checks at login time in insecure mode.
Previously, only secure mode would validate that the user connecting
actually existed. This isn't a security bug--anyone can log in as root
in insecure mode, for example--but was confusing nonetheless.
Fixescockroachdb#20717.
Release note (bug fix): It is no longer possible to log in as a
nonexistent user in insecure mode.
This problem is not present in secure mode:
The text was updated successfully, but these errors were encountered: