From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Fri, 20 Nov 2009 14:54:40 +0000 Subject: The R13B03 release. --- lib/orber/doc/src/orber_acl.xml | 106 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 lib/orber/doc/src/orber_acl.xml (limited to 'lib/orber/doc/src/orber_acl.xml') diff --git a/lib/orber/doc/src/orber_acl.xml b/lib/orber/doc/src/orber_acl.xml new file mode 100644 index 0000000000..441001894a --- /dev/null +++ b/lib/orber/doc/src/orber_acl.xml @@ -0,0 +1,106 @@ + + + + +
+ + 2005 + 2007 + Ericsson AB, All Rights Reserved + + + The contents of this file are subject to the Erlang Public License, + Version 1.1, (the "License"); you may not use this file except in + compliance with the License. You should have received a copy of the + Erlang Public License along with this software. If not, it can be + retrieved online at http://www.erlang.org/. + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See + the License for the specific language governing rights and limitations + under the License. + + The Initial Developer of the Original Code is Ericsson AB. + + + orber_acl + + + + + + 2005-05-19 + A +
+ orber_acl + Orber ACL operations + +

This module contains functions intended for analyzing Access + Control List (ACL) filters. The filters uses a extended format of + Classless Inter Domain Routing (CIDR). + For example, "123.123.123.10" limits + the connection to that particular host, while "123.123.123.10/17" allows + connections to or from any host equal to the 17 most significant bits. Orber + also allow the user to specify a certain port or port range, for example, + "123.123.123.10/17#4001" and "123.123.123.10/17#4001/5001" + respectively. IPv4 or none compressed IPv6 strings are accepted.

+ + + + match(IP, Direction) -> boolean() + match(IP, Direction, GetInfo) -> Reply + Verify if the IP address versus the current configuration + + IP = tuple() | [integer()] + Direction = tcp_in | ssl_in | tcp_out | ssl_out + GetInfo = boolean() + Reply = boolean() | {boolean(), [Interface], PortInfo} + Interface = string() + PortInfo = integer() | {integer(), integer()} + + +

If GetInfo is not supplied or set to false, this operation returns + a boolean which tells if the IPv4 or IPv6 address would pass the ACL + filter, defined by the iiop_acl configuration parameter, or not. + When GetInfo is set to true, a tuple which, besides the boolean + that tells if access was granted, also include the defined + interfaces and port(s). This operation requires that Orber is running and + can be used on a live node to determine if Orber has been properly configured.

+ + + + verify(IP, Filter, Family) -> Reply + Verify if the IP address versus the Filter + + IP = string() + Filter = string() + Family = inet | inet6 + Reply = true | {false, From, To} | {error, string()} + From = string() + To = string() + + +

This operation returns true if the IPv4 or IPv6 address would pass the + supplied ACL. If that is not the case, a tuple containing the accepted range + is returned. This operation should only be used for test purposes.

+ + + + range(Filter, Family) -> Reply + Get range of Filter + + Filter = string() + Family = inet | inet6 + Reply = {ok, From, To} | {error, string()} + From = string() + To = string() + + +

Returns the range of accepted IP addresses based on the supplied filter. + This operation should only be used for test purposes.

+ + + + + + -- cgit v1.2.3