Oliver Elphick wrote:
well....I just found it out by installing libapache-auth-pgsql :-)On Thu, 2004-06-24 at 05:17, dodol garut wrote: all i need to dig out now is postgre accessing security. since techtables always show "Unable to connect to PostgreSQL server: could not translate host name "127.0.0.1," to address: Name or service not known" Simply said, the techtables can not access to postgre database because he doesn't know the host ( am i right or....???) I've looked at a file called global.inc which, I guess, hold the server configuration cause it contains my database and username for the techtables and hostname and database port. the value is : $host = "127.0.0.1"; ---> i made it myself $port = "5432"; ----> postgre port my problem probably in pg_hba.conf, which untill now, i haven't figure out how. the script which is called to make connection to postgre is like this : <?php function opendb() { global $host, $username, $database, $password; $dbconn = pg_connect("host=$host, dbname=$database user=$username password=$password") or die("Cannot connect"); return $dbconn; } i'm no PHP expert so i dunno if it's just like i guess..... well.....i guess, i still have a job to do .... :-( attachment is my pg_hba.conf ( ....if somebody there put a mercy on me helping me get through this ) cheers all, me -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.4 (GNU/Linux) mQGiBEDato0RBADHD8bKvVCTORppg/pot1Zuyx4Joz/IC34aZlLkG7/JNEVemqiB jSVgnwxa9UNs9Chz9CT6vqzw1pgPXDAb1rD91kbupatgaFUlNEwAW/v2eH8LQEYz 3NicbaysYeeJLBOYlwtmbZWrV8KKoSNrHWxZRjfl4a7TGggllou6+sAQTwCg/2Q2 lLLdPjuaXGiRHqpHFuFWVT8D/Rfzi89GrGWwharBmqNlq3WNJJSK4NdZUy6yFrfY mqaytOBUq6wWoM9OdvAciS4R1qVK2GItV2xIX9N47zeEXspsANF3PyH6PSdXBYfO CDL6jdkL1JS/E+QQcOsqbwkJOa3IpSuJPuE0IuYj9G2pEUNFR9/QiNVq2ysqUK8I V/8VBACmL758SPyrMSwA2sPGiRbSndr0Bc6XW/YPwvJNQsU+zzX+qtAP4K3oEX7R z1OD6LfkJAvrCLswNJbyIlrsFSo/NxlsqnWgKU4K4qsntvMA2UiyAUCOONCn+7Uo V8UVK/3ZKRAlnTM6YdxEWe1c09pP3k4kxGdii5E3cJu6a1a4jbYAAAAxZGViaWFu IChKVVNUIFNJR05BVFVSRSkgPGRlYl9taWxpc3RAeWFob28uY29tLnNnPohbBBMR AgAbBQJA2raNBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEP6KKTciHvMpKQgAoLl1 8lYWPDqcTtRwNyPBA5UhlbHIAKDAjaZYyTgyYU2xtacqPDqsMzf/N7kBDQRA2raQ EAQAqzfMQUbVLt/iFTDFcI3XSO26v2BYQAvHdRkMGo8AFrffJCbEFfTlyCrTbhIH KB0D6Z8+lEqdsjJlwleNWDWTu3gYhOvUeGqCiNmPRGeYjM5VatsUNMQLS6qGVbpa iHXZ75e6Vco3MjMEKN1KQDn3QdtWJcW32LPA5XqrEbInV1MAAwYD/idygDdnBgOU NEfN+JVFr3OUuVBTxky6VZ08mYbjVmE/tFDh+H9o0GdHAMrvXbITFau6BR3ykNXt VPRMlT+g1pCe91RovR+WwfLItFnCeB6lfiu4tsdPWeBWPKbdQO7zb1Wj6U/yo5Jc jNjQjBHpxuoTpicYYgKiFIIhHzIGkt9MiEYEGBECAAYFAkDatpAACgkQ/oopNyIe 8ykmwgCfZLcfyNlAVIpfhyhjJPDbLYJsBc8AnRz9PqrchdlrWSonVBgsHg0VZml+ =Ow66 -----END PGP PUBLIC KEY BLOCK----- |
# 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 seven forms: # # local DATABASE USER METHOD [OPTION] # host DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] # hostssl DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] # hostnossl DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] # host DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] # hostssl DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] # hostnossl DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] # # (The uppercase quantities should be replaced by actual values.) # The first field is the connection type: "local" is a Unix-domain socket, # "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an # SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket. # 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 # "+", an include file prefixed with "@" or a list containing either. # IP-ADDRESS and IP-MASK specify the set of hosts the record matches. # CIDR-MASK is an integer between 0 and 32 (IPv6) or 128(IPv6) # inclusive, that specifies the number of significant bits in the # mask, so an IPv4 CIDR-MASK of 8 is equivalent to an IP-MASK of # 255.0.0.0, and an IPv6 CIDR-MASK of 64 is equivalent to an IP-MASK # of ffff:ffff:ffff:ffff::. METHOD can be "trust", "reject", "md5", # "crypt", "password", "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. # # INCLUDE FILES: # If you use include files for users and/or databases (see PostgreSQL # documentation, section 19.1), these files must be placed in the # database directory. Usually this is /var/lib/postgres/data/, but # that can be changed in /etc/postgresql/postmaster.conf with the # POSTGRES_DATA variable. Putting them in /etc/postgresql/ will NOT # work since the configuration files are only symlinked from # POSTGRES_DATA. # # 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". # # Upstream default configuration # # The following configuration is the upstream default, which allows # unrestricted access to amy database by any user on the local machine. # # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD # #local all all trust # IPv4-style local connections: #host all all 127.0.0.1 255.255.255.255 trust # IPv6-style local connections: # # Put your actual configuration here # ---------------------------------- # # This default configuration allows any local user to connect as himself # without a password, either through a Unix socket or through TCP/IP; users # on other machines are denied access. # # If you want to allow non-local connections, you need to add more # "host" records before the final line that rejects all TCP/IP connections. # Also, remember TCP/IP connections are only enabled if you enable # "tcpip_socket" in /etc/postgresql/postgresql.conf. # # DO NOT DISABLE! # If you change this first entry you will need to make sure the postgres user # can access the database using some other method. The postgres user needs # non-interactive access to all databases during automatic maintenance # (see the vacuum command and the /usr/lib/postgresql/bin/do.maintenance # script). # # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD # Database administrative login by UNIX sockets #local all postgres ident sameuser local all postgres trust # # All other connections by UNIX sockets #local all all ident sameuser local all all trust # # All IPv4 connections from localhost host all all 127.0.0.1 255.255.255.255 ident sameuser # # All IPv6 localhost connections host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff ident sameuser host all all ::ffff:127.0.0.1/128 ident sameuser #host all all ::ffff:172.16.1.0/255 trust #host all all ::ffff:172.16.2.0/255 trust #host all all ::ffff:127.0.0.1/128 trust # # reject all other connection attempts host all all 0.0.0.0 0.0.0.0 reject
