Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C44110FFA for ; Thu, 15 Aug 2013 04:07:53 +0000 (UTC) Received: (qmail 43721 invoked by uid 500); 15 Aug 2013 04:07:53 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 42920 invoked by uid 500); 15 Aug 2013 04:07:49 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 42702 invoked by uid 99); 15 Aug 2013 04:07:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Aug 2013 04:07:48 +0000 Date: Thu, 15 Aug 2013 04:07:48 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1009) Support encryption over the wire MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740655#comment-13740655 ] Keith Turner commented on ACCUMULO-1009: ---------------------------------------- Took a quick look at the patch. The patch adds a lot of constructors to ZooKeeperInstance. I'm thinking of just adding the following constructor : {code:java} /** * @param config provides all information needed to connect to an Accumulo instance. @see ClientConfiguration */ public ZooKeeperInstance(AccumuloConfiguration config){} {code} This would allow us maximum flexibility in the future w/o clutering the API as new features are added. The zookeepers, instance name, wether or not use ssl, etc. would be obtained from the config. This constructor would be the way to enable ssl. There is some code that pushes the client address and port across threads so its shows up in list scans, do you know if this is still working with the changes you made? > Support encryption over the wire > -------------------------------- > > Key: ACCUMULO-1009 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1009 > Project: Accumulo > Issue Type: New Feature > Reporter: Keith Turner > Assignee: Michael Berman > Fix For: 1.6.0 > > Attachments: ACCUMULO-1009_thriftSsl.patch > > > Need to support encryption between ACCUMULO clients and servers. Also need to encrypt communications between server and servers. > Basically need to make it possible for users to enable SSL+thrift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira