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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom,
On 27/01/16 20:02, Tom Ritter wrote:
> [feel free to reply adding tor-project or whomever]
Sure, let me copy tor-dev@.
> Remember a while ago I lamented that I wished there was some
> monitoring service that could tell me when my metrics
Nick Mathewson transcribed 1.3K bytes:
> First, the next meeting is scheduled on #tor-dev this Thursday, at
> 9:00 am EST (=1400 UTC). We'll be discussing these proposals:
>* Proposal 263: Postquantum circuit extension
>* Proposal 249: Large create cells
I'll be there, and I'm trying to
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
