[
https://issues.apache.org/jira/browse/TS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15099270#comment-15099270
]
ASF GitHub Bot commented on TS-4134:
------------------------------------
GitHub user SolidWallOfCode opened a pull request:
https://github.com/apache/trafficserver/pull/425
TS-4134: Fix privilege elevation issues.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SolidWallOfCode/trafficserver ts-4134
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/425.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #425
----
commit 398c468b0c49b4d1c00cdd8991b22d49c5530990
Author: Alan M. Carroll <[email protected]>
Date: 2016-01-15T01:28:44Z
TS-4134: Fix privilege elevation issues.
----
> 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)
