Update SECURITY.md: mention the cipher config
This commit is contained in:
parent
5a1540d3a2
commit
a924bcf6e7
@ -26,4 +26,10 @@ This Gitea instance is configured following best practices, in order to thwart l
|
||||
|
||||
- Official commits (eg, in the laylo/docs repository) are GPG signed, and MFA is enforced for accounts with write access).
|
||||
- Backups are made every 24 hours, using a 'pull mechanism'. This server does **NOT** have access to the backup repository.
|
||||
- SSH is hardened (PKI authentication, MFA via hardware tokens, highest level ciphersuites).
|
||||
- SSH is hardened (PKI authentication, MFA via hardware tokens).
|
||||
- SSH ciphers are hardened, these are in use:
|
||||
|
||||
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr
|
||||
KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group18-sha512,diffie-hellman-group16-sha512
|
||||
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com
|
||||
HostKeyAlgorithms ssh-ed25519,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-256,rsa-sha2-512,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com
|
||||
|
Loading…
Reference in New Issue
Block a user