[mcs] Remove doc about CAS security

1 files changed, 0 insertions, 37 deletions

diff --git a/man/mono.1 b/man/mono.1
index a6020801aef..a63282bc559 100644
--- a/man/mono.1
+++ b/man/mono.1
@@ -636,43 +636,6 @@ running a 1.1 program on a 2.0 version:
          mono --runtime=v2.0.50727 program.exe
 .fi
 .TP
-\fB--security\fR, \fB--security=mode\fR
-Activate the security manager, a currently experimental feature in
-Mono and it is OFF by default. The new code verifier can be enabled
-with this option as well.
-.RS
-.ne 8
-.PP
-Using security without parameters is equivalent as calling it with the
-"cas" parameter.  
-.PP
-The following modes are supported:
-.TP 
-.I core-clr
-Enables the core-clr security system, typically used for
-Moonlight/Silverlight applications.  It provides a much simpler
-security system than CAS, see http://www.mono-project.com/docs/web/moonlight/
-for more details and links to the descriptions of this new system. 
-.TP
-.I validil
-Enables the new verifier and performs basic verification for code
-validity.  In this mode, unsafe code and P/Invoke are allowed. This
-mode provides a better safety guarantee but it is still possible
-for managed code to crash Mono. 
-.TP
-.I verifiable
-Enables the new verifier and performs full verification of the code
-being executed.  It only allows verifiable code to be executed.
-Unsafe code is not allowed but P/Invoke is.  This mode should
-not allow managed code to crash mono.  The verification is not as
-strict as ECMA 335 standard in order to stay compatible with the MS
-runtime.
-.PP
-The security system acts on user code: code contained in mscorlib or
-the global assembly cache is always trusted.
-.ne
-.RE
-.TP
 \fB--server\fR
 Configures the virtual machine to be better suited for server
 operations (currently, allows a heavier threadpool initialization).