[
https://issues.apache.org/jira/browse/TS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15099225#comment-15099225
]
Alan M. Carroll edited comment on TS-4134 at 1/15/16 1:00 AM:
--------------------------------------------------------------
{code}
{ ElevateAccess access; }
{code}
won't work because that is a RAII pattern and when the instance goes out of
scope the privileges are revoked. The better option is to pass {{0}} for the
privilege bitmask if privileges aren't needed. Does this happen when running as
root or not as root or in both cases?
was (Author: amc):
{{ { ElevateAccess; } }} won't work because that is a RAII pattern and when the
instance goes out of scope the privileges are revoked. The better option is to
pass {{0}} for the privilege bitmask if privileges aren't needed. Does this
happen when running as root or not as root or in both cases?
> Traffic Manager aborts on attempted privilege escalation when non-root.
> -----------------------------------------------------------------------
>
> Key: TS-4134
> URL: https://issues.apache.org/jira/browse/TS-4134
> Project: Traffic Server
> Issue Type: Bug
> Affects Versions: 6.2.0
> Reporter: Peter Chou
> Fix For: 6.1.0
>
>
> Traffic Manager aborts since it cannot elevate access in mgmt/Rollback.cc and
> mgmt/LocalManager.cc. The root of the issue might be that the semantics of
> the ElevateAccess constructor argument was changed from (boolean,level) to
> just a (level) by commit 6a5f6241 or TS-306. It seems the ElevateAccess
> access( <boolean-expression> ) calls in these two files were not changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
