[
https://issues.apache.org/jira/browse/GEODE-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742571#comment-15742571
]
ASF GitHub Bot commented on GEODE-2119:
---------------------------------------
Github user kjduling commented on a diff in the pull request:
https://github.com/apache/geode/pull/311#discussion_r91999625
--- Diff:
geode-core/src/main/java/org/apache/geode/management/internal/cli/shell/Gfsh.java
---
@@ -14,38 +14,10 @@
*/
--- End diff --
Found it. It's an option in IDEA under 'reformat code' to 'rearrange code'
and 'optimize imports'. Those were turned off, but the upgrade to 2016.3
seemed to re-enable them.
> gfsh user and password visible in clear text
> --------------------------------------------
>
> Key: GEODE-2119
> URL: https://issues.apache.org/jira/browse/GEODE-2119
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Karen Smoler Miller
> Assignee: Kevin Duling
>
> Both gfsh connect and gfsh start server allow the specification on the
> command line of a user name and a password for use as credentials in
> authentication. Clear text versions of the user name and password are then
> visible
> 1. if the user runs gfsh history
> 2. in historyfile, if the user runs gfsh history --file=historyfile
> 3. in the output of ps
> It would be worth a check to see if clear text versions of the user or
> password end up in any locator or server logs. I don't believe it does for
> gfsh connect, but it might for the start server case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
