Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 93675200BA6 for ; Tue, 18 Oct 2016 23:45:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 92235160AE5; Tue, 18 Oct 2016 21:45:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CF2C4160ACE for ; Tue, 18 Oct 2016 23:45:09 +0200 (CEST) Received: (qmail 3568 invoked by uid 500); 18 Oct 2016 21:45:09 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 3547 invoked by uid 99); 18 Oct 2016 21:45:08 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2016 21:45:08 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 9F98BE0209; Tue, 18 Oct 2016 21:45:08 +0000 (UTC) From: jbertram To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #835: ARTEMIS-786 Store user's password in hash form ... Content-Type: text/plain Message-Id: <20161018214508.9F98BE0209@git1-us-west.apache.org> Date: Tue, 18 Oct 2016 21:45:08 +0000 (UTC) archived-at: Tue, 18 Oct 2016 21:45:10 -0000 Github user jbertram commented on the issue: https://github.com/apache/activemq-artemis/pull/835 The whole masking/hashing process still seems like a bit of a jumble to me. To mask a password there's a raw Java command (e.g. "java -cp <classPath> org.apache.activemq.artemis.utils.DefaultSensitiveStringCodec <password-to-encode>") and then there's a new command you've added to hash a password. I think it would provide a much better user experience to unify both, if possible. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---