Re: tracking down breakins?

From: "Mike Mascari" <mascarm(at)mascari(dot)com>
To: "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: tracking down breakins?
Date: 2003-01-08 16:36:07
Message-ID: 004601c2b734$0b28c980$0102a8c0@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

tracking down breakins?IIRC, Microsoft Access first attempts to use the userid associated with the current Access session (default 'Admin') when access data through ODBC linked tables.

FWIW,

Mike Mascari
mascarm(at)mascari(dot)com
----- Original Message -----
From: Johnson, Shaunn

Running PostgreSQL 7.2.1 on RedHat Linux 7.2

A similar question to what David Siebert was
asking - I am trying to locate users that are trying
to log in as someone else in PostgreSQL.

I have the postmaster running the debug with level 2
and when I review my logs, I see this:

[snip from logs]

Jan 6 09:11:46 test_srv postgres[30134]: [228919] FATAL 1: Password
authentication failed for user "Admin"

[/snip from logs]

How can I trace back *who* is trying to log in as 'Admin' and how
can I stop it? If I run debug on any higher level, the response is
much slower; perhaps there is another way?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-01-08 17:11:18 Re: Postgres (psql ?) rounds all odd second values to even seconds fo r timestamp(0) data type
Previous Message Johnson, Shaunn 2003-01-08 16:24:57 too many Fatal Error 1: shutdown messages