Kris Jurka wrote:
>On Wed, 21 Jul 2004, Blaine Simpson wrote:
>
>
>
>>Use "md5" instead of "trust". Besides trust having all sorts of
>>problems to do with ident daemons, I don't even know if the JDBC driver
>>will work with ident, since JDBC network drivers generally pass a
>>username and password.
>>
>>
>
>"trust" has nothing to do with "ident" authentication, trust does not do
>any authentication at all and just lets you in. Using ident
>authentication can be a little tricky with JDBC simply because it uses
>tcp/ip to connect as opposed to unix sockets. On the server side these
>use different code paths for ident authentication with unix sockets
>requiring kernel support for passing user information and tcp/ip sockets
>requiring an ident server.
>
>
Thanks for the correction. I understand now that ident should work if
you can satisfy
the ident requirements.
I still stand by what I said about trust. If you use TCP/IP, with or
without JDBC,
then if you use "trust" you will have to deal with "... problems to do
with ident
deamons". You just said that if you use "trust" with TCP/IP you need
an ident
server (due to differences in local vs. network socket handling in
server code).
Therefore, if you're running TCP/IP, "trust" has a lot to do with
"ident" authentication.
You don't need an ident server if you use "md5", you do need an ident
server if you
use "trust".
>In any case the JDBC driver works fine with both trust and ident
>authentication, as far as I know the only authentication method that are
>unsupported by the JDBC driver is kerberos.
>
>Kris Jurka
>
>
--
ICF: 703-934-3692 Cell: 703-944-9317