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 BFCBA2009A8 for ; Tue, 17 May 2016 18:06:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BE56C1609F5; Tue, 17 May 2016 16:06:19 +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 132F71607A8 for ; Tue, 17 May 2016 18:06:18 +0200 (CEST) Received: (qmail 59631 invoked by uid 500); 17 May 2016 16:06:17 -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 59619 invoked by uid 99); 17 May 2016 16:06:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 May 2016 16:06:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1323CC9944 for ; Tue, 17 May 2016 16:06:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id oiJonq7vBkwj for ; Tue, 17 May 2016 16:06:16 +0000 (UTC) Received: from mail-yw0-f179.google.com (mail-yw0-f179.google.com [209.85.161.179]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 1BAE160DB3 for ; Tue, 17 May 2016 16:06:16 +0000 (UTC) Received: by mail-yw0-f179.google.com with SMTP id g133so20260350ywb.2 for ; Tue, 17 May 2016 09:06:16 -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; bh=G23e7D2LNZXhcR04tm6z3sEgBKN7NJX8T952BvzSL4g=; b=dujnB9JE6nq35S7NSFOnn5iIF6CQZ39SIgxd9Mrb7xEb4kwXfWNgvbJhAQf2JB3/u/ grjM+wgZgYRNMbkfO6/NNyyIL6YMc1uuIi2Bv6GNz9s4ymsIzlz3P5Rpe2iQYftCXigZ mcpIXL90tVNfCoooR5w/9NJpHkCQlg7raqtpAogkyKOg5heBDwZVqF639RwIYRoBCL7A Uisso3ECkOcrceYp2IdlXnKBPScZn2mdoYNV9MDA4vLABH5tgxtCtrEvRLIyijHb1J3P ax3zyrWTlqEYb9KB6il1860wnErFTJd0d7808PVj5nGSz2dmZv+c5lMjCX9YmBa9f3tx Koog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=G23e7D2LNZXhcR04tm6z3sEgBKN7NJX8T952BvzSL4g=; b=NUki2iyDyzWdn5DrHYp8Mk3rZ3XHtDN3cfoLDjQT8PQjh+I75PCiGzipMa2hyTcfi3 Nq1aZJlqmUBI4/wTspcjfyuIVvWZ2gk+Vvn4bxsMxwDSlt/HKJPu572slzuMbrdRTW2B EFs00e7SSaWuEeCqkPrEGeg4wnXfvpRMzUpPv5U2c5AlRopJrHQser4SdDbE+ZjzvSdr O1hGacEqVmfZ7hLUEusxolfvwobPPFqm9ITAdSyqfp14/YKimXdJi1goLm6Yx6Ws/wsQ Yr0csSyC+agBggP3KgQuySFj8sUWdsYchqlO4dy5oIj97soRz0sBzLaOlg8kEj3iFlEJ 3HRQ== X-Gm-Message-State: AOPr4FXOyZ8ATe7v6E3xuPXOiHGQYW3Kk1xxU9meqN+2N7ppjm8ygtJil1P45wtlrpIpczX8IdHCl82AwUzGcw== MIME-Version: 1.0 X-Received: by 10.13.213.67 with SMTP id x64mr1147234ywd.261.1463501175217; Tue, 17 May 2016 09:06:15 -0700 (PDT) Received: by 10.37.37.4 with HTTP; Tue, 17 May 2016 09:06:15 -0700 (PDT) In-Reply-To: <7b0e54f0.6238.154bf5511f6.Coremail.wangyongqiang0617@163.com> References: <7fa09c9.10138.154be615468.Coremail.wangyongqiang0617@163.com> <7b0e54f0.6238.154bf5511f6.Coremail.wangyongqiang0617@163.com> Date: Tue, 17 May 2016 09:06:15 -0700 Message-ID: Subject: Re: Re: how to make a safe use of hbase From: Ted Yu To: WangYQ Cc: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a114fc14ead660305330bebeb archived-at: Tue, 17 May 2016 16:06:19 -0000 --001a114fc14ead660305330bebeb Content-Type: text/plain; charset=UTF-8 Please read the following: http://hbase.apache.org/book.html#security On Tue, May 17, 2016 at 8:28 AM, WangYQ wrote: > I have 2 goals > 1. protect 60010 web page > 2. control the access to hbase, such as read and write > for example, when want to access hbase, must have the correct password > > > thanks > > > On 2016-05-17 22:04 , Ted Yu Wrote: > > Is your goal to protect web page access ? > > Take a look at HBASE-5291. > > If I didn't understand your use case, please elaborate. > > Use user@hbase in the future. > > On Tue, May 17, 2016 at 4:02 AM, WangYQ wrote: > >> in hbase, if we know zookeeper address, we can write and read hbase >> if we know hmaster's address, we can see 60010 page >> >> >> how can we make a safe use of hbase >> such as, if we want to see 60010, to write/read hbase, we must have the >> correct password, like linux > > > > > --001a114fc14ead660305330bebeb--