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 1lJtzd-0003if-DM for pgsql-admin@arkaria.postgresql.org; Wed, 10 Mar 2021 08:14:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lJtzc-00082G-A3 for pgsql-admin@arkaria.postgresql.org; Wed, 10 Mar 2021 08:14:56 +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 1lJtzb-000822-Tr for pgsql-admin@lists.postgresql.org; Wed, 10 Mar 2021 08:14:56 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lJtzU-00036B-61 for pgsql-admin@lists.postgresql.org; Wed, 10 Mar 2021 08:14:55 +0000 Received: by mail-ed1-x52a.google.com with SMTP id w9so26535783edt.13 for ; Wed, 10 Mar 2021 00:14:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=o8PgpWoZtLRkZS2NZvnUNdGvivo4o8UDTudAoPZ1be0=; b=ck+jMG6U8pOR9js5O12hHSlqy9eZW+oweQRyZl4JuG51Xk46QFw15Qf3da8b5iKsMj 2p1lz7iX+7wjvTzvcpvZr5Idkt9ym8PnVvocQeM0BJ3gwEc44uiepBFCaV8H7S9inFGK nUwVUxdqcvjmfJyFUsw8zcvHFLmOuvuyHm6EtITjuI/g/TCbHJzmSd7Vw2wqxyBTT1HZ jbNk7keYHHc0M+42C1P1RLRhdo4Bf/MWH/3sUHZHghFO08Z8H4YEqM6m4hfFyJe53/tx nMxacTY/qZS52Wg9cfhDWC4kRQ1TlmssI9HP/WY8YuuN6RuCx67QAtgqUJYUr0qlEKCA MJsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=o8PgpWoZtLRkZS2NZvnUNdGvivo4o8UDTudAoPZ1be0=; b=ihRZFGp7zkrjOAP1uDW/V84korZ05pSW+ZBYA/6Dtx7HO4WAOkB3xbeZ2E1fCPDBsi YLa3zf/4RexyRQS72LVZ5aJ8tSHnreunynzLgi935d7A6yVCln8zD2okEcS0UfD9tJg7 jGl/a2I3JuU4zTUQqH+ROgF+JRy6lQCQwiQPptV83Xvh8vLHdTWNfh039+BHzsqA6RIm 9U25SnaydkNu4TI1QVQwef7KF9VJGRhTMc7HycngCl6aKrnAl11fwCV1lh+OqP234RhR qWoZiV8yPAlA5d/6jqPly0RqjR+gBg8SpHiPHGhfMoQopy8zt4+PBpeQGSFw7IG0ReHR xYJg== X-Gm-Message-State: AOAM532ELSTGMu/1OMfsQ1WR4TWxZhUfsun+q6W5ISPwYEvMeqUpUOma /Z3TayDbcZ7YlwS4O+eR9Dylxg== X-Google-Smtp-Source: ABdhPJylbuAYw1HeNpMwRBXYIo68mX7zf+PXA/bU0Mc8oLLWk/EOgFwPtQwgnDvkrhom3rpvJ8RAFQ== X-Received: by 2002:a50:ec0e:: with SMTP id g14mr1966752edr.264.1615364087248; Wed, 10 Mar 2021 00:14:47 -0800 (PST) Received: from localhost.localdomain (217-149-172-42.nat.highway.telekom.at. [217.149.172.42]) by smtp.gmail.com with ESMTPSA id c7sm4140588edk.50.2021.03.10.00.14.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Mar 2021 00:14:47 -0800 (PST) Message-ID: <8d7c07866ad29e48489d8bae07d519d455f95ccb.camel@cybertec.at> Subject: Re: Lock after several failed login attempts From: Laurenz Albe To: postbox giridhar , pgsql-admin@lists.postgresql.org Date: Wed, 10 Mar 2021 09:14:46 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2021-03-09 at 23:42 +0530, postbox giridhar wrote: > Is it possible to lock a database user after several failed login attempts. > Please suggest me. The only thing built into PostgreSQL that does something in that direction is auth_delay (https://www.postgresql.org/docs/current/auth-delay.html). It introduces a pause after each failed login attempt, which makes brute force attacks much harder. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com