gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use assert in legacy unit tests (#867)	Ethan Koenig	2017-02-08	1	-35/+22
\|
*	Update import paths from github.com/go-gitea to code.gitea.io (#135)	Sandro Santilli	2016-11-10	1	-1/+1
\| \| \| \| \| \| \|	- Update import paths from github.com/go-gitea to code.gitea.io - Fix import path for travis See https://docs.travis-ci.com/user/languages/go#Go-Import-Path
*	Change import reference to match gitea instead of gogs (#37)	Rémy Boulanouar	2016-11-03	1	-1/+1
\|
*	Code clean up for new config options	Unknwon	2016-08-14	1	-1/+1
\|
*	#3442 add test suites	Unknwon	2016-08-12	1	-1/+12
\|
*	Post work for #2637	Unknwon	2016-02-27	1	-29/+35
\| \| \| \|	Improve test cases, config settings, also show SSH config settings on admin config panel.
*	variable should not use ALL_CAPS	Gibheer	2016-02-23	1	-3/+3
\|
*	remove ed25519 test for now	Gibheer	2016-02-17	1	-7/+6
\| \| \| \|	TravisCI is too old for ed25519, so it can't be tested correctly.
*	fix ssh public key tests	Gibheer	2016-02-17	1	-8/+12
\| \| \| \| \| \| \|	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.
*	allow native and ssh-keygen public key check	Gibheer	2016-02-16	1	-0/+36
	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 7ef9a055886574655d9f2be70c957bc16bf30500. 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.