Re: [gentoo-portage-dev] [PATCH] const: Switch default hash set to BLAKE2B+SHA512

[Michał Górny]

Dnia 13 stycznia 2018 11:40:09 CET, Zac Medico <zmedico@g.o> napisał(a):
>On 01/13/2018 12:50 AM, Michał Górny wrote:
>> Switch the Portage defaults to the new Gentoo hash set. We're already
>> far past the initial testing and I have been approached by a few
>people
>> who were surprised that Portage does not use new hashes for overlays.
>> Switching the defaults will remove the need for custom hashes
>> in layout.conf.
>> ---
>>  pym/portage/const.py | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/pym/portage/const.py b/pym/portage/const.py
>> index ec877b841..e5fa4b67c 100644
>> --- a/pym/portage/const.py
>> +++ b/pym/portage/const.py
>> @@ -206,8 +206,8 @@ EAPI                     = 6
>>
>>  HASHING_BLOCKSIZE        = 32768
>>
>> -MANIFEST2_HASH_DEFAULTS = frozenset(["SHA256", "SHA512",
>"WHIRLPOOL"])
>> -MANIFEST2_HASH_DEFAULT  = "SHA512"
>> +MANIFEST2_HASH_DEFAULTS = frozenset(["BLAKE2B", "SHA512"])
>> +MANIFEST2_HASH_DEFAULT  = "BLAKE2B"
>>
>>  MANIFEST2_IDENTIFIERS    = ("AUX", "MISC", "DIST", "EBUILD")
>>
>>
>For repos where layout.conf doesn't set "manifest-required-hashes =
>SHA512", repoman is suddenly going to force all DIST files to be
>fetched
>in order to generate the missing BLAKE2B entries. Is that intended?

Yes. I don't think we need a transition period for overlays.


-- 
Best regards,
Michał Górny (by phone)