Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 14 Jun 2016 15:28:01 +0000 (UTC)
From: =?utf-8?Q?J=C3=A9r=C3=B4me_Mainaud_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12968082.1463003628000.2749.1465918081592@Atlassian.JIRA>
In-Reply-To: <JIRA.12968082.1463003628000@Atlassian.JIRA>
References: <JIRA.12968082.1463003628000@Atlassian.JIRA> <JIRA.12968082.1463003628111@arcas>
Subject: [jira] [Updated] (CASSANDRA-11755) nodetool info should run with
 "readonly" jmx access
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 14 Jun 2016 15:28:03 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-11755?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=A9r=C3=B4me Mainaud updated CASSANDRA-11755:
---------------------------------------
    Attachment: 11755-2.1.patch

Added a patch based on cassandra-2.1.
It needs to be challenged.

> nodetool info should run with "readonly" jmx access
> ---------------------------------------------------
>
>                 Key: CASSANDRA-11755
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1175=
5
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: J=C3=A9r=C3=B4me Mainaud
>            Priority: Minor
>              Labels: security
>         Attachments: 11755-2.1.patch, nodetool-info-exception-when-readon=
ly.txt
>
>
> nodetool info crash when granted with readonly jmx access
> In the example given in attachment, the jmxremote.access file gives reado=
nly access to the cassandra jmx role.
> When the role is granted to readwrite access, everything works.
> The main reason is that node datacenter and rack info are fetched by an o=
peration invocation instead of by an attribute read. The former one is not =
allowed to the role with readonly access.
> This is a security concern because nodetool info could be called by a mon=
itoring agent (Nagios for instance) and enterprise policy often don't allow=
 these agents to connect to JMX with higher privileges than "readonly".


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)