-
+
Client Authentication
The password is sent over the wire in clear text. For better
- protection, use the crypt method.
+ protection, use the md5 or
+ crypt methods.
- crypt
+ md5
Like the password method, but the password
is sent over the wire encrypted using a simple
challenge-response protocol. This protects against incidental
wire-sniffing. The name of a file may follow the
- crypt keyword. It contains a list of users
+ md5 keyword. It contains a list of users
for this record.
+
+ crypt
+
+ Like the md5 method but uses older crypt
+ authentication for pre-7.2 clients.
+
+
+
+
krb4
# Allow a user from host 192.168.12.10 to connect to database "template1"
# if the user's password in pg_shadow is correctly supplied:
-host template1 192.168.12.10 255.255.255.255 crypt
+host template1 192.168.12.10 255.255.255.255 md5
# In the absence of preceding "host" lines, these two lines will reject
# all connection attempts from 192.168.54.1 (since that entry will be
- To restrict the set of users that are allowed to connect to
- certain databases, list the set of users in a separate file (one
- user name per line) in the same directory that
- pg_hba.conf is in, and mention the (base) name of the
- file after the password or crypt keyword,
+ To restrict the set of users that are allowed to connect to certain
+ databases, list the set of users in a separate file (one user name
+ per line) in the same directory that pg_hba.conf is in,
+ and mention the (base) name of the file after the
+ password, md5, or crypt keyword,
respectively, in pg_hba.conf. If you do not use this
feature, then any user that is known to the database system can
connect to any database (so long as he passes password
- Alternative passwords cannot be used when using the
- crypt method. The file will still be evaluated as
+ Alternative passwords cannot be used when using the md5
+ or crypt methods. The file will still be evaluated as
usual but the password field will simply be ignored and the
pg_shadow password will be used.
pg_hba.conf file may need to be configured.
Refer to the Administrator's Guide for
details. The
JDBC Driver supports trust,
- ident, password, and crypt authentication methods.
+ ident, password, and md5, crypt authentication methods.
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/libpq/auth.c,v 1.58 2001/08/16 04:27:18 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/libpq/auth.c,v 1.59 2001/08/16 16:24:15 momjian Exp $
*
*-------------------------------------------------------------------------
*/
status = recv_and_check_password_packet(port);
break;
- case uaMD5:
- sendAuthRequest(port, AUTH_REQ_MD5);
- if ((status = recv_and_check_password_packet(port)) == STATUS_OK)
- break;
- port->auth_method = uaCrypt;
- /* Try crypt() for old client */
- /* FALL THROUGH */
-
case uaCrypt:
sendAuthRequest(port, AUTH_REQ_CRYPT);
status = recv_and_check_password_packet(port);
break;
+ case uaMD5:
+ sendAuthRequest(port, AUTH_REQ_MD5);
+ status = recv_and_check_password_packet(port);
+ break;
+
case uaTrust:
status = STATUS_OK;
break;
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/libpq/hba.c,v 1.63 2001/08/16 04:27:18 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/libpq/hba.c,v 1.64 2001/08/16 16:24:15 momjian Exp $
*
*-------------------------------------------------------------------------
*/
*userauth_p = uaKrb5;
else if (strcmp(token, "reject") == 0)
*userauth_p = uaReject;
- else if (strcmp(token, "crypt") == 0)
- /* Try MD5 first; on failure, switch to crypt() */
+ else if (strcmp(token, "md5") == 0)
*userauth_p = uaMD5;
+ else if (strcmp(token, "crypt") == 0)
+ *userauth_p = uaCrypt;
else
*error_p = true;
line = lnext(line);
# utility. Remember, these passwords override pg_shadow
# passwords.
#
-# crypt: Same as "password", but authentication is done by
+# md5: Same as "password", but authentication is done by
# encrypting the password sent over the network. This is
# always preferable to "password" except for old clients
-# that don't support "crypt". Also, crypt can use
-# usernames stored in secondary password files but not
-# secondary passwords.
+# that don't support it. Also, md5 can use usernames stored
+# in secondary password files but not secondary passwords.
#
+# crypt: Same as "md5", but uses crypt for pre-7.2 clients. You can
+# not store encrypted passwords if you use this option.
+#
# ident: For TCP/IP connections, authentication is done by contacting
# the ident server on the client host. (CAUTION: this is only
# as secure as the client machine!) On machines that support
# if the user's password in pg_shadow is correctly supplied:
#
# TYPE DATABASE IP_ADDRESS MASK AUTH_TYPE AUTH_ARGUMENT
-# host template1 192.168.12.10 255.255.255.255 crypt
+# host template1 192.168.12.10 255.255.255.255 md5
#
# In the absence of preceding "host" lines, these two lines will reject
# all connection from 192.168.54.1 (since that entry will be matched
* Interface to hba.c
*
*
- * $Id: hba.h,v 1.23 2001/08/15 18:42:15 momjian Exp $
+ * $Id: hba.h,v 1.24 2001/08/16 16:24:16 momjian Exp $
*
*-------------------------------------------------------------------------
*/
uaIdent,
uaPassword,
uaCrypt,
- uaMD5 /* This starts as uaCrypt from pg_hba.conf, but gets
- overridden if the client supports MD5 */
+ uaMD5
} UserAuth;
typedef struct Port hbaPort;
projects / postgresql.git / commitdiff