8 Commits (4e4c0c2cd3da66d83779c540ec7b879e64c8db3d)

Author	SHA1	Message	Date
Rémy Boulanouar	2d68bd1ef9	Change import reference to match gitea instead of gogs (#37)	8 years ago
Unknwon	15845cb287	Code clean up for new config options	8 years ago
Unknwon	5be881756b	#3442 add test suites	8 years ago
Unknwon	8055a0bdac	Post work for #2637 ... Improve test cases, config settings, also show SSH config settings on admin config panel.	9 years ago
Gibheer	2f27ee2232	variable should not use ALL_CAPS	9 years ago
Gibheer	dab74f21b7	remove ed25519 test for now ... TravisCI is too old for ed25519, so it can't be tested correctly.	9 years ago
Gibheer	9eef2e706c	fix ssh public key tests ... The old API was using []byte, but was changed to string without running the tests again. It also sets the variables from the configuration to make them work. Maybe there is a better way to do this.	9 years ago
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.	9 years ago