gitea

Commit Graph

Author	SHA1	Message	Date
zeripath	44371b96f5	Ensure valid git author names passed in signatures (#5774 ) * Ensure valid git author names passed in signatures Fix #5772 - Git author names are not allowed to include `\n` `<` or `>` and must not be empty. Ensure that the name passed in a signature is valid. * Account for pathologically named external users LDAP and the like usernames are not checked in the same way that users who signup are. Therefore just ensure that user names are also git safe and if totally pathological - Set them to "user-$UID" * Add Tests and adjust test users Make our testcases a little more pathological so that we be sure that integration tests have a chance to spot these cases. Signed-off-by: Andrew Thornton <art27@cantab.net>	6 years ago
Lunny Xiao	da5a0b8382	add tests for api user orgs (#5494 ) * add tests for api user orgs * add permission for admin to list user's orgs even he is a private user of org	6 years ago

Author

SHA1

Message

Date

zeripath

44371b96f5

Ensure valid git author names passed in signatures (#5774 )

* Ensure valid git author names passed in signatures

Fix #5772 - Git author names are not allowed to include `\n` `<` or `>` and
must not be empty. Ensure that the name passed in a signature is valid.

* Account for pathologically named external users

LDAP and the like usernames are not checked in the same way that users who signup are.
Therefore just ensure that user names are also git safe and if totally pathological -
Set them to "user-$UID"

* Add Tests and adjust test users

Make our testcases a little more pathological so that we be sure that integration
tests have a chance to spot these cases.

Signed-off-by: Andrew Thornton <art27@cantab.net>

6 years ago

Lunny Xiao

da5a0b8382

add tests for api user orgs (#5494 )

* add tests for api user orgs

* add permission for admin to list user's orgs even he is a private user of org

6 years ago

2 Commits (2ec9bf9048b86092c3c31a150df75eae753df7c1)