Add type to frontmatter
This commit is contained in:
parent
5e05ec3b8b
commit
fc925583da
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
comments: false
|
||||
type: index
|
||||
---
|
||||
|
||||
# Security
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: reference
|
||||
---
|
||||
|
||||
# How we manage the TLS protocol CRIME vulnerability
|
||||
|
||||
> CRIME ("Compression Ratio Info-leak Made Easy") is a security exploit against
|
||||
|
|
@ -7,7 +11,7 @@ authentication cookies, it allows an attacker to perform session hijacking on an
|
|||
authenticated web session, allowing the launching of further attacks.
|
||||
([CRIME](https://en.wikipedia.org/w/index.php?title=CRIME&oldid=692423806))
|
||||
|
||||
### Description
|
||||
## Description
|
||||
|
||||
The TLS Protocol CRIME Vulnerability affects compression over HTTPS, therefore
|
||||
it warns against using SSL Compression (for example gzip) or SPDY which
|
||||
|
|
@ -24,7 +28,7 @@ Although SPDY is enabled in Omnibus installations, CRIME relies on compression
|
|||
(the 'C') and the default compression level in NGINX's SPDY module is 0
|
||||
(no compression).
|
||||
|
||||
### Nessus
|
||||
## Nessus
|
||||
|
||||
The Nessus scanner, [reports a possible CRIME vulnerability][nessus] in GitLab
|
||||
similar to the following format:
|
||||
|
|
@ -50,7 +54,7 @@ attack nor does it check if compression is enabled. With just this approach, it
|
|||
cannot tell that SPDY's compression is disabled and not subject to the CRIME
|
||||
vulnerability.
|
||||
|
||||
### References
|
||||
## References
|
||||
|
||||
- Nginx ["Module ngx_http_spdy_module"][ngx-spdy]
|
||||
- Tenable Network Security, Inc. ["Transport Layer Security (TLS) Protocol CRIME Vulnerability"][nessus]
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: concepts
|
||||
---
|
||||
|
||||
# Information exclusivity
|
||||
|
||||
Git is a distributed version control system (DVCS).
|
||||
|
|
@ -6,4 +10,4 @@ In GitLab every project member that is not a guest (so reporters, developers and
|
|||
After obtaining this local copy the user can upload the full repository anywhere, including another project under their control or another server.
|
||||
The consequence is that you can't build access controls that prevent the intentional sharing of source code by users that have access to the source code.
|
||||
This is an inherent feature of a DVCS and all git management systems have this limitation.
|
||||
Obviously you can take steps to prevent unintentional sharing and information destruction, this is why only some people are allowed to invite others and nobody can force push a protected branch.
|
||||
Obviously you can take steps to prevent unintentional sharing and information destruction, this is why only some people are allowed to invite others and nobody can force push a protected branch.
|
||||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: reference, howto
|
||||
---
|
||||
|
||||
# Custom password length limits
|
||||
|
||||
If you want to enforce longer user passwords you can create an extra Devise initializer with the steps below.
|
||||
|
|
|
|||
Loading…
Reference in New Issue