Re: What's cooking in git.git (Jan 2022, #07; Mon, 24)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 4, 2022, 00:27 UTC
Message-ID: <xmqqiltvpjc7.fsf@gitster.g>
In-Reply-To: <YfRu0G9aNQxT3vtl@camp.crustytoothpaste.net>

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

Show 13 quoted lines

>> * bc/csprng-mktemps (2022-01-17) 2 commits
>>  - wrapper: use a CSPRNG to generate random file names
>>  - wrapper: add a helper to generate numbers from a CSPRNG
>> 
>>  Pick a better random number generator and use it when we prepare
>>  temporary filenames.
>> 
>>  Are we solving the right problem?
>>  cf. <220118.86zgntpegy.gmgdl@evledraar.gmail.com>
>>  source: <20220117215617.843190-1-sandals@crustytoothpaste.net>
>
> It sounds like folks would prefer we drop this series.  I'm not planning
> to send an alternate approach here.

I personally am OK with these two patches, by the way. There was an interesting thought experiment to see if we can only rely on mkstemp() and mkdtemp() that we assume are already secure enough, but swapping the not-particularly-good linear conguential generator used in git_mkstemps_mode() with a better algorithm that is externally supported, making the security issue somebody else's problem, is a good incremental improvement, I would think.

Unless I hear differently from others, I am planning to mark the topic for 'next' in my draft of the "What's cooking" report.

Thanks.