Jayadevan M maymala.jayade...@gmail.com writes:
I am able to login as postgres with password from the same machine. So it
is not an expiry issue (as you too concluded). Output from strace is about
500 lines. I am pasting what I feel may be relevant. I hope this will be
useful.
Well, this is
On 01/06/2014 02:42 PM, Tom Lane wrote:
Jayadevan M maymala.jayade...@gmail.com writes:
I am able to login as postgres with password from the same machine. So it
is not an expiry issue (as you too concluded). Output from strace is about
500 lines. I am pasting what I feel may be relevant. I
Sameer Kumar wrote
This only tells that there is one instance running!
There could be multiple PostgreSQL installations. And I guess that is what
Tom meant here.
I doubt that was what Tom meant. Anyway, we can see from the error that the
request did reach the server.
Sameer Kumar wrote
On Sun, Jan 5, 2014 at 6:45 PM, Jayadevan maymala.jayade...@gmail.comwrote:
Sameer Kumar wrote
This only tells that there is one instance running!
There could be multiple PostgreSQL installations. And I guess that is
what
Tom meant here.
I doubt that was what Tom meant. Anyway, we can
On 01/04/2014 08:46 PM, Jayadevan M wrote:
Log entries for 3 situations - 2 successful and one failed attempt -
From non-chroot, shell user postgres
2014-01-05 10:11:58 IST [17008]: [2-1] user=postgres,db=postgres LOG:
connection authorized: user=postgres database=postgres
2014-01-05
With md5
psql
psql: FATAL: password authentication failed for user postgres
with trust
psql -h localhost
psql (9.3.2)
Type help for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user postgres
But...
find / -name .pgpass
no file found
$ env | grep PG
On 01/05/2014 07:47 AM, Jayadevan M wrote:
With md5
psql
psql: FATAL: password authentication failed for user postgres
with trust
psql -h localhost
psql (9.3.2)
Type help for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user postgres
Just noticed
Jayadevan M maymala.jayade...@gmail.com writes:
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user postgres
[ but there's no .pgpass file ]
Perhaps the postgres user has a password that's marked as expired
in pg_authid.rolvaliduntil? Try
select rolname,
I wrote:
Perhaps the postgres user has a password that's marked as expired
in pg_authid.rolvaliduntil?
Ah, no, scratch that: a look at the code shows the backend doesn't
check rolvaliduntil until after the client has given a valid password.
Seems like psql *must* be getting a password from
On 01/05/2014 07:47 AM, Jayadevan M wrote:
With md5
psql
psql: FATAL: password authentication failed for user postgres
with trust
psql -h localhost
psql (9.3.2)
Type help for help.
back to md5
psql -h localhost
psql: FATAL: password authentication failed for user postgres
But...
find /
I am able to login as postgres with password from the same machine. So it
is not an expiry issue (as you too concluded). Output from strace is about
500 lines. I am pasting what I feel may be relevant. I hope this will be
useful.
execve(/usr/pgsql-9.3/bin/psql, [psql, -h, localhost], [/* 24 vars
On 01/03/2014 09:29 PM, Jayadevan M wrote:
There is only one instance -
ps -eaf | grep bin/postgres | grep -v grep
postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
The basic checks I did -
Connectivity from other machines work (so server is accessible)
No .pgpass
Log entries for 3 situations - 2 successful and one failed attempt -
From non-chroot, shell user postgres
2014-01-05 10:11:58 IST [17008]: [2-1] user=postgres,db=postgres LOG:
connection authorized: user=postgres database=postgres
2014-01-05 10:12:03 IST [17008]: [3-1] user=postgres,db=postgres
On Sat, Jan 4, 2014 at 1:29 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
There is only one instance -
ps -eaf | grep bin/postgres | grep -v grep
postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
This only tells that there is one instance running!
There could
Hi,
I am trying to login from psql and consistently getting a
psql: FATAL: password authentication failed for user xyz for all
users. I am not being prompted for a password at all. I faced a similar
issue sometime ago because there was a .pgpass file and it had wrong
entries. This time there is
Try psql -W for prompting the password forcefully.
On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
Hi,
I am trying to login from psql and consistently getting a
psql: FATAL: password authentication failed for user xyz for all
users. I am not being prompted for
Nope -
psql -W
psql: FATAL: password authentication failed for user postgres
On Fri, Jan 3, 2014 at 2:49 PM, Ashesh Vashi
ashesh.va...@enterprisedb.comwrote:
Try psql -W for prompting the password forcefully.
On Fri, Jan 3, 2014 at 2:46 PM, Jayadevan M
maymala.jayade...@gmail.comwrote:
Hi,
On Fri, Jan 3, 2014 at 3:32 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
Nope -
psql -W
psql: FATAL: password authentication failed for user postgres
There might be possible of the user's password expiration. Make the user's
local authentication as trust, and reload the postgres
On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M maymala.jayade...@gmail.comwrote:
Hi,
I am trying to login from psql and consistently getting a
psql: FATAL: password authentication failed for user xyz for all
users. I am not being prompted for a password at all. I faced a similar
issue sometime
I am able to login from the non-chroot environment. So it is not an issue
with pg_hba.conf and not an issue of password expiration. Is there a debug
psql option?
On Fri, Jan 3, 2014 at 5:09 PM, Chris Curvey ch...@chriscurvey.com wrote:
On Fri, Jan 3, 2014 at 4:16 AM, Jayadevan M
On Fri, Jan 3, 2014 at 5:13 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
I am able to login from the non-chroot environment. So it is not an issue
with pg_hba.conf and not an issue of password expiration. Is there a debug
psql option?
OK.
Have you checked the PGPASSWORD environment
Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to 6.5.
Another interesting thing - if I su - postgres and then try, it works. So
it has something to do with the chrt user (root) settings.
On Fri, Jan 3, 2014 at 5:36 PM, dinesh kumar dineshkuma...@gmail.comwrote:
On Fri, Jan
On 01/03/2014 04:54 AM, Jayadevan M wrote:
Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to
6.5. Another interesting thing - if I su - postgres and then try, it
works. So it has something to do with the chrt user (root) settings.
It might be helpful to detail what are the
Adrian Klaver adrian.kla...@gmail.com writes:
On 01/03/2014 04:54 AM, Jayadevan M wrote:
Yes. All the basic checks I have done. I upgraded from CENTOs 6.4 to
6.5. Another interesting thing - if I su - postgres and then try, it
works. So it has something to do with the chrt user (root)
There is only one instance -
ps -eaf | grep bin/postgres | grep -v grep
postgres 3203 1 0 2013 ?00:02:04 /usr/pgsql-9.3/bin/postgres
The basic checks I did -
Connectivity from other machines work (so server is accessible)
No .pgpass file in the system
Able to login as postgres
On 2013-05-10, Alvaro Herrera alvhe...@2ndquadrant.com wrote:
Tom Lane escribió:
It's fairly common for distro-supplied packages to create a postgres
OS user but not assign it any password. In that state, the only way to
become postgres is to su to it from root, or perhaps from a sudoer
Hi,
Although I'm quite happy with the way my system (Debian sid) has set up
the server (PosgreSQL 9.1), I'm not sure I'm using the
authentication/privilege mechanism properly.
In particular, I'd like to understand how the administrative user
(postgres) is set up. Here is what pg_hba contains:
Sebastian P. Luque splu...@gmail.com writes:
With peer authentication, one can only login as postgres from a local
connection. I'm not sure what password the postgres user was set up in
the OS, however, I assigned one to it (the same as for the PostgreSQL
user). I've read somewhere that the
Tom Lane escribió:
It's fairly common for distro-supplied packages to create a postgres
OS user but not assign it any password. In that state, the only way to
become postgres is to su to it from root, or perhaps from a sudoer
account with root-equivalent privileges. While that might be okay
Thanks!
On Thu, Nov 17, 2011 at 7:33 PM, Adrian Klaver adrian.kla...@gmail.comwrote:
On Thursday, November 17, 2011 3:41:22 pm deepak wrote:
Hi !
Although, it is not clear what options I have to use while
building/configuring?
This same configuration used to work with Postgres 9.0.3,
Hi !
When attempting to start Postgres 9.1.1 with hba conf for local
connections on Windows, I get an error.
e.g. I tried adding the following line to pg_hba.conf
localall user1 trust
and I get:
pg_ctl -D pgsql\data -w start
waiting for server to
On Thursday, November 17, 2011 3:41:22 pm deepak wrote:
Hi !
When attempting to start Postgres 9.1.1 with hba conf for local
connections on Windows, I get an error.
e.g. I tried adding the following line to pg_hba.conf
localall user1 trust
and
On 17/11/2011 23:41, deepak wrote:
Hi !
When attempting to start Postgres 9.1.1 with hba conf for local
connections on Windows, I get an error.
e.g. I tried adding the following line to pg_hba.conf
localall user1 trust
and I get:
pg_ctl -D
On Thursday, November 17, 2011 3:41:22 pm deepak wrote:
Hi !
Although, it is not clear what options I have to use while
building/configuring?
This same configuration used to work with Postgres 9.0.3, though.
Any thoughts?
Error in my previous post the setting should be host not localhost.
Personally I would lean toward making
the bulk of security within the
application so to simplify everything - the
database would do what it
does best - store and manipulate data - and the
application would be the
single point of entry. Protect the servers - keep
the applications (like
On 14 May 2010 09:08, Leonardo F m_li...@yahoo.it wrote:
Personally I would lean toward making
the bulk of security within the
application so to simplify everything - the
database would do what it
does best - store and manipulate data - and the
application would be the
single point of
On Fri, May 14, 2010 at 4:43 AM, Ivan Voras ivo...@freebsd.org wrote:
On 14 May 2010 09:08, Leonardo F m_li...@yahoo.it wrote:
Personally I would lean toward making
the bulk of security within the
application so to simplify everything - the
database would do what it
does best - store
I think this point number 2 is pretty important. If at all possible, keep
the webapp separate from the database, and keep the database
server on a fairly restrictive firewall. This means that someone has
got to get in to the webapp, then hop to the database server, it just
adds another
From: pgsql-general-ow...@postgresql.org on behalf of Leonardo F
Sent: Fri 14/05/2010 14:24
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Authentication method for web app
I think this point number 2 is pretty important. If at all possible, keep
If you build a web-app the user doesn't connect to the db . It connects
to the application.
It is the web app that should have an auth mechanism.
The web app will perform predefined and limited operations and it is the
web programmer that has to guarantee that only operations provided by
the web
Hi all,
we're going to deploy a web app that manages users/roles for another
application.
We want the database to be safe from changes made by malicious
users.
I guess our options are:
1) have the db listen only on local connections; basically when the
machine is accessed the db could be
On 05/13/10 09:21, Leonardo F wrote:
Hi all,
we're going to deploy a web app that manages users/roles for another
application.
We want the database to be safe from changes made by malicious
users.
I guess our options are:
1) have the db listen only on local connections; basically
On Mar 28, 12:57 pm, dp...@pgadmin.org (Dave Page) wrote:
On Sat, Mar 28, 2009 at 4:21 PM, Scott Mead
scott.li...@enterprisedb.com wrote:
On Sat, Mar 28, 2009 at 3:51 AM, ray ray.jos...@cdicorp.com wrote:
I have installed 8.2 on a Windows 2000 laptop.
I think it is installed. From
I have installed 8.2 on a Windows 2000 laptop.
I think it is installed. From the pgAdmin, it shows Servers (1) and
it is named PostgreSQL Database Server 8.2 (localhost:5432). Right
clicking for says I can stop services or disconnect so I am guessing
that it is running.
Is that correct?
On Sat, Mar 28, 2009 at 3:51 AM, ray ray.jos...@cdicorp.com wrote:
I have installed 8.2 on a Windows 2000 laptop.
I think it is installed. From the pgAdmin, it shows Servers (1) and
it is named PostgreSQL Database Server 8.2 (localhost:5432). Right
clicking for says I can stop services or
On Sat, Mar 28, 2009 at 4:21 PM, Scott Mead
scott.li...@enterprisedb.com wrote:
On Sat, Mar 28, 2009 at 3:51 AM, ray ray.jos...@cdicorp.com wrote:
I have installed 8.2 on a Windows 2000 laptop.
I think it is installed. From the pgAdmin, it shows Servers (1) and
it is named PostgreSQL
Just in case others follow in my footsteps - this may prove to be
helpful.
Summary of problem: CentOS 4.4 - SELinux enabled - authorizing pam based
users
### Created file /etc/pam.d/postgresql (I'm using LDAP) [*]
# cat /etc/pam.d/postgresql
#%PAM-1.0
auth required pam_stack.so
Craig White wrote:
logs say...
Nov 8 20:18:26 srv1 postgresql: Starting postgresql service: succeeded
Nov 8 20:18:39 srv1 postgres[21020]: PAM audit_open() failed:
Permission denied
Nov 8 20:18:39 srv1 postgres[21020]: [2-1] LOG: pam_authenticate
failed: System error
Nov 8 20:18:39
On Thu, 2006-11-09 at 12:34 -0300, Alvaro Herrera wrote:
Craig White wrote:
logs say...
Nov 8 20:18:26 srv1 postgresql: Starting postgresql service: succeeded
Nov 8 20:18:39 srv1 postgres[21020]: PAM audit_open() failed:
Permission denied
Nov 8 20:18:39 srv1 postgres[21020]: [2-1]
Craig White [EMAIL PROTECTED] writes:
I haven't had to fool too much with pam for authenticating other
services so I'm a little bit out of my knowledge base but I know that it
was simple to add netatalk into the pam authentication and expected that
postgresql would be similar.
FWIW, we ship
On Thu, 2006-11-09 at 11:51 -0500, Tom Lane wrote:
Craig White [EMAIL PROTECTED] writes:
I haven't had to fool too much with pam for authenticating other
services so I'm a little bit out of my knowledge base but I know that it
was simple to add netatalk into the pam authentication and
Craig White [EMAIL PROTECTED] writes:
On Thu, 2006-11-09 at 11:51 -0500, Tom Lane wrote:
FWIW, we ship this PAM config file in the Red Hat PG RPMs:
that doesn't work at all... /var/log/messages reports...
Sorry, I should have mentioned that that was for recent Fedora branches.
In RHEL4 I
Tom Lane wrote:
Craig White [EMAIL PROTECTED] writes:
I haven't had to fool too much with pam for authenticating other
services so I'm a little bit out of my knowledge base but I know that it
was simple to add netatalk into the pam authentication and expected that
postgresql would be
On Thu, 2006-11-09 at 16:34 -0300, Alvaro Herrera wrote:
Tom Lane wrote:
Craig White [EMAIL PROTECTED] writes:
I haven't had to fool too much with pam for authenticating other
services so I'm a little bit out of my knowledge base but I know that it
was simple to add netatalk into the
CentOS 4.4 which means postgresql-server-7.4.13-2.RHEL4.1
I'm starting to deal with the notion of allowing other users access
(read only) to a db.
Experimenting on my own db...
hostall main_user 192.168.2.10255.255.255.0 trust
hostall all 127.0.0.1
Hi!
I've got some problems with PostgreSQL v8.1.3 . My system is Windows XP Professional Edition.
Here's the deal. For example, when trying to connect to an existing databas, or even
creating a new one with the command createdb [dbname],
different error occurs.
Another example: when running
Here's the deal. For example, when trying to connect to an existing
databas, or even
creating a new one with the command createdb [dbname],
different error occurs.
What errors exactly? We can't guess..
Another example: when running the command psql,
entering the password and hitting
On 5/1/06, chris smith [EMAIL PROTECTED] wrote:
Here's the deal. For example, when trying to connect to an existing
databas, or even
creating a new one with the command createdb [dbname],
different error occurs.
What errors exactly? We can't guess..
Another example: when running the
Hi,
I've got Postgres
8.1.1 running on a Win32 platform. I would like to authenticate users through an
LDAP server and I saw that is possble to do this under a Unix platform with the
pam_ldap package.
Does anybody know if
something similar is at the moment available (or will be available)
Hi,
I've got Postgres 8.1.1 running on a Win32 platform. I would
like to authenticate users through an LDAP server and I saw
that is possble to do this under a Unix platform with the
pam_ldap package.
Does anybody know if something similar is at the moment
available (or will be
Hi all,
suppose that I want to allow one user local access to
template1 under the database account postgres (which is the
superuser for my PostgreSQL). pg_hba.conf contains this:
local all postgresident sameuser
I would then set up pg_ident.conf like this:
I'm working on a PL/SQL set of functions to handle user access
restrictions to particular tables and am wondering:
- Is it safe to use postgresql authentication? Should I (like a LOT
of apps do) build my own authentication tables and just use a common
login/password for the application?
Is anyone aware of FAQs or HowTos for using crypt type authentication and
storing encrypted passwords?
I am mainly interested in two things: 1) if passwords have to be stored in a
plain text file (pg_passwd), can they be stored encrypted? and 2) is it
possible to authenticate with an encrypted
I am trying to connect to postgres from a cgi script. In order for it to connect to
postgres,
I need to create a new postgres user that matches the Unix owner of my Web files. I
don't get an error on create user, but I cannot find a pg_shadow file. Is the
pg_shadow file supposed to be in my
Where, in the backend code, is the authentication handled? And at what
stage is it handled?
Thanks.
--
Matt Barringer
Adversary
WireX, Inc.
65 matches
Mail list logo
