[ https://issues.apache.org/jira/browse/TS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103373#comment-15103373 ]
ASF subversion and git services commented on TS-4134: ----------------------------------------------------- Commit 2c1bdddc5e0946ef2fca0d821603e03f3d19cef2 in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=2c1bddd ] TS-4134: Fix privilege elevation issues. This closes #425. > 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 > Assignee: Alan M. Carroll > 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)