On Wed, Feb 16 2022 at 19:58:27 -0600, Matt Zagrabelny scribbled
in "Re: unexpected failure for GSS Pg server":
> On Tue, Feb 8, 2022 at 5:03 PM Dameon Wagner
> wrote:
>
> >
> > Armed with that information, the most likely solution would be to
> > extract a
On Tue, Feb 8, 2022 at 5:03 PM Dameon Wagner
wrote:
>
> Armed with that information, the most likely solution would be to
> extract a fresh keytab (using either the kadmin "ktadd" subcommand, or
> the handy `k5srvutil` command).
>
Thanks for the detailed instructions, Dameon!
Do you know why pe
On Tue, Feb 08 2022 at 12:28:21 -0600, Matt Zagrabelny via Kerberos scribbled
in "Re: unexpected failure for GSS Pg server":
> On Tue, Feb 8, 2022 at 11:54 AM Matt Zagrabelny wrote:
>
> > Greetings,
> >
> > I'm experiencing a failure between a GSS enabled
On Tue, Feb 8, 2022 at 11:54 AM Matt Zagrabelny wrote:
> Greetings,
>
> I'm experiencing a failure between a GSS enabled Postgresql server and my
> CLI client.
>
> To my knowledge nothing has changed on the system to create this failure.
> I did modify some puppet configs, but according to the pu
Greetings,
I'm experiencing a failure between a GSS enabled Postgresql server and my
CLI client.
To my knowledge nothing has changed on the system to create this failure. I
did modify some puppet configs, but according to the puppet log output (and
stat'ing /etc/postgresql-common/krb5.keytab) fil
