[
https://issues.apache.org/jira/browse/CASSANDRA-16983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503862#comment-17503862
]
Brad Schoening edited comment on CASSANDRA-16983 at 3/9/22, 9:46 PM:
---------------------------------------------------------------------
[~Bowen Song] yes, I'm providing credentials in CQL_TEST_USER and CQL_TEST_PWD,
but test_cqlsh_output in test_no_prompt_or_colors_output is still looking for
my cqlshrc and printing out the warning message. Ideally, you'd be able to
specify credentials either way, file based or with ENV variables because it
can't be done interactively like cqlsh can to request a pwd.
This seems to happen when a statement is executed with testcall_cqlsh(), not
with testrun_cqlsh()
was (Author: bschoeni):
[~Bowen Song] yes, I'm providing credentials in CQL_TEST_USER and CQL_TEST_PWD,
but test_cqlsh_output in test_no_prompt_or_colors_output is still looking for
my cqlshrc and printing out the warning message. Ideally, you'd be able to
specify credentials either way, file based or with ENV variables because it
can't be done interactively like cqlsh can to request a pwd.
> Separating CQLSH credentials from the cqlshrc file
> --------------------------------------------------
>
> Key: CASSANDRA-16983
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16983
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/cqlsh
> Reporter: Bowen Song
> Assignee: Bowen Song
> Priority: Normal
> Labels: lhf
> Fix For: 4.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently, the CQLSH tool accepts credentials (username & password) from the
> following 3 places:
> 1. the command line parameter "-p"
> 2. the cqlshrc file
> 3. prompt the user
> This is not ideal.
> Credentials in the command line is a security risk, because it could be see
> by other users on a shared system.
> The cqlshrc file is better, but still not good enough. Because the cqlshrc
> file is a config file, it's often acceptable to have it as a world readable
> file, and share it with other users. It also prevents user from having
> multiple sets of credentials, either for the same Cassandra cluster or
> different clusters.
> To improve the security of CQLSH and make it secure by design, I purpose the
> following changes:
> * Warn the user if a password is giving in the command line, and recommend
> them to use a credential file instead
> * Warn the user if credentials are present in the cqlshrc file and the
> cqlshrc file is not secure (e.g.: world readable or owned by a different user)
> * Deprecate credentials in the cqlshrc, and recommend the user to move them
> to a separate credential file. The aim is to not break anything at the
> moment, but eventually stop accepting credentials from the cqlshrc file.
> * Reject the credentials file if it's not secure, and tell the user how to
> secure it. Optionally, prompt the user for password if it's an interactive
> session. (Think how does OpenSSH handle insecure credential files)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
