Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Received-SPF: pass (nike.apache.org: domain of freeman.fang@gmail.com
 designates 209.85.220.50 as permitted sender)
From: Freeman Fang <freeman.fang@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_E0875ED6-2C34-43F3-A417-A70FCAEF505D"
Subject: Re: [PROPOSAL] Remove default ssh key
Date: Fri, 18 Jul 2014 08:38:50 +0800
In-Reply-To: <53C82787.2000009@nanthrax.net>
To: dev@karaf.apache.org
References: <53C82787.2000009@nanthrax.net>
Message-Id: <4E273821-4739-4CC1-88CA-0F35859E9BF4@gmail.com>

--Apple-Mail=_E0875ED6-2C34-43F3-A417-A70FCAEF505D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1 to comment out the default public key in keys.properties, it's really =
a security hole.

And about specify the key to bin/client, I just added it weeks ago, =
please see KARAF-3059[1]

[1]https://issues.apache.org/jira/browse/KARAF-3059


=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=
=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D
Freeman(Yue) Fang

Red Hat, Inc.=20
FuseSource is now part of Red Hat


On 2014-7-18, at =E4=B8=8A=E5=8D=883:44, Jean-Baptiste Onofr=C3=A9 =
wrote:

> Hi all,
>=20
> Following a discussion that we had with Christian, I would like to =
raise a concern.
>=20
> Now, on Karaf 2.x/3.x/4.x, the JMX layer is secure using RBAC. The =
MBeanServerBuilder is enabled by default, meaning that it's not possible =
to locally connect to the MBean server.
> I think it's good and secure.
>=20
> However, on the other hand, we have a key enabled by default (in =
etc/keys.properties) and used by default by bin/client.
> So it means that any user that download a Karaf distribution can =
connect to any Karaf runtimes by default.
> On one hand we have a very secure JMX layer (even for local =
connection), but on the other hand, bin/client can connect to any Karaf =
running instance (so not very secure).
>=20
> I would like to propose the following:
> - in etc/keys.properties, we should comment out the default key. We =
can document how to enable it and how to change the keys.
> - in bin/client, we should be able to specify a key that we want to =
use.
>=20
> WDYT ?
>=20
> I already created some Jira about the keys:
> - KARAF-2786: I would change this one by comment out the default key
> - KARAF-2836 to allow to specify multiple keys for an user in =
etc/keys.properties
> - KARAF-2787 to allow to specify the key to bin/client
>=20
> Thanks,
> Regards
> JB
> --=20
> Jean-Baptiste Onofr=C3=A9
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com


--Apple-Mail=_E0875ED6-2C34-43F3-A417-A70FCAEF505D--