From 486ee115abb831b2ec78be6777fb1bca9e931df0 Mon Sep 17 00:00:00 2001 From: James Moger Date: Tue, 25 Oct 2011 17:23:47 -0400 Subject: Documentation. Changed status RPC protection. Status tab for Manager. --- docs/01_setup.mkd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/01_setup.mkd') diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd index b2c5b2f8..0939d5a2 100644 --- a/docs/01_setup.mkd +++ b/docs/01_setup.mkd @@ -159,7 +159,7 @@ Usernames must be unique and are case-insensitive. Whitespace is illegal. #### Passwords -User passwords are CASE-SENSITIVE and may be *plain* or *md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*). +User passwords are CASE-SENSITIVE and may be *plain*, *md5*, or *combined-md5* formatted (see `gitblit.properties` -> *realm.passwordStorage*). #### User Roles There are two actual *roles* in Gitblit: *#admin*, which grants administrative powers to that user, and *#notfederated*, which prevents an account from being pulled by another Gitblit instance. Administrators automatically have access to all repositories. All other *roles* are repository names. If a repository is access-restricted, the user must have the repository's name within his/her roles to bypass the access restriction. This is how users are granted access to a restricted repository. -- cgit v1.2.3