Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-07-25 Thread Tris Mabbs
4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest). So it seems that with these changes, kerberos_decode_pac() is never entered with client_principal anything other than a NULL

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-15 Thread Tris Mabbs
So it seems that with these changes, kerberos_decode_pac() is never entered with client_principal anything other than a NULL pointer. So I'm (very) happy that these changes fix my problem. However it does seem a little curious that client_principal now never appears to be set - I

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-14 Thread Andrew Bartlett
On Fri, 2013-03-08 at 17:20 +, Tris Mabbs wrote: Hello again everyone, On 08 March 2013 13:10, Michael Wood wrote: ... ---Cut here. Sorry, I forgot a step. You would have needed a git fetch gd in there before the checkout. Ah ha! That would explain it then. Well,

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-08 Thread Tris Mabbs
Message- From: Guenther Deschner Sent: 28 February 2013 15:09 To: Tris Mabbs Cc: samba@lists.samba.org Subject: Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest). Hi

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-08 Thread Michael Wood
: RE: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest). Hiya again Günther, I'm *really* sorry - I must be being completely dense but I can't actually find that branch

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-08 Thread Tris Mabbs
Message- From: Michael Wood Sent: 08 March 2013 10:33 To: Tris Mabbs Cc: Guenther Deschner; Andrew Bartlett; samba@lists.samba.org Subject: Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-08 Thread Michael Wood
- From: Michael Wood Sent: 08 March 2013 10:33 To: Tris Mabbs Cc: Guenther Deschner; Andrew Bartlett; samba@lists.samba.org Subject: Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-08 Thread Tris Mabbs
Hello again everyone, On 08 March 2013 13:10, Michael Wood wrote: ... ---Cut here. Sorry, I forgot a step. You would have needed a git fetch gd in there before the checkout. Ah ha! That would explain it then. Well, forgotten command or not, the help was much appreciated and I now have

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-03-07 Thread Andrew Bartlett
On Thu, 2013-02-28 at 22:33 +, Tris Mabbs wrote: Hiya Günther, Absolutely - I'm really sorry, I intended to try this today but haven't had the chance. Hopefully I will get the chance tomorrow, and I'll let you know the results. Many thanks, much appreciated :-) Where did we get

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-28 Thread Guenther Deschner
Hi Triss, can you test this branch? https://git.samba.org/?p=gd/samba/.git;a=shortlog;h=refs/heads/master-krb5pac It contains fixes for various pac buffer types. Let us know if it resolves your issues. Thanks, Guenther -- Günther DeschnerGPG-ID: 8EE11688 Red Hat

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-28 Thread Tris Mabbs
] Sent: 28 February 2013 15:09 To: Tris Mabbs Cc: samba@lists.samba.org Subject: Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest). Hi Triss, can you test this branch

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-27 Thread Tris Mabbs
I do so enjoy working with users who I can ask to 'put some code in' and who can handle this so well :-). Why thank you, kind Sir :-) I do so enjoy working with people who quite obviously really, REALLY, know their subject :-) In my case, evidence only of far too many years stuck in front of a

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-27 Thread Gregory Sloop
I do so enjoy working with users who I can ask to 'put some code in' and who can handle this so well :-). TM Why thank you, kind Sir :-) TM I do so enjoy working with people who quite obviously really, REALLY, know their subject :-) TM In my case, evidence only of far too many years stuck

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-27 Thread Tris Mabbs
I do so enjoy working with users who I can ask to 'put some code in' and who can handle this so well :-). Why thank you, kind Sir :-) I do so enjoy working with people who quite obviously really, REALLY, know their subject :-) In my case, evidence only of far too many years stuck in front of

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-26 Thread Andrew Bartlett
On Mon, 2013-02-25 at 11:51 +, Tris Mabbs wrote: Hello, We're having a problem with Samba 4 joined to a Server 2008 R2 domain (at Server 2008 functional level across the forest). The interesting thing is that this only affects a single user - all other accounts work without

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-26 Thread Tris Mabbs
- From: Andrew Bartlett [mailto:abart...@samba.org] Sent: 26 February 2013 11:05 To: Tris Mabbs Cc: samba@lists.samba.org Subject: Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-26 Thread Andrew Bartlett
On Tue, 2013-02-26 at 11:22 +, Tris Mabbs wrote: Wow. Hiya Andrew, OK, this sounds like a very promising approach, and potentially saves me working through a large number of git bisects (as also most helpfully suggested by Michael Wood) - so far, I'm right back into the beta code

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-26 Thread Tris Mabbs
What I was getting at about the full name is that if this was a odd character encoding issue, knowing that this was a user with non-ascii full name would be an important data point. Yes, I see what you mean. No, neither the full username, nor the login name, contain anything other than

[Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-25 Thread Tris Mabbs
Hello, We're having a problem with Samba 4 joined to a Server 2008 R2 domain (at Server 2008 functional level across the forest). The interesting thing is that this only affects a single user - all other accounts work without problems. When accessing our main server using that account,

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-25 Thread Michael Wood
Hi You might try getting a packet capture. By the way, what's common between the user before you deleted the account and the one you created later, besides the username? The password? Can you replicate this in a test environment? If you can replicate this in a test environment and you know

Re: [Samba] Samba 4 - smbd; can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL error but only for a single domain user (Server 2008 R2 domain, Server 2008 functional level forest).

2013-02-25 Thread Tris Mabbs
Hiya Michael, Many thanks for the quick and helpful response. Yes, I can certainly try a packet capture; I think I'll go with your other suggestion first though, that of using git bisect to track down the problematic version. I'm sorry, that should have occurred to me . Once I've