Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 375A49BB5 for ; Thu, 6 Sep 2012 05:32:00 +0000 (UTC) Received: (qmail 63194 invoked by uid 500); 6 Sep 2012 05:31:58 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 62851 invoked by uid 500); 6 Sep 2012 05:31:53 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 62819 invoked by uid 99); 6 Sep 2012 05:31:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 05:31:53 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mohandes.zebeleh.67@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-ob0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 05:31:46 +0000 Received: by obhx4 with SMTP id x4so2114358obh.14 for ; Wed, 05 Sep 2012 22:31:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DppzrZR3ko5FaChcRurdGNwjQ+nw5RmHb1tvUKjNJQ8=; b=Yt65s8HytMtentK8rlZ+kL7WW210qOMTUBMiXAtwuGFAVbKu7W8lyD5cVbIHUocEVn gubLY8h1rnkq0No1/3880QkreZJKDGtpQ1reTAShd2kb4n4DQpWgJzPBkiELDWfnhFx/ BdJcG6hoTjqkvNV6N7B4HqQGz2QacQfdU1mafqa08oNMExqnV4XD/YUSV+AOJ358CiIC RXOPlpiwly9V1NrcNNP5HXEkhzQAZ09StpEP5isrvjuaavyjMSIvqWsneVk5IHd9jCPn KzmGWeoR63AiNEAMim1F3paOANf47efoUlokFrzGswvR3eX4pKL25TdBmzZuDJ1hyoVl 90rQ== MIME-Version: 1.0 Received: by 10.182.207.6 with SMTP id ls6mr683597obc.36.1346909485338; Wed, 05 Sep 2012 22:31:25 -0700 (PDT) Received: by 10.76.23.138 with HTTP; Wed, 5 Sep 2012 22:31:25 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Sep 2012 10:01:25 +0430 Message-ID: Subject: Re: why hbase doesn't provide Encryption From: Farrokh Shahriari To: Julian Wissmann Cc: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f646e2b6b0f4604c901cd1b --e89a8f646e2b6b0f4604c901cd1b Content-Type: text/plain; charset=ISO-8859-1 Hi there I want encryption before pushing data into hbase,and I've done it by changing in some library to encrypt data.But it doesn't have any performance,I mean for each row it should encrypt/decrypt the cell,so for a query that has a lot of rows ,it will take a long time. my question is this,why hbase doesn't have any option for that ( in hbase shell like compression method ),for example like other relational databases(sqlserver,.. ),is there any reason for that ? Thanks you guys On Thu, Sep 6, 2012 at 2:23 AM, Julian Wissmann wrote: > What problem are you trying to solve? Do you want encryption between > server and client, between servers or encryption of data within Hbase? You > need to be more specific. > > If one of the first two is what you want: This kind of stuff can easily be > achieved with stunnel or OpenVPN and can probably be considered a very > esoteric requirement, as there are probably not many Hbase users out there, > who have a cluster running across machines that are exposed to open > networks. > If you are looking for the latter, imo the correct way to do it would be > encrypting data _before_ pushing it into the database. Java actually > provides an excellent crypto framework for doing such things. > > > 2012/9/5 Farrokh Shahriari > >> Hello >> I just wanna know why hbase doesn't provide Encryption ? >> >> Tnx >> > > --e89a8f646e2b6b0f4604c901cd1b--