Project

General

Profile

Actions

User story #8901

closed

Beautify pg_hba.conf

Added by Florian Heigl over 7 years ago. Updated over 4 years ago.

Status:
Released
Priority:
4
Category:
Packaging
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Rudder adds it's own entries to pg_hba.conf.

Unfortunately, they are not marked as managed by rudder.
Also they're at the start of the file instead of the end, where all the other auth settings are.
Looks really sloppy, like a drunk admin did it.

@[root@rudder data]# head pg_hba.conf ; echo "SNIPSNAP" ; tail pg_hba.conf
host all rudder 127.0.0.1/32 md5
host all rudder ::1/128 md5
  1. PostgreSQL Client Authentication Configuration File
  2. =================================================== #
  3. Refer to the "Client Authentication" section in the
  4. PostgreSQL documentation for a complete description
  5. of this file. A short synopsis follows. #
  6. This file controls: which hosts are allowed to connect, how clients
    SNIPSNAP
  1. TYPE DATABASE USER CIDR-ADDRESS METHOD
  1. "local" is for Unix domain socket connections only
    local all all ident
  2. IPv4 local connections:
    host all all 127.0.0.1/32 ident
  3. IPv6 local connections:
    host all all ::1/128 ident@

Subtasks 1 (0 open1 closed)

Bug #14848: Parent ticket broke postgresql identification ReleasedNicolas CHARLESActions

Related issues 1 (0 open1 closed)

Related to Rudder - User story #14780: Beautify pg_hba.conf ReleasedBenoît PECCATTEActions
Actions

Also available in: Atom PDF