| From: | David Link <dlink(at)soundscan(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ident authentication with named localhost |
| Date: | 2006-05-12 19:58:25 |
| Message-ID: | 4464E8E1.20200@soundscan.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> David Link <dlink(at)soundscan(dot)com> writes:
>
>> Does anyone know how I can test ident?
>>
>
> I'd try sniffing the IP traffic to and from it with a packet sniffer
> and/or tracing the daemon's system calls with strace. Manually invoking
> the daemon isn't going to prove a lot, you want to watch its reaction
> to Postgres.
>
Thanks for your suggestion. I'm new to the concept of packet sniffing
and tracing. Can you suggest where I should go or what I should read to
better understand this?
> I believe some flavors of identd have debug tracing options, too
> ... check the man page ...
>
Too bad no one else has reported this and already found an answer.
Maybe I should move to md5 authentication, however I wanted to avoid
having to type passwords.
Thanks,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-12 20:02:47 | Re: ident authentication with named localhost |
| Previous Message | Tony Caduto | 2006-05-12 19:40:37 | Re: GUI Interface |