Re: [GENERAL] [Re: Password?]
On 2009-07-08, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: Serge Fonville schrieb: *argh* - more detailed to avoid confusion. The auth method 'password' in pg_hba.conf means, that you will be asked for a password for the user you try to create a db with. If no user is given (with createdb -U [username]), this user is postgres ... Wasn't it that it uses the currently logged on user is used if no user is specified? correct - so this will be postgres because other users are not allowed to use these programs ... /var/lib/postgresql/8.4/bin$ ./createdb test -p 5433 createdb: could not connect to database postgres: FATAL: role duke does not exist $ sudo su postgres postg...@duke-linux:~/8.4/bin$ ./createdb test -p 5433 postg...@duke-linux:~/8.4/bin$ auth method in pg_hba.conf is trust in this case. if it's trust any user can do ~postgres/8.4/bin/createdb -U postgres -p 5433 test -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
Jasen Betts schrieb: On 2009-07-08, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: Serge Fonville schrieb: *argh* - more detailed to avoid confusion. The auth method 'password' in pg_hba.conf means, that you will be asked for a password for the user you try to create a db with. If no user is given (with createdb -U [username]), this user is postgres ... Wasn't it that it uses the currently logged on user is used if no user is specified? correct - so this will be postgres because other users are not allowed to use these programs ... /var/lib/postgresql/8.4/bin$ ./createdb test -p 5433 createdb: could not connect to database postgres: FATAL: role duke does not exist $ sudo su postgres postg...@duke-linux:~/8.4/bin$ ./createdb test -p 5433 postg...@duke-linux:~/8.4/bin$ auth method in pg_hba.conf is trust in this case. if it's trust any user can do ~postgres/8.4/bin/createdb -U postgres -p 5433 test nope! what you did is calling createdb as system user postgres (I believe because of the ~ sign at the beginning) *and* giving the option -U postgres. That works for sure and you even don't need -U postgres since you are allready postgres. But leave -U postgres away as a system user not equal to postgres ... see my example above. Cheers Andy -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
On Jul 8, 2009, at 6:19 AM, Andreas Wenk wrote: Jasen Betts schrieb: On 2009-07-08, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: Serge Fonville schrieb: *argh* - more detailed to avoid confusion. The auth method 'password' in pg_hba.conf means, that you will be asked for a password for the user you try to create a db with. If no user is given (with createdb -U [username]), this user is postgres ... Wasn't it that it uses the currently logged on user is used if no user is specified? correct - so this will be postgres because other users are not allowed to use these programs ... That's not true. /var/lib/postgresql/8.4/bin$ ./createdb test -p 5433 createdb: could not connect to database postgres: FATAL: role duke does not exist $ sudo su postgres postg...@duke-linux:~/8.4/bin$ ./createdb test -p 5433 postg...@duke-linux:~/8.4/bin$ auth method in pg_hba.conf is trust in this case. if it's trust any user can do ~postgres/8.4/bin/createdb -U postgres -p 5433 test nope! what you did is calling createdb as system user postgres (I believe because of the ~ sign at the beginning) *and* giving the option -U postgres. That works for sure and you even don't need -U postgres since you are allready postgres. But leave -U postgres away as a system user not equal to postgres ... see my example above. Nor is that. Most of the postgresql client tools, including createdb, can be used by any operating system user to connect to the database as any database user. If they are called with -U foo then they will attempt to connect to the database as database user foo. If they are not called with -U then they will usually attempt to connect to the database as the current operating system user (though that can be overridden with the PGUSER or PGSERVICE environment variables). So if I'm logged in as steve and I do createdb test then I will try and connect to the database as database user steve and create the test database. If I do createdb -U postgres test I will try to connect to the database as database user postgres and create the test database. Whether I'm prompted for a password or not depends on the settings in pg_hba.conf. Typically the postgres operating system user is allowed to connect to the database as the postgres database user without a password. Other OS user / database user combinations may or may not need a password depending on whether pg_hba.conf is set up to ask for one or not - how that is set up as default varies, but it's fairly common to require a password. Cheers, Steve -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
On 08/07/2009 18:14, Steve Atkins wrote: Typically the postgres operating system user is allowed to connect to the database as the postgres database user without a password. Is this really so? I don't think so - I think it depends on pg_hba.conf settings, just like any other user. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland r...@iol.ie Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals -- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
On Jul 8, 2009, at 10:25 AM, Raymond O'Donnell wrote: On 08/07/2009 18:14, Steve Atkins wrote: Typically the postgres operating system user is allowed to connect to the database as the postgres database user without a password. Is this really so? I don't think so - I think it depends on pg_hba.conf settings, just like any other user. It does, yes. But most of the distributions I've seen tend to set it up that way (as otherwise there's not really a good way to do automated maintenance and backups, nor any easy way to bootstrap the database). So it's not hardwired that way, just typically set up that way (on non-Windows OSes anyway - Windows has issues that likely mean it's setup differently there). Cheers, Steve -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
On 08/07/2009 18:30, Steve Atkins wrote: On Jul 8, 2009, at 10:25 AM, Raymond O'Donnell wrote: Is this really so? I don't think so - I think it depends on pg_hba.conf settings, just like any other user. It does, yes. But most of the distributions I've seen tend to set it up that way (as otherwise there's not really a good way to do automated maintenance and backups, nor any easy way to bootstrap the database). So it's not hardwired that way, just typically set up that way (on non-Windows OSes anyway - Windows has issues that likely mean it's setup differently there). Ah, OK - I see what you mean. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland r...@iol.ie Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals -- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
Steve Atkins schrieb: On Jul 8, 2009, at 6:19 AM, Andreas Wenk wrote: Jasen Betts schrieb: On 2009-07-08, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: Serge Fonville schrieb: *argh* - more detailed to avoid confusion. The auth method 'password' in pg_hba.conf means, that you will be asked for a password for the user you try to create a db with. If no user is given (with createdb -U [username]), this user is postgres ... Wasn't it that it uses the currently logged on user is used if no user is specified? correct - so this will be postgres because other users are not allowed to use these programs ... That's not true. you are right!Sorry for that mistake. /var/lib/postgresql/8.4/bin$ ./createdb test -p 5433 createdb: could not connect to database postgres: FATAL: role duke does not exist $ sudo su postgres postg...@duke-linux:~/8.4/bin$ ./createdb test -p 5433 postg...@duke-linux:~/8.4/bin$ auth method in pg_hba.conf is trust in this case. if it's trust any user can do ~postgres/8.4/bin/createdb -U postgres -p 5433 test nope! what you did is calling createdb as system user postgres (I believe because of the ~ sign at the beginning) *and* giving the option -U postgres. That works for sure and you even don't need -U postgres since you are allready postgres. But leave -U postgres away as a system user not equal to postgres ... see my example above. Nor is that. Why not? I think it is but maybe I did not write it understandable enough. See my example. Most of the postgresql client tools, including createdb, can be used by any operating system user to connect to the database as any database user. If they are called with -U foo then they will attempt to connect to the database as database user foo. If they are not called with -U then they will usually attempt to connect to the database as the current operating system user (though that can be overridden with the PGUSER or PGSERVICE environment variables). So if I'm logged in as steve and I do createdb test then I will try and connect to the database as database user steve and create the test database. If I do createdb -U postgres test I will try to connect to the database as database user postgres and create the test database. this is exactly my example. I am the system user duke but there is no role duke in the db. The result is the error message. Using -U postgres is successful. But in the case shown by Swati she is allready the system user postgres. So there's no need to put the option -U postgres. Correct? See my example. Whether I'm prompted for a password or not depends on the settings in pg_hba.conf. Typically the postgres operating system user is allowed to connect to the database as the postgres database user without a password. Other OS user / database user combinations may or may not need a password depending on whether pg_hba.conf is set up to ask for one or not - how that is set up as default varies, but it's fairly common to require a password. exactly. Thanks a lot for explaining that way better. Cheers, Steve Actually I think we both know how it works ;-) Cheers Andy -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Re: Password?]
I think I can understand what you both have discussed. But I am unable to unearth my mistake. Regards Swati --- On Wed, 7/8/09, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: From: Andreas Wenk a.w...@netzmeister-st-pauli.de Subject: Re: [GENERAL] [Re: Password?] To: Steve Atkins st...@blighty.com Cc: pgsql-general List pgsql-general@postgresql.org Date: Wednesday, July 8, 2009, 11:20 PM Steve Atkins schrieb: On Jul 8, 2009, at 6:19 AM, Andreas Wenk wrote: Jasen Betts schrieb: On 2009-07-08, Andreas Wenk a.w...@netzmeister-st-pauli.de wrote: Serge Fonville schrieb: *argh* - more detailed to avoid confusion. The auth method 'password' in pg_hba.conf means, that you will be asked for a password for the user you try to create a db with. If no user is given (with createdb -U [username]), this user is postgres ... Wasn't it that it uses the currently logged on user is used if no user is specified? correct - so this will be postgres because other users are not allowed to use these programs ... That's not true. you are right!Sorry for that mistake. /var/lib/postgresql/8.4/bin$ ./createdb test -p 5433 createdb: could not connect to database postgres: FATAL: role duke does not exist $ sudo su postgres postg...@duke-linux:~/8.4/bin$ ./createdb test -p 5433 postg...@duke-linux:~/8.4/bin$ auth method in pg_hba.conf is trust in this case. if it's trust any user can do ~postgres/8.4/bin/createdb -U postgres -p 5433 test nope! what you did is calling createdb as system user postgres (I believe because of the ~ sign at the beginning) *and* giving the option -U postgres. That works for sure and you even don't need -U postgres since you are allready postgres. But leave -U postgres away as a system user not equal to postgres ... see my example above. Nor is that. Why not? I think it is but maybe I did not write it understandable enough. See my example. Most of the postgresql client tools, including createdb, can be used by any operating system user to connect to the database as any database user. If they are called with -U foo then they will attempt to connect to the database as database user foo. If they are not called with -U then they will usually attempt to connect to the database as the current operating system user (though that can be overridden with the PGUSER or PGSERVICE environment variables). So if I'm logged in as steve and I do createdb test then I will try and connect to the database as database user steve and create the test database. If I do createdb -U postgres test I will try to connect to the database as database user postgres and create the test database. this is exactly my example. I am the system user duke but there is no role duke in the db. The result is the error message. Using -U postgres is successful. But in the case shown by Swati she is allready the system user postgres. So there's no need to put the option -U postgres. Correct? See my example. Whether I'm prompted for a password or not depends on the settings in pg_hba.conf. Typically the postgres operating system user is allowed to connect to the database as the postgres database user without a password. Other OS user / database user combinations may or may not need a password depending on whether pg_hba.conf is set up to ask for one or not - how that is set up as default varies, but it's fairly common to require a password. exactly. Thanks a lot for explaining that way better. Cheers, Steve Actually I think we both know how it works ;-) Cheers Andy -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Re: PASSWORD() function for postgresql?
You could take the password hashing routine out of client/password.c (in the mysql source) and write your own C function... I know just enough C to think that it shouldn't be that hard, but not enough to do it :) -philip On Sun, 15 Jul 2001, Jason DiCioccio wrote: I am looking for a postgresql PASSWORD() function that produces hashes compatible with MySQL's implementation. I am converting from MySQL and I know of no other way to use the passwords I have in the old database other than having a compatible PASSWORD() function. I have searched around for one quite a bit but could not find one. Does anyone know if someone has written something to do this already? If so, where I can get it from? I am off the list so please include me in CC, etc. Thanks in advance, Jason DiCioccio ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [GENERAL] Re: PASSWORD() function for postgresql?
For that matter, you could write a perl function using perl's built-in crypt() function. I'm not sure if it's exactly identical to what mysql does, though I strongly suspect that it is. Philip Hallstrom [EMAIL PROTECTED] on 07/23/2001 02:13:27 PM To: Jason DiCioccio [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Wesley Sheldahl/Lex/Lexmark) Subject: [GENERAL] Re: PASSWORD() function for postgresql? You could take the password hashing routine out of client/password.c (in the mysql source) and write your own C function... I know just enough C to think that it shouldn't be that hard, but not enough to do it :) -philip On Sun, 15 Jul 2001, Jason DiCioccio wrote: I am looking for a postgresql PASSWORD() function that produces hashes compatible with MySQL's implementation. I am converting from MySQL and I know of no other way to use the passwords I have in the old database other than having a compatible PASSWORD() function. I have searched around for one quite a bit but could not find one. Does anyone know if someone has written something to do this already? If so, where I can get it from? I am off the list so please include me in CC, etc. Thanks in advance, Jason DiCioccio ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
