Bug #11107

Apply transfer.fsckobjects true to our default Git config

Added by sajolida over 1 year ago. Updated over 1 year ago.

Status:ResolvedStart date:02/12/2016
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:Tails_2.2
QA Check:Pass Blueprint:
Feature Branch: Easy:
Type of work:Code Affected tool:

Description

See:

Proposed but untested patch:

--- a/config/chroot_local-includes/etc/gitconfig
+++ b/config/chroot_local-includes/etc/gitconfig
@@ -1,2 +1,4 @@
 [color]
        ui = auto
+[transfer]
+       fsckObjects = true

Associated revisions

Revision 73d7b643
Added by anonym over 1 year ago

Make Git verify the integrity of transferred object.

Short story: Git will happily fetch a corrupt (or even maliciously
manipulated) tree unless transfer.fsckObjects is set.

Long story: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813157

Fix-committed: #11107

History

#1 Updated by sajolida over 1 year ago

  • Assignee set to anonym
  • Target version set to Tails_2.2
  • QA Check set to Ready for QA

I'm not sure this qualifies as "Ready for QA" but I'll let the RM decide on the priority of this.

#2 Updated by anonym over 1 year ago

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100

#3 Updated by anonym over 1 year ago

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

I've been using this personally for a month, and it seems to work in Tails too. Applied, tanks!

#4 Updated by anonym over 1 year ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF