Zone security MySQL with Apache
|
|
|
|
| Articles Reviews Mysql | |||||||
| Written by Radu Mazare | |||||||
| Monday, 09 October 2006 | |||||||
Page 5 of 5 {mos_sb_discuss:27}AuthMySQLPwEncryption none | crypt | scrambled | md5 | aes | sha1
This
is the method of encryption used when encoding the passwords in the database,
as follows: none: No encryption/plain text
crypt: UNIX crypt() encryption
scrambled: MySQL PASSWORD() encryption
md5: MD5 hashing
aes: Advanced Encryption Standard (AES) encryption
sha1: Secure Hash Algorith (SHA1)
If
no value is specified, the default value of crypt is used.
When
using AES password encryption, make sure the password field in your MySQL user
tables is a BLOB type, not a CHAR, VARCHAR, or BINARY type. Unless the column
type is one of the BLOB variations, MySQL will strip any extra encoded
characters from the encrypted passwords -- and you'll never be able to match
the given password to the database values. AuthMySQLSaltField
This
allows you to specify one of three values to use as the "salt value"
when encrypting passwords. AuthMySQLGroupTable
This is used to set the name of the table containing group information, when
Apache is told to check groups instead of individual users (require group
versus require valid-user). AuthMySQLGroupCondition
Similar to AuthMySQLUserCondition, this directive allows you to specify
conditional statements to include in the WHERE clause when matching user
groups. AuthMySQLGroupField
This is the name of the field in the database that contains the group names.
This field is used when matching groups using Apache's require group
directive. AuthMySQLAuthoritative This tells Apache whether or not to fallback to other modules if MySQL authentication fails. Powered by jReviews |
|||||||
| Last Updated ( Sunday, 08 July 2007 ) | |||||||
| < Prev | Next > |
|---|







