[OpenSER-Devel] [ openser-Bugs-1925738 ] permissions: allow_trusted evaluates to false unexpectedly

[SourceForge.net]

Bugs item #1925738, was opened at 2008-03-26 02:13
Message generated for change (Comment added) made by henningw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1925738&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.3.x
>Status: Closed
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Cameron (kjcsb)
>Assigned to: Henning Westerholt (henningw)
Summary: permissions: allow_trusted evaluates to false unexpectedly

Initial Comment:
I have the following permissions module setup:
modparam("auth_db|permissions|uri_db|usrloc|domain|lcr", "db_url", "mysql://user:password@localhost/ser")
modparam("permissions", "db_mode", 0) 
modparam("permissions", "trusted_table", "trusted")

        if (!is_uri_host_local()) {
                if (is_from_local() || allow_trusted() ) {
                        route(5);
                        route(1);
                } else {
                        sl_send_reply("403", "Forbidden");
                        xlog("403 in call type processing. rs $rs si $si rm $rm ru $ru tu $tu fu $fu fd $fd rr $rr");
                };
                return;
        };

When an invite is received the calls is rejected with a 403 and 403 in call type processing is written to the log file. So allow_trusted must be evaluating to false

I can see from the log that the following query is executed:
13 Query       select proto,from_pattern,tag from trusted where src_ip='202.180.001.001'

When I execute this query directly on the database it returns:
+-------+--------------+------+
| proto | from_pattern | tag  |
+-------+--------------+------+
| any   | NULL         | NULL |
+-------+--------------+------+
1 row in set (0.00 sec)

Could anyone advise what Ive done wrong?

OpenSER1.3.1


----------------------------------------------------------------------

>Comment By: Henning Westerholt (henningw)
Date: 2008-07-11 09:12

Message:
Logged In: YES 
user_id=337916
Originator: NO

I can also confirm that it works with current trunk and 1.3 branch. No
response from the reporter so far, closes this bug. Please reopen if this
is still valid and you can add more informations.


----------------------------------------------------------------------

Comment By: Henning Westerholt (henningw)
Date: 2008-07-04 13:22

Message:
Logged In: YES 
user_id=337916
Originator: NO

Hello Cameron,

any update on this problem? Is this report still valid?

Henning

----------------------------------------------------------------------

Comment By: Juha Heinanen (juhe)
Date: 2008-07-01 12:26

Message:
Logged In: YES 
user_id=1332122
Originator: NO

i tested this with trunk version and allow_trusted() worked fine when
source ip address matched src_ip entry in trusted table and when proto was
any and from and tag were both NULL. so i'm puzzled what the problem might
be.

----------------------------------------------------------------------

Comment By: Daniel-Constantin Mierla (miconda)
Date: 2008-05-05 22:53

Message:
Logged In: YES 
user_id=1246013
Originator: NO

OK, then needs some investigation. It is another bug filed for
permissions: #1888101. Daniel.

----------------------------------------------------------------------

Comment By: Cameron (kjcsb)
Date: 2008-05-05 20:26

Message:
Logged In: YES 
user_id=1236862
Originator: YES

I substituted the original IP address which is why the format looks
strange. The query is definately issued by OpenSer. My apologies for the
confusion.

----------------------------------------------------------------------

Comment By: Daniel-Constantin Mierla (miconda)
Date: 2008-05-03 20:38

Message:
Logged In: YES 
user_id=1246013
Originator: NO

Are you sure that is the query sent by openser? I do not recognize the
form of the IP address used in query. openser should set the ip address as
'202.180.1.1', should not add '00' in front of the last two '1'-es in the
ip address.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1925738&group_id=139143