Re: [MMUSIC] 4572 update: forbid weak hashes?

[Roman Shpount <[e-mail]>]

On Thu, Apr 7, 2016 at 3:27 PM, Paul Kyzivat <[e-mail]> wrote:

> On 4/7/16 3:08 PM, Roman Shpount wrote:
>
>> There is no reason to sort. This will not make hash check any more
>>
> secure. If a hash you consider secure is compromised you will just get
>> false positive slightly later. There is probably a reason to sort hashes
>> based on the amount of resources it will take for you to check them,
>> with easiest to check first  in order to optimize the hash checking
>> process. This will likely sort the hashes weakest first.
>>
>
> If everybody did this, and the easiest to check one is compromised, and
> used by a MiTH to inject a bogus cert that matches that nobody might
> notice. Isn't that undesirable?
>

This is why you should discard hashes that you consider too weak. After you
done this, since any single hash match is sufficient, it does not matter in
what order the hashes are checked. If the weak hash is present, the session
will be accepted.
_____________
Roman Shpount