public inbox for [email protected]  
help / color / mirror / Atom feed
From: Wim Bertels <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Unexpected authentication behaviour
Date: Tue, 27 Aug 2024 08:49:32 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Hello Izum

in my memory,
this is the fallback behaviour to a safer auth method (from md5 to
scram), the other way around it doesn't work;
correct me if i'm wrong, should be in the documentation

hth,
Wim


Domen Šetar schreef op di 27-08-2024 om 08:00 [+0000]:
> Hi Admins,
>  
> I have strange issue that I can't explain to myself:
>  
> I want to use scram-sha-256 authentication on postgresql 16.
> Parameter password_encryption is set to scram-sha-256. I defined a
> user with scram-sha-256 encoded password.
> My pg_hba.conf have  following  lines:
>  
> # TYPE  DATABASE        USER            ADDRESS                
> METHOD
> local      all                         
> all                                                          peer
> host       all                          all            
>       samenet                     md5
>  
> Even though there is defined md5 authentication method for remote
> logins in pg_hba.conf I can make remote login to my postgresql server
> which is unexpected behaviour of postgresql.
> What did I miss?
>  
> Best regards!
> izum
> Domen Šetar
> Computer Systems Support
> IZUM – Institute of Information Science| Prešernova ulica 17 | 2000
> Maribor |Slovenia
> T: +386 2 25 20 339| M: +386 41 676
> 342|www.izum.si|[email protected]
> 
>  
>  



view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Unexpected authentication behaviour
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox