From: Sitaram Chamarty <sitaramc@gmail.com>
To: gitolite <gitolite@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: [gitolite] (security) problem with deleted or renamed pubkey files
Date: Tue, 20 Apr 2010 19:57:06 +0530 [thread overview]
Message-ID: <o2v2e24e5b91004200727le913dd21lc88603ada9f057fd@mail.gmail.com> (raw)
If you deleted or renamed a pubkey file after 5fd9328 went
in (April 12th), please:
- upgrade asap, then
- go to your latest gitolite-admin clone and "git push -f"
Otherwise this is not urgent and does not affect you.
Please see the latest "master" commit (1e06fea) for more
details.
Sorry about that, and of course feel free to email or holler
at me on #git :)
Sitaram
reply other threads:[~2010-04-20 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=o2v2e24e5b91004200727le913dd21lc88603ada9f057fd@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitolite@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).