public inbox for [email protected]help / color / mirror / Atom feed
Re: Cannot connect local with ttrust (pg_upgrade assumes it) 13+ messages / 4 participants [nested] [flat]
* Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 17:03 Francisco Olarte <[email protected]> 0 siblings, 2 replies; 13+ messages in thread From: Francisco Olarte @ 2025-04-09 17:03 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; +Cc: [email protected] <[email protected]> On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: > Asking for help with inability to connect local using trust > Fail > #local all all trust > #local all dbauser peer > OK > #host all all 127.0.0.1/32 trust How are you connecting? Your symptoms matches confusing local with TCP/IP to localhost. They are not the same thing. Also, are you on windows? ( which does not have unix sockets ). local This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket connections are disallowed. host This record matches connection attempts made using TCP/IP. host records match SSL or non-SSL connection attempts as well as GSSAPI encrypted or non-GSSAPI encrypted connection attempts. On a unix host psql -h localhost will use the host line, psql -h /socket/path will go to the local one, and no -h defaults to socket. On a windows host it default to tcp/ip to localhost. Francisco Olarte. ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 17:44 Abraham, Danny <[email protected]> parent: Francisco Olarte <[email protected]> 1 sibling, 1 reply; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 17:44 UTC (permalink / raw) To: Francisco Olarte <[email protected]>; +Cc: [email protected] <[email protected]> Thanks for the answers. All the 3 lines are, of course, uncommented for the test. I am using Linux, socket is in /tmp, i see the .s files , but local trust still does not connect. Sent from Workspace ONE Boxer On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: > Asking for help with inability to connect local using trust > Fail > #local all all trust > #local all dbauser peer > OK > #host all all 127.0.0.1/32 trust How are you connecting? Your symptoms matches confusing local with TCP/IP to localhost. They are not the same thing. Also, are you on windows? ( which does not have unix sockets ). local This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket connections are disallowed. host This record matches connection attempts made using TCP/IP. host records match SSL or non-SSL connection attempts as well as GSSAPI encrypted or non-GSSAPI encrypted connection attempts. On a unix host psql -h localhost will use the host line, psql -h /socket/path will go to the local one, and no -h defaults to socket. On a windows host it default to tcp/ip to localhost. Francisco Olarte. ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 17:45 Abraham, Danny <[email protected]> parent: Francisco Olarte <[email protected]> 1 sibling, 1 reply; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 17:45 UTC (permalink / raw) To: Francisco Olarte <[email protected]>; +Cc: [email protected] <[email protected]> Failure eans going down the hba list and asking for the password. Sent from Workspace ONE Boxer On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: > Asking for help with inability to connect local using trust > Fail > #local all all trust > #local all dbauser peer > OK > #host all all 127.0.0.1/32 trust How are you connecting? Your symptoms matches confusing local with TCP/IP to localhost. They are not the same thing. Also, are you on windows? ( which does not have unix sockets ). local This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket connections are disallowed. host This record matches connection attempts made using TCP/IP. host records match SSL or non-SSL connection attempts as well as GSSAPI encrypted or non-GSSAPI encrypted connection attempts. On a unix host psql -h localhost will use the host line, psql -h /socket/path will go to the local one, and no -h defaults to socket. On a windows host it default to tcp/ip to localhost. Francisco Olarte. ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 17:47 Adrian Klaver <[email protected]> parent: Abraham, Danny <[email protected]> 0 siblings, 0 replies; 13+ messages in thread From: Adrian Klaver @ 2025-04-09 17:47 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; Francisco Olarte <[email protected]>; +Cc: [email protected] <[email protected]> On 4/9/25 10:44 AM, Abraham, Danny wrote: > Thanks for the answers. > All the 3 lines are, of course, uncommented for the test. Then provide the actual configuration you are working with. > I am using Linux, socket is in /tmp, i see the .s files , but local > trust still does not connect. Provide: a) The connection string you are using. b) The error you get. > > Sent from Workspace ONE Boxer > > On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: > On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: >> Asking for help with inability to connect local using trust >> Fail >> #local all all trust >> #local all dbauser peer >> OK >> #host all all 127.0.0.1/32 trust > > How are you connecting? Your symptoms matches confusing local with > TCP/IP to localhost. They are not the same thing. > Also, are you on windows? ( which does not have unix sockets ). > > local > This record matches connection attempts using Unix-domain sockets. > Without a record of this type, Unix-domain socket connections are > disallowed. > host > This record matches connection attempts made using TCP/IP. host > records match SSL or non-SSL connection attempts as well as GSSAPI > encrypted or non-GSSAPI encrypted connection attempts. > > On a unix host psql -h localhost will use the host line, psql -h > /socket/path will go to the local one, and no -h defaults to socket. > On a windows host it default to tcp/ip to localhost. > > Francisco Olarte. -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 17:49 Adrian Klaver <[email protected]> parent: Abraham, Danny <[email protected]> 0 siblings, 1 reply; 13+ messages in thread From: Adrian Klaver @ 2025-04-09 17:49 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; Francisco Olarte <[email protected]>; +Cc: [email protected] <[email protected]> On 4/9/25 10:45 AM, Abraham, Danny wrote: > Failure eans going down the hba list and asking for the password. In pg_hba.conf first match wins, sounds like you have password auth line before the trust lines. You need to provide the complete pg_hba.conf auth lines you are working with. > > > Sent from Workspace ONE Boxer > > On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: > On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: >> Asking for help with inability to connect local using trust >> Fail >> #local all all trust >> #local all dbauser peer >> OK >> #host all all 127.0.0.1/32 trust > > How are you connecting? Your symptoms matches confusing local with > TCP/IP to localhost. They are not the same thing. > Also, are you on windows? ( which does not have unix sockets ). > > local > This record matches connection attempts using Unix-domain sockets. > Without a record of this type, Unix-domain socket connections are > disallowed. > host > This record matches connection attempts made using TCP/IP. host > records match SSL or non-SSL connection attempts as well as GSSAPI > encrypted or non-GSSAPI encrypted connection attempts. > > On a unix host psql -h localhost will use the host line, psql -h > /socket/path will go to the local one, and no -h defaults to socket. > On a windows host it default to tcp/ip to localhost. > > Francisco Olarte. -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* RE: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 19:21 Abraham, Danny <[email protected]> parent: Adrian Klaver <[email protected]> 0 siblings, 2 replies; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 19:21 UTC (permalink / raw) To: Adrian Klaver <[email protected]>; Francisco Olarte <[email protected]>; +Cc: [email protected] <[email protected]>; Abraham, Danny <[email protected]> Thanks again. Here is the example: >>>>>>>> dba-tlv-x6y64k% cat pg_hba.conf # TYPE DATABASE USER CIDR-ADDRESS METHOD local all all trust host all all 0.0.0.0/0 scram-sha-256 dba-tlv-x6y64k% pg_ctl reload server signaled dba-tlv-x6y64k% psql -Upostgres Password for user postgres: psql (17.4) Type "help" for help. ctrlmdb=# >>>>>>> PSQL should not have asked for the password. Thanks Danny -----Original Message----- From: Adrian Klaver <[email protected]> Sent: Wednesday, April 9, 2025 8:49 PM To: Abraham, Danny <[email protected]>; Francisco Olarte <[email protected]> Cc: [email protected] Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) On 4/9/25 10:45 AM, Abraham, Danny wrote: > Failure eans going down the hba list and asking for the password. In pg_hba.conf first match wins, sounds like you have password auth line before the trust lines. You need to provide the complete pg_hba.conf auth lines you are working with. > > > Sent from Workspace ONE Boxer > > On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: > On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: >> Asking for help with inability to connect local using trust Fail >> #local all all trust #local >> all dbauser peer OK #host all all >> 127.0.0.1/32 trust > > How are you connecting? Your symptoms matches confusing local with > TCP/IP to localhost. They are not the same thing. > Also, are you on windows? ( which does not have unix sockets ). > > local > This record matches connection attempts using Unix-domain sockets. > Without a record of this type, Unix-domain socket connections are > disallowed. > host > This record matches connection attempts made using TCP/IP. host > records match SSL or non-SSL connection attempts as well as GSSAPI > encrypted or non-GSSAPI encrypted connection attempts. > > On a unix host psql -h localhost will use the host line, psql -h > /socket/path will go to the local one, and no -h defaults to socket. > On a windows host it default to tcp/ip to localhost. > > Francisco Olarte. -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* FW: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 19:23 Abraham, Danny <[email protected]> parent: Abraham, Danny <[email protected]> 1 sibling, 1 reply; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 19:23 UTC (permalink / raw) To: [email protected] <[email protected]> Thanks again. Here is the example: >>>>>>>> dba-tlv-x6y64k% cat pg_hba.conf # TYPE DATABASE USER CIDR-ADDRESS METHOD local all all trust host all all 0.0.0.0/0 scram-sha-256 dba-tlv-x6y64k% pg_ctl reload server signaled dba-tlv-x6y64k% psql -Upostgres Password for user postgres: psql (17.4) Type "help" for help. ctrlmdb=# >>>>>>> PSQL should not have asked for the password. Thanks Danny -----Original Message----- From: Adrian Klaver <[email protected]> Sent: Wednesday, April 9, 2025 8:49 PM To: Abraham, Danny <[email protected]>; Francisco Olarte <[email protected]> Cc: [email protected] Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) On 4/9/25 10:45 AM, Abraham, Danny wrote: > Failure eans going down the hba list and asking for the password. In pg_hba.conf first match wins, sounds like you have password auth line before the trust lines. You need to provide the complete pg_hba.conf auth lines you are working with. > > > Sent from Workspace ONE Boxer > > On Apr 9, 2025 20:04, Francisco Olarte <[email protected]> wrote: > On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <[email protected]> wrote: >> Asking for help with inability to connect local using trust Fail >> #local all all trust #local >> all dbauser peer OK #host all all >> 127.0.0.1/32 trust > > How are you connecting? Your symptoms matches confusing local with > TCP/IP to localhost. They are not the same thing. > Also, are you on windows? ( which does not have unix sockets ). > > local > This record matches connection attempts using Unix-domain sockets. > Without a record of this type, Unix-domain socket connections are > disallowed. > host > This record matches connection attempts made using TCP/IP. host > records match SSL or non-SSL connection attempts as well as GSSAPI > encrypted or non-GSSAPI encrypted connection attempts. > > On a unix host psql -h localhost will use the host line, psql -h > /socket/path will go to the local one, and no -h defaults to socket. > On a windows host it default to tcp/ip to localhost. > > Francisco Olarte. -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: FW: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 19:31 Adrian Klaver <[email protected]> parent: Abraham, Danny <[email protected]> 0 siblings, 0 replies; 13+ messages in thread From: Adrian Klaver @ 2025-04-09 19:31 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; [email protected] <[email protected]> On 4/9/25 12:23, Abraham, Danny wrote: > Thanks again. > Here is the example: >>>>>>>>> > dba-tlv-x6y64k% cat pg_hba.conf > # TYPE DATABASE USER CIDR-ADDRESS METHOD > local all all trust > host all all 0.0.0.0/0 scram-sha-256 > > dba-tlv-x6y64k% pg_ctl reload > server signaled > dba-tlv-x6y64k% psql -Upostgres > Password for user postgres: > psql (17.4) > Type "help" for help. > > ctrlmdb=# >>>>>>>> > PSQL should not have asked for the password. Do you have more then one instance of Postgres running on this machine? If so are you editing the correct pg_hba.conf? How did you install Postgres and what Linux distro(& version) are you using? > Thanks > Danny > > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 19:34 David G. Johnston <[email protected]> parent: Abraham, Danny <[email protected]> 1 sibling, 1 reply; 13+ messages in thread From: David G. Johnston @ 2025-04-09 19:34 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; +Cc: Adrian Klaver <[email protected]>; Francisco Olarte <[email protected]>; [email protected] On Wed, Apr 9, 2025, 12:21 Abraham, Danny <[email protected]> wrote: > Thanks again. > Here is the example: > >>>>>>>> > dba-tlv-x6y64k% cat pg_hba.conf > # TYPE DATABASE USER CIDR-ADDRESS METHOD > local all all trust > host all all 0.0.0.0/0 scram-sha-256 > > dba-tlv-x6y64k% pg_ctl reload > server signaled > dba-tlv-x6y64k% psql -Upostgres > Password for user postgres: > psql (17.4) > Type "help" for help. > > ctrlmdb=# > >>>>>>> > PSQL should not have asked for the password. > Thanks > Danny > Suggests there are environment variables coming into play making non-default choices for you. Namely, making you not use local as the connection method. David J. ^ permalink raw reply [nested|flat] 13+ messages in thread
* RE: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 20:40 Abraham, Danny <[email protected]> parent: David G. Johnston <[email protected]> 0 siblings, 2 replies; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 20:40 UTC (permalink / raw) To: David G. Johnston <[email protected]>; Adrian Klaver <[email protected]>; Francisco Olarte <[email protected]>; [email protected] <[email protected]>; +Cc: Abraham, Danny <[email protected]> Thanks again. 1. No other PG instances on this Linux machine. 2. RHEL9 3. Our compiled PG which is embedded within our product/site 4. I am not aware of an env variable that changes the top down matching on pg_hba.conf Danny From: David G. Johnston <[email protected]> Sent: Wednesday, April 9, 2025 10:34 PM To: Abraham, Danny <[email protected]> Cc: Adrian Klaver <[email protected]>; Francisco Olarte <[email protected]>; [email protected] Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) On Wed, Apr 9, 2025, 12:21 Abraham, Danny <[email protected]<mailto:[email protected]>> wrote: Thanks again. Here is the example: >>>>>>>> dba-tlv-x6y64k% cat pg_hba.conf # TYPE DATABASE USER CIDR-ADDRESS METHOD local all all trust host all all 0.0.0.0/0<https://urldefense.com/v3/__http:/0.0.0.0/0__;!!PEZBYkTc!e_x_LCIABYSpqVum5S6Hr0TtEs6P4NaumHqEqyXEa3E...; scram-sha-256 dba-tlv-x6y64k% pg_ctl reload server signaled dba-tlv-x6y64k% psql -Upostgres Password for user postgres: psql (17.4) Type "help" for help. ctrlmdb=# >>>>>>> PSQL should not have asked for the password. Thanks Danny Suggests there are environment variables coming into play making non-default choices for you. Namely, making you not use local as the connection method. David J. ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 20:45 Adrian Klaver <[email protected]> parent: Abraham, Danny <[email protected]> 1 sibling, 0 replies; 13+ messages in thread From: Adrian Klaver @ 2025-04-09 20:45 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; David G. Johnston <[email protected]>; Francisco Olarte <[email protected]>; [email protected] <[email protected]> On 4/9/25 13:40, Abraham, Danny wrote: > Thanks again. > > 1. No other PG instances on this Linux machine. > 2. RHEL9 > 3. Our compiled PG which is embedded within our product/site > 4. I am not aware of an env variable that changes the top down matching > on pg_hba.conf From here: https://www.postgresql.org/docs/current/libpq-envars.html "The following environment variables can be used to select default connection parameter values, which will be used by PQconnectdb, PQsetdbLogin and PQsetdb if no value is directly specified by the calling code. PGHOST behaves the same as the host connection parameter. ... " So if you have PGHOST set to say localhost it would be added to: psql -Upostgres > > Danny > > *From:*David G. Johnston <[email protected]> > *Sent:* Wednesday, April 9, 2025 10:34 PM > *To:* Abraham, Danny <[email protected]> > *Cc:* Adrian Klaver <[email protected]>; Francisco Olarte > <[email protected]>; [email protected] > *Subject:* Re: [EXTERNAL] Re: Cannot connect local with ttrust > (pg_upgrade assumes it) > > On Wed, Apr 9, 2025, 12:21 Abraham, Danny <[email protected] > <mailto:[email protected]>> wrote: > > Thanks again. > Here is the example: > >>>>>>>> > dba-tlv-x6y64k% cat pg_hba.conf > # TYPE DATABASE USER CIDR-ADDRESS METHOD > local all all trust > host all all 0.0.0.0/0 > <https://urldefense.com/v3/__http:/0.0.0.0/0__;!!PEZBYkTc!e_x_LCIABYSpqVum5S6Hr0TtEs6P4NaumHqEqyXEa3E... scram-sha-256 > > dba-tlv-x6y64k% pg_ctl reload > server signaled > dba-tlv-x6y64k% psql -Upostgres > Password for user postgres: > psql (17.4) > Type "help" for help. > > ctrlmdb=# > >>>>>>> > PSQL should not have asked for the password. > Thanks > Danny > > Suggests there are environment variables coming into play making > non-default choices for you. Namely, making you not use local as the > connection method. > > David J. > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 20:59 Adrian Klaver <[email protected]> parent: Abraham, Danny <[email protected]> 1 sibling, 1 reply; 13+ messages in thread From: Adrian Klaver @ 2025-04-09 20:59 UTC (permalink / raw) To: Abraham, Danny <[email protected]>; David G. Johnston <[email protected]>; Francisco Olarte <[email protected]>; [email protected] <[email protected]> On 4/9/25 13:40, Abraham, Danny wrote: > Thanks again. > 4. I am not aware of an env variable that changes the top down matching > on pg_hba.conf Should have added to previous post: From here: https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT a) Set log_connections and log_disconnections to on if they are not already and reload the server conf. b) Then look at Postgres log to see what the connection settings are for the connections in question. > > Danny > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
* RE: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) @ 2025-04-09 21:53 Abraham, Danny <[email protected]> parent: Adrian Klaver <[email protected]> 0 siblings, 0 replies; 13+ messages in thread From: Abraham, Danny @ 2025-04-09 21:53 UTC (permalink / raw) To: Adrian Klaver <[email protected]>; David G. Johnston <[email protected]>; Francisco Olarte <[email protected]>; [email protected] <[email protected]>; +Cc: Abraham, Danny <[email protected]> Thanks a lot. As you mentioned , I have not cleared the environment vars prior to the call. ==> dba-tlv-x6y64k% cat d2 unsetenv PGPORT unsetenv PGSYSCONFDIR unsetenv PGUSER unsetenv PGDATABASE unsetenv PGSERVICE unsetenv PGHOST psql -Upostgres -p5548 -dpostgres dba-tlv-x6y64k% source d2 psql (17.4) Type "help" for help. postgres=# \q ==> -----Original Message----- From: Adrian Klaver <[email protected]> Sent: Thursday, April 10, 2025 12:00 AM To: Abraham, Danny <[email protected]>; David G. Johnston <[email protected]>; Francisco Olarte <[email protected]>; [email protected] Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) On 4/9/25 13:40, Abraham, Danny wrote: > Thanks again. > 4. I am not aware of an env variable that changes the top down matching > on pg_hba.conf Should have added to previous post: From here: https://urldefense.com/v3/__https://www.postgresql.org/docs/current/runtime-config-logging.html*RUNT... a) Set log_connections and log_disconnections to on if they are not already and reload the server conf. b) Then look at Postgres log to see what the connection settings are for the connections in question. > > Danny > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2025-04-09 21:53 UTC | newest] Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-04-09 17:03 Re: Cannot connect local with ttrust (pg_upgrade assumes it) Francisco Olarte <[email protected]> 2025-04-09 17:44 ` Abraham, Danny <[email protected]> 2025-04-09 17:47 ` Adrian Klaver <[email protected]> 2025-04-09 17:45 ` Abraham, Danny <[email protected]> 2025-04-09 17:49 ` Adrian Klaver <[email protected]> 2025-04-09 19:21 ` Abraham, Danny <[email protected]> 2025-04-09 19:23 ` Abraham, Danny <[email protected]> 2025-04-09 19:31 ` Adrian Klaver <[email protected]> 2025-04-09 19:34 ` David G. Johnston <[email protected]> 2025-04-09 20:40 ` Abraham, Danny <[email protected]> 2025-04-09 20:45 ` Adrian Klaver <[email protected]> 2025-04-09 20:59 ` Adrian Klaver <[email protected]> 2025-04-09 21:53 ` Abraham, Danny <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox