gitea

Author	SHA1	Message	Date
Gibheer	12403bdfb0	allow native and ssh-keygen public key check This commit adds the possibibility to use either the native golang libraries or ssh-keygen to check public keys. The check is adjusted depending on the settings, so that only supported keys are let through. This commit also brings back the blacklist feature, which was removed in `7ef9a05588`. This allows to blacklist algorythms or keys based on the key length. This works with the native and the ssh-keygen way. Because of #2179 it also includes a way to adjust the path to ssh-keygen and the working directory for ssh-keygen. With this, sysadmins should be able to adjust the settings in a way, that SELinux is okay with it. In the worst case, they can switch to the native implementation and only loose support for ed25519 keys at the moment. There are some other places which need adjustment to utilize the parameters and the native implementation, but this sets the ground work.	2016-02-16 23:01:56 +01:00
John Maguire	b3e0efc0c3	Trim whitespace when adding SSH keys (fixes #2447 )	2016-01-31 22:02:36 -05:00
John Maguire	caa4ca46c0	Add debug log when SSH key for deletion isn't found	2016-01-31 22:02:23 -05:00
Unknwon	7ef9a05588	#2179 use Go sub-repo ssh to verify public key content	2016-01-15 18:39:51 +08:00
Unknwon	53eb37d529	fix #1436	2015-12-19 21:43:32 -05:00
Unknwon	bc17f2f759	#2147 fix rewrites authorized_keys when builtin SSH server is enabled	2015-12-11 05:02:33 -05:00