gitlab-org--gitlab-foss/doc/security
Nick Thomas 6847060266 Rework the permissions model for SSH key restrictions
`allowed_key_types` is removed and the `minimum_<type>_bits` fields are
renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
that the key type is disabled.

This also feeds through to the UI - checkboxes per key type are out, inline
selection of "forbidden" and "allowed" (i.e., no restrictions) are in.

As with the previous model, unknown key types are disallowed, even if the
underlying ssh daemon happens to support them. The defaults have also been
changed from the lowest known bit size to "no restriction". So if someone
does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
least until the administrator restricts them.
2017-08-30 20:50:44 +01:00
..
img Rework the permissions model for SSH key restrictions 2017-08-30 20:50:44 +01:00
README.md Add settings for minimum key strength and allowed key type 2017-08-30 20:50:44 +01:00
crime_vulnerability.md
information_exclusivity.md
password_length_limits.md
rack_attack.md
reset_root_password.md
ssh_keys_restrictions.md
two_factor_authentication.md
user_email_confirmation.md
user_file_uploads.md
webhooks.md