ok. Follow what Benoit said and make sure you edit the right file. I had this problem where in FC5 pg_hba.conf are located in three places. One in /usr/share/pgsql second one in /usr/local/pgsql and another one in /var/lib/pgsql/data. When I googled this problem, it turns out that you should edit pg_hba.conf from /usr/share/pgsql or /usr/local/pgsql and execute following command.
<br><br>pg_ctl reload<br><br>This will copy the edited file to /var/lib/pgsql/data directory where the pgsql service reads it from. You should try this first. If this does not work, edit pg_hba.conf from /var/lib/pgsql/data directory. I am not sure if there is any security risk with editing from there. you should edit what Benoit said and leave rest of the settings alone. I think having md5 encryption even on local network is good practice. I hope this works.
<br><br>--V Patel.<br><br><br><div><span class="gmail_quote">On 10/13/06, <b class="gmail_sendername">Benoit Gregoire</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 11 October 2006 00:39, <a href="mailto:email@example.com">firstname.lastname@example.org</a> wrote:<br>> Finally, I've edited the pg_hba.conf file, and all connections from<br>> <a href="http://127.0.0.0">
127.0.0.0</a> (localhost) are trusted, thus we shouldn't need a password.<br><br>That's not what the following snipplet from pg_hba says.<br><br>> ---<br>> # "local" is for Unix domain socket connections only
<br>> #local all all ident sameuser<br>> local all all trust<br>> ---<br>> (Doesn't seem to matter though - either way I get the same error - no<br>> matter if "trust" or "ident sameuser")
<br>><br>> Am I missing something?<br><br>Clearly your pg_hba.conf is still doesn't match your config. Just put<br>host wifidog wifidog <a href="http://127.0.0.1/32">127.0.0.1/32</a> md5<br>local wifidog wifidog md5
<br>and leave the rest default. That way the wifidog user will always use<br>encrypted password authentication.<br><br>It's probably the simplest way without learning the postgress security system<br>(which you really should).
<br><br><br>_______________________________________________<br>WiFiDog mailing list<br><a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br><a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog">