From b8aa153a2d398bdcfb6438e1392c0eb1c861a05f Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 21 Jun 2007 12:20:10 +0000 Subject: [PATCH] Update password example. --- doc/src/sgml/ref/createuser.sgml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 495db8f797..5633065c54 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -378,12 +378,14 @@ PostgreSQL documentation $ createuser -P -s -e joe Enter password for new role: xyzzy Enter it again: xyzzy -CREATE ROLE joe PASSWORD 'xyzzy' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN; +CREATE ROLE joe PASSWORD 'md5b5f5ba1a423792b526f799ae4eb3d59e' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN; In the above example, the new password isn't actually echoed when typed, - but we show what was typed for clarity. However the password - will appear in the echoed command, as illustrated — - so you don't want to use -e when assigning a password, if + but we show what was typed for clarity. As you see, the password is + encrypted before it is sent to the client. If the option + is used, the password will appear in the echoed command + (and possibly also in the server log and elsewhere), + so you don't want to use