IP Whitelisting commented on by Jonathan Robie (Feb 04, 2009).

Comment:

I prefer to call this an "access list for a server". It's not a firewall - you clearly say that in your description. And I think we're moving into calling these things servers rather than brokers, for consistency with AMQP. An access list contains access elements. Each access element specifies the permissions for a network or a hostname:

<accesslist server="server1.qpid.apache.org">
<include file="/path/to/file" />
<access permission="allow" network="192.168.1.0/24" />
<access permisson="block" network="10.0.0.0/8"/>
<access permission="allow" hostname="*.qpid.apache.org"/>
</accesslist>

As for the virtualhost idea, I think I would do that by nesting accesslist:

<accesslist server="server1.qpid.apache.org">
<accesslist virtualhost="prod">
<access permission="deny" network="192.168.1.0/24" />
</accesslist>
</accesslist>

--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:commits-subscr...@qpid.apache.org

Reply via email to