Success!
I was able to decrypt an extracted key. Here are some quick notes, which
may be useful to those writing the documentation on key extraction.
- The block size, as you (Edgar) noted, is 16 bytes. As it turns out,
this is the *standard* block size for AES CBC. AES, however, is
der
Thanks, Edgar.
That's another critical piece of information. I will keep working with this.
Chris -)-
Edgar Olougouna wrote:
> Hi Chris,
>
> Just a quick follow-up, the block size is 16.
>
> Thanks,
> Edgar
--
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba T
Hi Chris,
Just a quick follow-up, the block size is 16.
Thanks,
Edgar
___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
Hi Stefan, thank you for your question. A member of the protocol documentation
team will be in touch with you soon.
Josh Curry
Escalation Engineer
469.775.7215
Exceeding your expectations is my highest priority. If you would like to
provide feedback on your case you may contact my manager at
On Tue, Jul 5, 2011 at 12:01 AM, Moh Yen Liew wrote:
> Hi Mike:
> According to MS-NRPC pg 111, bit 17 (indicated as bit R) of negotiable
> flag is actually referring to "supports the NetrServerPasswordSet2
> functionality".
Page numbers are probably not going to line up well and I think yo
Hi!
Thanks, that describes it so far. If my testing shows more
irregularities, I'll inform you. Please close the case.
Thanks a lot,
Volker
On Fri, Jul 01, 2011 at 07:46:41PM +, Obaid Farooqi wrote:
> Hi Volker:
>
> We have completed our investigation regarding your inquiry on WRITE_DAC
>
Hi,
can you please document the behavior that is triggered by the following
parameter.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Netlogon\Parameters]
"AllowNT4Crypto"=dword:0001
I can't find this in MS-NRPC.
Is there any interaction with the RequireStrongKey parameter?
Thanks!
metze
