On 02/02/16 18:56, Peter Palfrader wrote:
> On Tue, 02 Feb 2016, Nick Mathewson wrote:
>
>> The tl;dr here is:
>>* By default Git doesn't verify the sha1 checksums it receives by default.
>>* It doesn't look like we've got any inconsistencies in our
>> repositories I use, though. That's
> I suspect that setting things globally (in your ~/.gitconfig)
> git config --global --add transfer.fsckobjects true
> git config --global --add fetch.fsckobjects true
> git config --global --add receive.fsckobjects true
> might also work. (However, I haven't verified it.)
You only
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813157 for more
information why.
The tl;dr here is:
* By default Git doesn't verify the sha1 checksums it receives by default.
* It doesn't look like we've got any inconsistencies in our
repositories I use, though. That's good!
* To
On Tue, 02 Feb 2016, Nick Mathewson wrote:
> The tl;dr here is:
>* By default Git doesn't verify the sha1 checksums it receives by default.
>* It doesn't look like we've got any inconsistencies in our
> repositories I use, though. That's good!
>* To turn on verification, I think you
