unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barry.margolin@level3.com>
Subject: Re: What's the problem with the authenticity of 21.3?
Date: Wed, 13 Aug 2003 22:02:25 GMT	[thread overview]
Message-ID: <Rzy_a.72$mD.7@news.level3.com> (raw)
In-Reply-To: e1schb.r5.ln@acm.acm

In article <e1schb.r5.ln@acm.acm>, Alan Mackenzie <none@example.invalid> wrote:
>Hi everybody.
>
>I was looking at the gnu ftp server and one of its mirrors last night,
>with a view to downloading 21.3, (or at least, a patch to upgrade to it).
>
>Instead of this, I could find only the file
>emacs-21.3.tar.gz.back-RSN.README which contained a massive list of files
>(about 690) which are currently unavailable "because their authenticity
>is being confirmed.  We expect to have them uploaded Real Soon Now
>(RSN)."
>
>Can anybody throw any light upon what's going on?

I just saw a CERT Advisory that said that root on ftp.gnu.org has been
compromised since March.  They've presumably been going through all the
software on it and verifying that it hasn't been corrupted by the cracker.

-- 
Barry Margolin, barry.margolin@level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

  reply	other threads:[~2003-08-13 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  8:14 What's the problem with the authenticity of 21.3? Alan Mackenzie
2003-08-13 22:02 ` Barry Margolin [this message]
2003-08-15 20:50 ` Jose A. Ortega Ruiz

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='Rzy_a.72$mD.7@news.level3.com' \
    --to=barry.margolin@level3.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 read-only IMAP folder(s) and NNTP newsgroup(s).