Skip site navigation (1) Skip section navigation (2)

Re: pgaccess et pgsql

From: siruphi <pgsql(at)siruphi(dot)freesurf(dot)fr>
To: pgsql-fr-generale(at)postgresql(dot)org
Subject: Re: pgaccess et pgsql
Date: 2004-03-20 13:19:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-fr-generale
bonjour Apollonie, bonjour à tous
et merci pour ton aide !

>Il faut modifier 2 fichiers permettant les connexions par TCP/IP qui se 
>trouvent certainement dans /var/lib/pgsql/data/ :
>        - postgresql.conf - mettre : tcpip_socket = true


>        - pg_hba.conf (c'est le fichier de contrôle des accès des hôtes à 
>A configurer selon la configuration du réseau. Exemple : 
>host       all     all    trust  # permet la 
>connexion sur le poste lui-même.
>host       all     all    trust  # permet la 
>connexion du réseau

fait aussi, et depuis le message d'erreur de pgaccess a changé, signe 
que le problème vient bien de là, tu as vu juste ;)

'FATAL: missing or erroneous pg_hba.conf file, see postamster log for 

j'ai cherché le log de postmaster (postmaster.log) sans succès (j'ai 
pourtant trouvé des, et .opts)

donc je vous mets le fichier pg_hba.conf dans son intégralité en 
espérant que vous puissiez m'aider à détecter la faille :)

# PostgreSQL Client Authentication Configuration File
# ===================================================
# Refer to the PostgreSQL Administrator's Guide, chapter "Client
# Authentication" for a complete description.  A short synopsis
# follows.
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of three forms:
# local    all       moi   trust   [OPTION]
host      all  all   trust   [OPTION]
# (The uppercase quantities should be replaced by actual values.)
# DATABASE can be "all", "sameuser", "samegroup", a database name (or
# a comma-separated list thereof), or a file name prefixed with "@".
# USER can be "all", an actual user name or a group name prefixed with
# "+" or a list containing either.  IP-ADDRESS and IP-MASK specify the
# set of hosts the record matches.  METHOD can be "trust", "reject",
# "md5", "crypt", "password", "krb4", "krb5", "ident", or "pam".  Note
# that "password" uses clear-text passwords; "md5" is preferred for
# encrypted passwords.  OPTION is the ident map or the name of the PAM
# service.
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect, or use
# "pg_ctl reload".

# Put your actual configuration here
# ----------------------------------
# CAUTION: The default configuration allows any local user to connect
# using any PostgreSQL user name, including the superuser, over either
# Unix-domain sockets or TCP/IP.  If you are on a multiple-user
# machine, the default configuration is probably too liberal for you.
# Change it to use something other than "trust" authentication.
# If you want to allow non-local connections, you need to add more
# "host" records.  Also, remember TCP/IP connections are only enabled
# if you enable "tcpip_socket" in postgresql.conf.

# TYPE  DATABASE    USER        IP-ADDRESS        IP-MASK           METHOD

host     all         all      trust
host     all         all      trust
#host    all                                                          trust
# Using sockets credentials for improved security. Not available everywhere,
# but works on Linux, *BSD (and probably some others)

comme vous voyez, j'ai essayé de le faire le plus permissif possible

merci encore Apollonie pour m'avoir ouvert un peu les yeux 0_0
à bientôt


In response to


pgsql-fr-generale by date

Next:From: Apollonie RaffalliDate: 2004-03-20 14:44:26
Subject: Re: pgaccess et pgsql
Previous:From: Apollonie RaffalliDate: 2004-03-19 21:18:44
Subject: Re: pgaccess et pgsql

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group