[ntpwg] [ntp:hackers] MS-SNTP

[Luke Howard]

Dave,

The RID is not hashed, it's an integer that is roughly analogous to a  
UID or GID on POSIX systems. In an NTP packet, it is encoded in the  
incorrect byte order.

The size of the RID space depends on the number of users in a domain;  
the first RID is typically 500, as Andrew points out.

It appears that the most significant bit is used to select between the  
current and prior shared secret (although I wasn't aware of this when  
I built Novell's implementation).

regards,

-- Luke

On 30/03/2008, at 4:50 AM, David L. Mills wrote:
> Luke,
>
> Can you confirm that the RID is hashed and that the hash can take up  
> to
> 31 bits?
>
> Dave
>
> Luke Howard wrote:
>
>>
>> On 29/03/2008, at 5:43 AM, David L. Mills wrote:
>>
>>> Luke,
>>>
>>> Note the pivot partions on the basis of value, not assigned bit   
>>> fields.
>>> This is done specificatlly to give Autokey a large fraction of the
>>> space. Walling of the space seperately by fields would defeat that
>>> purpose.
>>>
>>> I don't understand your comment about zero and endian. A little  
>>> endian
>>> zero is identical to a big endian zero.
>>
>>
>>
>> My bad. Let me rephrase: Microsoft's encoding of RIDs as key IDs is
>> in  the incorrect byte order.
>>
>> I can confirm this from my experience building an implementation of
>> this.
>>
>> -- Luke
>
>
> _______________________________________________
> hackers mailing list
> hackers at lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/hackers
>

--
www.padl.com | www.fghr.net