Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0oYR-00005o-TV for pgsql-general@arkaria.postgresql.org; Thu, 01 Dec 2022 18:45:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p0oYQ-0003Wa-Hc for pgsql-general@arkaria.postgresql.org; Thu, 01 Dec 2022 18:45:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0oYQ-0003WM-5I for pgsql-general@lists.postgresql.org; Thu, 01 Dec 2022 18:45:02 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p0oYL-00079Q-B7 for pgsql-general@lists.postgresql.org; Thu, 01 Dec 2022 18:45:01 +0000 Received: by mail-oi1-x22c.google.com with SMTP id m204so2972274oib.6 for ; Thu, 01 Dec 2022 10:44:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=ZkrnkBS3NNjSsRmY+rsEYAEn61tYN9ou44WwckCMVjQ=; b=L9VLKfS4XE2G7l/iHb2c7au1A6ceyh1bQZrolMqVlm9QMV/O3wWObPtC3SUGe0qKeZ jqLy5T0OgDWP+k/G/J71KZ3xeg0kTX7jmoLDJEK/+oMzrZf+WJhN2bNlZhfTcCSlHN2R K2s7GBEaChlAzeFP+KaXWMxA33AfCFPb9Dt17Ltd4ZyGjXcZ1x42wMmM7a4OShEn0NLH ayNe9h5yFE+rrVriVkqDdk/L3SaNF9yWwup4rIkO2GbCMlF+oqaAAwQSvp/BJ9fJoSvA anvhyyvLJ/BuXCYXQe/K0g8l+Wvojbny2L4NtxTGfklELx9GTH3ux+MxeN8CqriO7aMY 6PpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZkrnkBS3NNjSsRmY+rsEYAEn61tYN9ou44WwckCMVjQ=; b=6Uqvm56KK3UJmhyTwDv+t4Hf06C358X757oKwQyCBnvXCPtjK2fbmA+gPYv7tfL421 Xzz5xS9PwlwhTqDstPMSpsr+xo/LpdvzuY+8dkExeQbvyl2EfwXInvS8g0Q4YDhK1yUM n0w/zxO/JDmeJF9dFoe9ABcpynHA/gwJtKZ7KDi8LyqZv615E3rUUkbOTFGWLftNTP1Q gi2q7/Sq+SnfNsjmj+PU0htsN68A+ejhkzhDkkJZwb52fiDvpcHOLJ9yZwxq9KqXiX8A TdGspof0hea/DV51G7d/MBxunGfluS0yb6FXcRYa+iUy282e0FFr06ilZIZIsajwifxH +mXw== X-Gm-Message-State: ANoB5pn50BrlPAbasES99/Jz02GqxdVmimioSZbUUcT3rpKR6IP+r3u4 uYBkdzqSt8ejPpmNLnngYI9DTvh/OhGjfA== X-Google-Smtp-Source: AA0mqf7hA/ugKt+6nXi6V8yN4UnZdalhgeoDFgKnNNxxuoqSw6xrNs3RBFi6ic0DzFjMZOkRyD08Ow== X-Received: by 2002:a54:4399:0:b0:355:bceb:2606 with SMTP id u25-20020a544399000000b00355bceb2606mr27413001oiv.188.1669920295207; Thu, 01 Dec 2022 10:44:55 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id r8-20020a9d5cc8000000b0066cc0525476sm2356417oti.75.2022.12.01.10.44.54 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Dec 2022 10:44:54 -0800 (PST) Message-ID: Date: Thu, 1 Dec 2022 12:44:54 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: how to secure pg_hba.conf Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/1/22 07:45, Rizwan Shaukat wrote: > Hi, > > we hv requiremnt from security to secure pg_hba.conf file was encryption or password protected on server to protect ip visibilty because these server access by application n thy can amend as well. how we can achive it pls pg_hba.conf should only be readable by user postgres, while your application should not be running as user postgres.  Thus, there should not be a problem. -- Angular momentum makes the world go 'round.