Sicherheit

Sind diese Einstellungen passend, wenn ich dafür sorgen will das nur der Localhost zugriff auf Postgre bekommt?
Ich gehe davon aus da halt 127.0.0.1/32 bei der Adresse steht aber ich frage mal lieber nach :astonished:
Der Zugriff allein Über Unix Socket funktioniert leider nicht. Da hab ich offensichtlich das Prinzip von den Sockets denke ich nicht verstanden :confused:
Was ich nämlich schade finde ist mit den Einstellungen sehe ich das mein Port 5432 offen ist was zu 99% von Postgre kommt

PostgreSQL Client Authentication Configuration File

===================================================

Refer to the “Client Authentication” section in the PostgreSQL

documentation for a complete description of this file. 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 these forms:

local DATABASE USER METHOD [OPTIONS]

host DATABASE USER ADDRESS METHOD [OPTIONS]

hostssl DATABASE USER ADDRESS METHOD [OPTIONS]

hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]

(The uppercase items must 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”, “samerole”, “replication”, a

database name, or a comma-separated list thereof. The “all”

keyword does not match “replication”. Access to replication

must be enabled in a separate record (see example below).

USER can be “all”, a user name, a group name prefixed with “+”, or a

comma-separated list thereof. In both the DATABASE and USER fields

you can also write a file name prefixed with “@” to include names

from a separate file.

ADDRESS specifies the set of hosts the record matches. It can be a

host name, or it is made up of an IP address and a CIDR mask that is

an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that

specifies the number of significant bits in the mask. A host name

that starts with a dot (.) matches a suffix of the actual host name.

Alternatively, you can write an IP address and netmask in separate

columns to specify the set of hosts. Instead of a CIDR-address, you

can write “samehost” to match any of the server’s own IP addresses,

or “samenet” to match any address in any subnet that the server is

directly connected to.

METHOD can be “trust”, “reject”, “md5”, “password”, “gss”, “sspi”,

“krb5”, “ident”, “peer”, “pam”, “ldap”, “radius” or “cert”. Note that

“password” sends passwords in clear text; “md5” is preferred since

it sends encrypted passwords.

OPTIONS are a set of options for the authentication in the format

NAME=VALUE. The available options depend on the different

authentication methods – refer to the “Client Authentication”

section in the documentation for a list of which options are

available for which authentication methods.

Database and user names containing spaces, commas, quotes and other

special characters must be quoted. Quoting one of the keywords

“all”, “sameuser”, “samerole” or “replication” makes the name lose

its special character, and just match a database or username with

that name.

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. You can

use “pg_ctl reload” to do that.

Put your actual configuration here

----------------------------------

If you want to allow non-local connections, you need to add more

“host” records. In that case you will also need to make PostgreSQL

listen on a non-local interface via the listen_addresses

configuration parameter, or via the -i or -h command line switches.




\

DO NOT DISABLE!

If you change this first entry you will need to make sure that the

database superuser can access the database using some other method.

Noninteractive access to all databases is required during automatic

maintenance (custom daily cronjobs, replication, and similar tasks).

Database administrative login by Unix domain socket

local all postgres peer

TYPE DATABASE USER ADDRESS METHOD

“local” is for Unix domain socket connections only

local all all peer

IPv4 local connections:

host all all 127.0.0.1/32 md5

IPv6 local connections:

host all all ::1/128 md5

Allow replication connections from localhost, by a user with the

replication privilege.

#local replication postgres peer
#host replication postgres 127.0.0.1/32 md5
#host replication postgres ::1/128 md5

Zu den Einstellungen kann ich nichts sagen, aber: es heißt Postgres oder PostgreSQL (oder einfach nur pg), aber nicht “Postgre”

“peer” ist gleich zu “ident”: der Unix-User muß gleich dem DB-User sein. Das hast bei ‘local’ eingestellt. Also, wenn Du via sudo zu ‘postres’ wirst kannst Dich dann als ‘postgres’ an der DB anmelden.

Ansonsten sieht es für mich so aus, daß man sich wirklich nur von 127.0.0.1 anmelden kann.

Den Port hast Du offenbar derzeit auf

listen_addresses = “*” gesetzt, Du kannst das gerne auf localhost begrenzen. Dann lauscht er nur noch an der lokalen 127.0.0.1.

Du kannst das mit netstat prüfen, mal so als Hinweis…

Andreas

Tut mir leid aber den listen_addresses teil habe ich jetzt leider nicht ganz verstanden.
Also ich selber habe zu 99.999% nirgendwo in die confi listen_addresses = “*” geschrieben.
In der confi steht nur einmal was von listen_addresses und das ist kommentiert # xD :slight_smile:

Mein Ports habe ich übrigens mit Zenmap überprüft.

Ja, in der postgresql.conf stehen alle Default-Werte mit einem Kommentarzeichen. Will man diese verändern, entfernt man dieses und ändert es.
Hast Du Windows oder *NIX? Windows kennt keine Unix-Socken, da geht NUR TCP/IP, als host - Zugriff, und da ist default listen_adresses auf * gesetzt.

Ich hab Debian :slight_smile: .
Nach hinzufügen von Liste_Adress habe ich ein neues Problem :confused:

pgadmin meldet mir.

Server doesn’t listen
The server doesn’t accept connections: the connection library reports
konnte nicht mit dem Server verbinden: Verbindungsaufbau abgelehnt Läuft der Server auf dem Host »localhost« (::1) und akzeptiert er TCP/IP-Verbindungen auf Port 5432? konnte nicht mit dem Server verbinden: Verbindungsaufbau abgelehnt Läuft der Server auf dem Host »localhost« (127.0.0.1) und akzeptiert er TCP/IP-Verbindungen auf Port 5432?

Hier meine config.

PostgreSQL Client Authentication Configuration File

===================================================

Refer to the “Client Authentication” section in the PostgreSQL

documentation for a complete description of this file. 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 these forms:

local DATABASE USER METHOD [OPTIONS]

host DATABASE USER ADDRESS METHOD [OPTIONS]

hostssl DATABASE USER ADDRESS METHOD [OPTIONS]

hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]

(The uppercase items must 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”, “samerole”, “replication”, a

database name, or a comma-separated list thereof. The “all”

keyword does not match “replication”. Access to replication

must be enabled in a separate record (see example below).

USER can be “all”, a user name, a group name prefixed with “+”, or a

comma-separated list thereof. In both the DATABASE and USER fields

you can also write a file name prefixed with “@” to include names

from a separate file.

ADDRESS specifies the set of hosts the record matches. It can be a

host name, or it is made up of an IP address and a CIDR mask that is

an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that

specifies the number of significant bits in the mask. A host name

that starts with a dot (.) matches a suffix of the actual host name.

Alternatively, you can write an IP address and netmask in separate

columns to specify the set of hosts. Instead of a CIDR-address, you

can write “samehost” to match any of the server’s own IP addresses,

or “samenet” to match any address in any subnet that the server is

directly connected to.

METHOD can be “trust”, “reject”, “md5”, “password”, “gss”, “sspi”,

“krb5”, “ident”, “peer”, “pam”, “ldap”, “radius” or “cert”. Note that

“password” sends passwords in clear text; “md5” is preferred since

it sends encrypted passwords.

OPTIONS are a set of options for the authentication in the format

NAME=VALUE. The available options depend on the different

authentication methods – refer to the “Client Authentication”

section in the documentation for a list of which options are

available for which authentication methods.

Database and user names containing spaces, commas, quotes and other

special characters must be quoted. Quoting one of the keywords

“all”, “sameuser”, “samerole” or “replication” makes the name lose

its special character, and just match a database or username with

that name.

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. You can

use “pg_ctl reload” to do that.

Put your actual configuration here

----------------------------------

If you want to allow non-local connections, you need to add more

“host” records. In that case you will also need to make PostgreSQL

listen on a non-local interface via the listen_addresses

configuration parameter, or via the -i or -h command line switches.

listen_addresses = “127.0.0.1”

\

DO NOT DISABLE!

If you change this first entry you will need to make sure that the

database superuser can access the database using some other method.

Noninteractive access to all databases is required during automatic

maintenance (custom daily cronjobs, replication, and similar tasks).

Database administrative login by Unix domain socket

local all postgres peer

TYPE DATABASE USER ADDRESS METHOD

“local” is for Unix domain socket connections only

local all all peer

IPv4 local connections:

host all all 127.0.0.1/32 md5

IPv6 local connections:

host all all ::1/128 md5

Allow replication connections from localhost, by a user with the

replication privilege.

#local replication postgres peer
#host replication postgres 127.0.0.1/32 md5
#host replication postgres ::1/128 md5