[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to gnats/gnats/gnatsd.user_access
From: |
Yngve Svendsen |
Subject: |
Changes to gnats/gnats/gnatsd.user_access |
Date: |
Mon, 23 Jun 2003 05:04:11 -0400 |
Index: gnats/gnats/gnatsd.user_access
diff -c gnats/gnats/gnatsd.user_access:1.2 gnats/gnats/gnatsd.user_access:1.3
*** gnats/gnats/gnatsd.user_access:1.2 Thu May 1 07:46:43 2003
--- gnats/gnats/gnatsd.user_access Mon Jun 23 05:04:11 2003
***************
*** 21,28 ****
# prefix are assumed to be encrypted with standard
# crypt(). For example, on FreeBSD systems, no prefix implies DES
# encryption, a prefix of $1$ implies MD5 encryption, while
! # $2$ prefix implies Blowfish encryption. GNATS will support all then
! # encryption methods supported by your system's crypt() routing. An
# empty field value means that the user should not supply any
# password.
# * access-level: (default = listdb)
--- 21,28 ----
# prefix are assumed to be encrypted with standard
# crypt(). For example, on FreeBSD systems, no prefix implies DES
# encryption, a prefix of $1$ implies MD5 encryption, while
! # $2$ prefix implies Blowfish encryption. GNATS will support all the
! # encryption methods supported by your system's crypt() routine. An
# empty field value means that the user should not supply any
# password.
# * access-level: (default = listdb)
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Changes to gnats/gnats/gnatsd.user_access,
Yngve Svendsen <=