From: Junio C Hamano <junkio@cox.net>
To: Alexander Litvinov <lan@academsoft.ru>
Cc: git@vger.kernel.org
Subject: Re: Security problem
Date: Thu, 15 Jun 2006 17:12:53 -0700 [thread overview]
Message-ID: <7vbqsuc60q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200606151709.22752.lan@academsoft.ru> (Alexander Litvinov's message of "Thu, 15 Jun 2006 17:09:22 +0700")
Alexander Litvinov <lan@academsoft.ru> writes:
> Why does not git-checkout check if file content match name of the object ?
Good point. We could do a few things:
- entry.c:write_entry() could validate after read_sha1_file().
- read_sha1_file() could do the checking; this has performance
implications, though.
Cloning over git aware protocols validate the objects coming
over the wire, so it may make sense to cheat and do the former,
so that we do not have to pay the validation cost every time we
access any object.
next parent reply other threads:[~2006-06-16 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606151709.22752.lan@academsoft.ru>
2006-06-16 0:12 ` Junio C Hamano [this message]
2006-06-16 2:28 ` Security problem Linus Torvalds
[not found] ` <200606160931.29553.lan@academsoft.ru>
2006-06-16 2:56 ` Linus Torvalds
2006-06-16 3:54 ` Alexander Litvinov
2006-06-16 5:00 ` Linus Torvalds
2006-06-16 5:37 ` Alexander Litvinov
2006-06-16 6:27 ` Linus Torvalds
2006-06-16 8:18 ` Alexander Litvinov
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=7vbqsuc60q.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=lan@academsoft.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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