On Wed, 2008-09-17 at 14:02 -0700, Hongwei Sun wrote:
> Andrew,
>
> After running Samba RPC-PAC test, analyzing network trace and
> reviewing its source code, we think that we found the problem in the
> Sambatorture implementation. In the loop of setting message type
> from 0x00 to 0xFF, the
Andrew,
After running Samba RPC-PAC test, analyzing network trace and reviewing its
source code, we think that we found the problem in the Sambatorture
implementation. In the loop of setting message type from 0x00 to 0xFF, the
test program sends the exactly same PAC_Validate buffer for ea
On Mon, 2008-09-08 at 12:44 -0700, Hongwei Sun wrote:
> Andrew,
>
>
>
> We ran Smbtortue RPC-PAC testing on windows 2008 DC and got the
> following output.
>
>
>
> [EMAIL PROTECTED] source]# bin/smbtorture -k yes //VM-W2K8.nick.com/public
> RPC-PAC Using seed 1220896649 Running PAC Pas
Andrew,
We ran Smbtortue RPC-PAC testing on windows 2008 DC and got the following
output.
[EMAIL PROTECTED] source]# bin/smbtorture -k yes //VM-W2K8.nick.com/public
RPC-PAC Using seed 1220896649 Running PAC Password for [NICKDOM\root]:
Domain join failed - Connection to SAMR pipe of DC
On Sun, 2008-09-07 at 17:01 -0700, Hongwei Sun wrote:
> Andrew,
>
>I went through the logic of the generic pass through function in
> Kerberos package for both Windows server 2003 and 2008. I found that
> it only processes KerbVerifyPacMessage (0x03). For any other message
> types, STATUS_AC
Andrew,
I went through the logic of the generic pass through function in Kerberos
package for both Windows server 2003 and 2008. I found that it only processes
KerbVerifyPacMessage (0x03). For any other message types, STATUS_ACCESS_DENIED
should be returned.
Could you give me more info
Good morning Andrew. Thank you for your question! I have created a new case for
this (info below); one of my colleagues will take ownership of this and contact
you soon.
SRX080903600015 [MS-APDS] 2.2.2.1 valid Kerberos message types
Regards,
Bill Wesse
MCSE / Escalation Engineer, US-CSS DSC PRO
