summaryrefslogtreecommitdiff
path: root/src/backend/libpq/crypt.c
diff options
context:
space:
mode:
authorMarc G. Fournier <scrappy@hub.org>1998-02-25 13:09:49 +0000
committerMarc G. Fournier <scrappy@hub.org>1998-02-25 13:09:49 +0000
commit780068f812a61e73b2474f7f025b28309a2f1840 (patch)
tree7d1db588478714e434ced675e55af8101f94f3fb /src/backend/libpq/crypt.c
parentd067f83b274adffb3415a8a41dd8bdc71bc87620 (diff)
downloadpostgresql-780068f812a61e73b2474f7f025b28309a2f1840.tar.gz
From: Jan Wieck <jwieck@debis.com>
seems that my last post didn't make it through. That's good since the diff itself didn't covered the renaming of pg_user.h to pg_shadow.h and it's new content. Here it's again. The complete regression test passwd with only some float diffs. createuser and destroyuser work. pg_shadow cannot be read by ordinary user.
Diffstat (limited to 'src/backend/libpq/crypt.c')
-rw-r--r--src/backend/libpq/crypt.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/libpq/crypt.c b/src/backend/libpq/crypt.c
index dbda5e3e2b..e6d3a7cf43 100644
--- a/src/backend/libpq/crypt.c
+++ b/src/backend/libpq/crypt.c
@@ -1,7 +1,7 @@
/*-------------------------------------------------------------------------
*
* crypt.c--
- * Look into pg_user and check the encrypted password with the one
+ * Look into pg_shadow and check the encrypted password with the one
* passed in from the frontend.
*
* Modification History
@@ -119,7 +119,7 @@ void crypt_loadpwdfile() {
/* We want to delete the flag file before reading the contents of the pg_pwd
* file. If result == 0 then the unlink of the reload file was successful.
- * This means that a backend performed a COPY of the pg_user file to
+ * This means that a backend performed a COPY of the pg_shadow file to
* pg_pwd. Therefore we must now do a reload.
*/
if (!pwd_cache || !result) {