apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43499] - apr_global_mutex_create returns error "Access denied"
Date Thu, 27 Sep 2007 13:52:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43499>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43499





------- Additional Comments From forums02@38244.copi.ru  2007-09-27 06:52 -------
>Typically not; no process other than the other-child, different user context
should have access to that lock.

My problem is that the service and the usual application have no parent/child
relations.

>Widening the access to the created mutex as you suggest typically creates
too many exploit patterns.

The current implementation creates user-wide mutexes, which could be used by all
processes of that user. My implemetation creates PC-wide mutexes, which could be
used by any processes.
Is it possible to add additional flag, or function to support both variants?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org


Mime
View raw message