Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
a75ce8b7
Commit
a75ce8b7
authored
Mar 16, 2015
by
Poul-Henning Kamp
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove doc references to parameters which has been removed.
parent
fde2d231
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
1 addition
and
8 deletions
+1
-8
varnishd.rst
doc/sphinx/reference/varnishd.rst
+1
-2
run_security.rst
doc/sphinx/users-guide/run_security.rst
+0
-6
No files found.
doc/sphinx/reference/varnishd.rst
View file @
a75ce8b7
...
...
@@ -124,8 +124,7 @@ OPTIONS
administrator a way to limit what the Varnish CLI can do. Consider
making parameters such as *user*, *group*, *cc_command*,
*vcc_allow_inline_c* read only as these can potentially be used to
escalate privileges from the CLI. Protecting *listen_address* may
also be a good idea.
escalate privileges from the CLI.
-s <[name=]type[,options]>
...
...
doc/sphinx/users-guide/run_security.rst
View file @
a75ce8b7
...
...
@@ -156,12 +156,6 @@ interface.
Pretty much any parameter can be used to totally mess up your
HTTP service, but a few can do more damage than others:
.. XXX :ref:`ref_param_user` and :ref:`ref_param_group`
.. XXX Access to local system via VCL
:ref:`ref_param_listen_address`
Trojan other TCP sockets, like `ssh`
:ref:`ref_param_cc_command`
Execute arbitrary programs
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment