From: Junio C Hamano <gitster@pobox•com>
To: "Lasse Kliemann" <lasse-gmane-git-2009@mail•plastictree.net>
Cc: git@vger•kernel.org
Subject: Re: Manipulating existing revisions by push or pull?
Date: Mon, 16 Nov 2009 13:53:19 -0800 [thread overview]
Message-ID: <7vd43innlc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <hdshcm$c06$1@ger.gmane.org> (Lasse Kliemann's message of "Mon\, 16 Nov 2009 21\:49\:10 +0000 \(UTC\)")
"Lasse Kliemann" <lasse-gmane-git-2009@mail•plastictree.net> writes:
> Put a different way: consider there is a hostile entity from
> which I pull or which I allow to push to me. Can this entity
> fiddle with my history? Can it change the data in existing
> revisions in my repository? Or can it only make new revisions
> grow on my side?
If you allow your ref to get updated to an arbitrary value, you are lost,
unless you have signed tags that anchor things in place, in which case you
can trust the part of history that is reachable from them.
prev parent reply other threads:[~2009-11-16 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 21:49 Manipulating existing revisions by push or pull? Lasse Kliemann
2009-11-16 21:53 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vd43innlc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=lasse-gmane-git-2009@mail$(echo .)plastictree.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox