public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Subject: Re: Dubious files at ftp://gcc.gnu.org
Date: Mon, 20 Jan 2020 22:51:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.2001202346060.739@anthias.pfeifer.com> (raw)
In-Reply-To: <20191117002401.GA654@cgf.cx>

On Sat, 16 Nov 2019, Christopher Faylor wrote:
>> I noticed two files SysinternalsSuite.zip and mwbytes.exe at the
>> top level of ftp://gcc.gnu.org.  Can/should we remove those?
>> 
>> And how about those .notar files dating back to 1999?  Would it
>> make sense to remove those?
> I'd say yes to all of those.  We probably should be doing a much better
> job of auditing those directories.

I just ran the following:

  % rm ~ftp/SysinternalsSuite.zip
  % rm ~ftp/mwbytes.exe

  % find ~ftp/ -name .notar -exec echo {} \;
  /var/ftp/pub/gcc/releases/gcc-2.95.2.1/.notar
  /var/ftp/etc/.notar
  /var/ftp/lib/.notar
  /var/ftp/bin/.notar
  /var/ftp/usr/.notar

  (And again, replacing "echo" by "rm" ;-)

And also had a look for similarly interesting files, but did not spot
any.

Gerald

      reply	other threads:[~2020-01-20 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 21:56 Gerald Pfeifer
2019-11-17  0:24 ` Christopher Faylor
2020-01-20 22:51   ` Gerald Pfeifer [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=alpine.LSU.2.21.2001202346060.739@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=overseers@gcc.gnu.org \
    /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).