whitelist/regex for remote resource URL requests
-
Greg Schueler
considering these properties to check:
in
project.properties: "project.resources.allowedURL.0-X"in
framework.properties: "framework.resources.allowedURL.0-X" -
Deleted User
I forgot about project.properties. That's probably the best place to put the project level restrictions.
-
Greg Schueler
so forget about framework props?
-
Deleted User
Yeah, start in project.properties. Another ticket should be created for global override, which I kinda see framework.properties providing.
-
Greg Schueler
don't really need a separate ticket...if you want framework.props global
override it's easier as part of this ticket -
Deleted User
Framework.properties can be the override. Add a log message when project.properties rules are completely overridden by a more restrictive framework.properties rule.
-
Greg Schueler
if
project.resources.url== input url, then it is explicitly allowed.otherwise this logic is used:
F=framework.props
P=project.props
unset= no regexes set
pass=1 or more regexes match
fail=0 regexes matchP\F| unset | pass | fail unset| no | yes | no pass | yes | yes | no fail | no | no | noyes= allow URL
no= disallow URL -
Deleted User
- State changed from new to resolved
(from [07df1f4a3b2fae5c64878dfb9889077de4363bd3]) Support allowedURL regex properties for resource provider URLs [#260 whitelist/regex for remote resource URL requests state:resolved] https://github.com/dtolabs/rundeck/commit/07df1f4a3b2fae5c64878dfb9...
-
Deleted User
(from [b1c05e70e4d33285c7f4244606004daa20451bc1]) Add whitelist/regex for project/framework.properties provider URLs [#260 whitelist/regex for remote resource URL requests state:resolved] https://github.com/dtolabs/rundeck/commit/b1c05e70e4d33285c7f424460...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.