Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.rutherglen@gmail.com
 designates 209.85.217.13 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=ek1xgfRZuyRo5vq3erEppsJG31fHm4jvNUpFC0QEBk55jJDGYzjBjWhDYJelSMKFyj
         2kO6F/0YiuLOjjkCu+Xx1fLkurNZk8aKcbZPY1PIHj8TDFzu3e24CTyH7XcOdRkYxYRZ
         b6Qx+VWpa5eM3naRkm5ywKzb7i9TUEh1rOVsI=
Message-ID: <85d3c3b60809300633r2b1bb9fcoaf938c30bdcaa0b7@mail.gmail.com>
Date: Tue, 30 Sep 2008 09:33:46 -0400
From: "Jason Rutherglen" <jason.rutherglen@gmail.com>
To: core-user@hadoop.apache.org
Subject: Re: Question about Hadoop 's Feature(s)
In-Reply-To: <48E221EF.2020105@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3DADD35EDAE49145B9BA1AB44844771178F3E4@lvsrv_dns.luvina.net>
	 <D13D8F4C-BD0A-453D-AB79-CA510C00C114@apache.org>
	 <48DB7A59.1030506@apache.org>
	 <85d3c3b60809291732r3e1e9227kf60adb6f79738698@mail.gmail.com>
	 <48E221EF.2020105@apache.org>

> However, HDFS uses HTTP to serve blocks up -that needs to be locked down
>  too. Would the signing work there?

I am not familiar with HDFS over HTTP.  Could it simply sign the
stream and include the signature at the end of the HTTP message
returned?

On Tue, Sep 30, 2008 at 8:56 AM, Steve Loughran <stevel@apache.org> wrote:
> Jason Rutherglen wrote:
>>
>> I implemented an RMI protocol using Hadoop IPC and implemented basic
>> HMAC signing.  It is I believe faster than public key private key
>> because it uses a secret key and does not require public key
>> provisioning like PKI would.  Perhaps it would be a baseline way to
>> sign the data.
>
> That should work for authenticating messages between (trusted) nodes.
> Presumably the ipc.key value could be set in the Conf and all would be well.
>
> External job submitters shouldn't be given those keys; they'd need an
> HTTP(S) front end that could authenticate them however the organisation
> worked.
>
> Yes, that would be simpler. I am not enough of a security expert to say if
> it will work, but the keys should be easier to work with. As long as the
> configuration files are kept secure, your cluster will be locked.
>
> However, HDFS uses HTTP to serve blocks up -that needs to be locked down
>  too. Would the signing work there?
>
> -steve
>