Re: Win32 ODBC Issue! - Mailing list pgsql-odbc
From | Dave Page |
---|---|
Subject | Re: Win32 ODBC Issue! |
Date | |
Msg-id | FED2B709E3270E4B903EB0175A49BCB1047321@dogbert.vale-housing.co.uk Whole thread Raw |
In response to | Win32 ODBC Issue! ("Медер Бакиров" <bakirov@green.net.kg>) |
Responses |
Re: Win32 ODBC Issue!
|
List | pgsql-odbc |
The first correct match in the file is used: host ispstat 0.0.0.0 0.0.0.0 crypt host ispstat 192.168.0.0 255.255.255.0 trust So *all* connections will use crypt. Try swapping the 2 entries around (note that that will open up your database to the entire 192.168.0.x subnet which may be a bad thing - you might want to try password instead of trust :-) ). Regards, Dave. > -----Original Message----- > From: bakirov@green.net.kg [mailto:bakirov@green.net.kg] > Sent: 03 December 2001 15:17 > To: Dave Page > Subject: Re: [ODBC] Win32 ODBC Issue! > > > Here is my conf. file > > Regards, Mika. > > > ----- Original Message ----- > From: "Dave Page" <dpage@vale-housing.co.uk> > To: "'????? ???????'" <bakirov@green.net.kg> > Cc: <pgsql-odbc@postgresql.org> > Sent: Monday, December 03, 2001 7:08 PM > Subject: Re: [ODBC] Win32 ODBC Issue! > > > > Can you post your pg_hba.conf file _to the list_, and note what your > client > > IP address is please - this is almost certainly where the > problem lies > > I would guess. > > > > Regards, Dave. > > > > > -----Original Message----- > > > From: bakirov@green.net.kg [mailto:bakirov@green.net.kg] > > > Sent: 03 December 2001 14:02 > > > To: Dave Page > > > Subject: Re: [ODBC] Win32 ODBC Issue! > > > > > > > > > Hi there! > > > > > > I have tried to give trust and plain password access > settings, but > > > both did not work me! By the way I have a Java application, which > > > uses Postgresql JDBC (v7.2, installed by default), which > comes with > > > RedHat Linux. I wrote an application on Java and it just > works fine > > > with database, whether it uses encrypted or plain > passwords, but I > > > have no luck with ODBC :( ---- > > > :-) > > > I downloaded the latest ODBC form odbc.postgresql.org (which > > > is 7.01.009) and tried it - the problem persists - even I use > > > plain passwords and make that host(network) trust (no > > > password). It gives me an error (encrypted passwords not > supported). > > > > > > Any idea? > > > > > > Thanks... > > > > > > ----- Original Message ----- > > > From: "Dave Page" <dpage@vale-housing.co.uk> > > > To: "'evgeny'" <evgeny@don.sitek.net>; <pgsql-odbc@postgresql.org> > > > Sent: Monday, December 03, 2001 1:49 PM > > > Subject: Re: [ODBC] Win32 ODBC Issue! > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: luk@iplus.ru [mailto:luk@iplus.ru] > > > > > Sent: 03 December 2001 07:43 > > > > > To: pgsql-odbc@postgresql.org > > > > > Subject: Re: [ODBC] Win32 ODBC Issue! > > > > > > > > > > > > > > > ODBC driver is NOT outdated. Drivers has their own > > > versioning, that > > > > > is not the same as Postgresql's one. ODBC does not > > > support encrypted > > > > > passwords, so you have to use plain text authentification > > > with your > > > > > Windows client. > > > > > > > > > > BTW, the latest version of Postgresql ODBC drivers is > 7.01.0009. > > > > > > > > Actually we are vaguely following the PostgreSQL versions > > > - at least > > > > in Major/Minor number. The revision number doesn't follow > > > PostgreSQL > > > > though. The formatting of the number is also slightly > > > different - this > > > > is to > > > comply > > > > with certain elements of the ODBC spec which expects > > > version numbers > > > > in xx.xx.xxxx form - hence the PostgreSQL 7.1 ODBC drivers > > > version is > > > > 07.01.xxxx > > > > > > > > Regards, Dave. > > > > > > > > ---------------------------(end of > > > > broadcast)--------------------------- > > > > TIP 6: Have you searched our list archives? > > > > > > > > http://archives.postgresql.org > > > > > > > > > > ---------------------------(end of > > broadcast)--------------------------- > > TIP 3: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@postgresql.org so that your > > message can get through to the mailing list cleanly > > >
pgsql-odbc by date: