Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 9 Jan 2014 13:26:52 +0000 (UTC)
From: "Wei Zhou (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12678761.1384250547689.68456.1389274012361@arcas>
In-Reply-To: <JIRA.12678761.1384250547689@arcas>
References: <JIRA.12678761.1384250547689@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone
 Security Groups - SSH to VM is allowed even when there is no ingress rule
 defined for the security group
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D13866636#comment-13866636 ]=20

Wei Zhou commented on CLOUDSTACK-5144:
--------------------------------------

I am wondering why these rule exist?

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
14M 11G ACCEPT all =E2=80=93 * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLIS=
HED


and also this one

Chain RH-Firewall-1-INPUT (2 references)
pkts bytes target prot opt in out source destination=20
35M 49G ACCEPT all =E2=80=93 lo * 0.0.0.0/0 0.0.0.0/0=20

> [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when=
 there is no ingress rule defined for the security group
> -------------------------------------------------------------------------=
--------------------------------------------------------
>
>                 Key: CLOUDSTACK-5144
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-514=
4
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Network Controller
>    Affects Versions: 4.3.0
>            Reporter: Gaurav Aradhye
>            Assignee: Wei Zhou
>            Priority: Blocker
>              Labels: automation
>             Fix For: 4.3.0
>
>         Attachments: MS-Log.txt, agent.log, agent.log, ipset-L output.txt=
, iptables-rules.txt, management-server.log
>
>
> In Basic Zone Setup:
> 1. Create an account
> 2. Deploy a VM in that account
> 3. Verify that any ingress rule is not defined for the security group bel=
onging to the account
> 4. Try SSH to VM using the nic ipaddress from external client
> SSH is successful to the VM where as it should fail when the ingress rule=
 is not defined.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)