samba - Dec 2019 - Failed to find [principal](kvno 4) in keytab MEMORY:cifs_srv_keytab (arcfour-hmac-md5)]

Yes, I am planning on upgrading the FreeNAS which will include a newer
version of samba.
However, I'm quite confident that this is not a duplicate of #12262.

To be clear: I'm offering to leave my production system in a degraded
state to help myself and the Samba developers understand exactly
what's going on here, to determine if this is a new bug, or an
existing one. I'm worried that upgrading will make the problem "go
away" but not actually be resolved.

I mainly don't understand how two clients can be presenting tickets
for the exact same principal (and kvno), but Samba says that one of
them can't be found, but the other is acceptable.


On Mon, Dec 16, 2019 at 3:46 PM Rowland penny via samba
<samba at lists.samba.org> wrote:
> > I have a FreeNAS server (9.10 running samba 4.3.11-GIT-UNKNOWN)
that's recently
> > started emitting this error:
> >
> If you are running Samba 4.3.11 then you should be aware that it is EOL
> and bug 12262 was fixed in 4.4, so I would suggest you upgrade to a
> supported Samba version. You will probably find that your problem is
> fixed, but if it isn't, you will at least stand a chance of getting it
> fixed, you have little or no chance of getting 4.3.11 fixed.
>
> Rowland

On 18/12/2019 14:05, Jonathon Reinhart wrote:
> Yes, I am planning on upgrading the FreeNAS which will include a newer
> version of samba.
> However, I'm quite confident that this is not a duplicate of #12262.
>
> To be clear: I'm offering to leave my production system in a degraded
> state to help myself and the Samba developers understand exactly
> what's going on here, to determine if this is a new bug, or an
> existing one. I'm worried that upgrading will make the problem "go
> away" but not actually be resolved.
>
> I mainly don't understand how two clients can be presenting tickets
> for the exact same principal (and kvno), but Samba says that one of
> them can't be found, but the other is acceptable.
Problem is, and as I said, Samba? 4.3.x is EOL as far as Samba is 
concerned and if you have found a bug in it, it is very, very unlikely 
to get fixed, unless it is still in a later, supported, Samba version.

Rowland

On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba <
samba at lists.samba.org> wrote:
> Problem is, and as I said, Samba  4.3.x is EOL as far as Samba is
> concerned and if you have found a bug in it, it is very, very unlikely
> to get fixed, unless it is still in a later, supported, Samba version.
>
Of course; I wouldn't expect any more patches for 4.3.x. I've dug
through a
lot of the code and most of it is identical to latest master. So to word it
another way: I'm trying to see if this is a known bug that has been fixed
since 4.3.x, or if this instance is highlighting a new unknown bug that
could still exist in master.

I understand your role on the list is a first line of response; keeper of
the gates sort of thing. Is there a more appropriate channel where I can
get some input from developers familiar with this part of the code?