netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [MAINTENANCE] Shutting down FTP services at netfilter.org
Date: Wed, 3 Jun 2020 23:32:35 +0200	[thread overview]
Message-ID: <20200603213235.GA31552@salvia> (raw)
In-Reply-To: <20200603171621.GC717800@nataraja>

Hi Harald,

On Wed, Jun 03, 2020 at 07:16:21PM +0200, Harald Welte wrote:
> Hi Pablo,
> 
> On Wed, Jun 03, 2020 at 01:37:12PM +0200, Pablo Neira Ayuso wrote:
> > So netfilter.org will also be shutting down FTP services by
> > June 12th 2020.
> 
> I always find that somewhat sad, as with HTTP there is no real convenient
> way to get directory listings in a standardized / parseable format.  But
> of course I understand the rationale and I obviously respect your
> decision in that matter.

There was a discussion regarding the existing netfilter.org
infrastructure during the last workshop. People are busy and the
infrastructure maintainance tasks end up being the last thing on the
list at the end of the day, unfortunately. Luckly, there is one more
person volunteering to help maintain the netfilter.org infrastructure
these days. Still I have to scratch my limited spare time to migrate
the infrastructure to the new datacenter.

> > As an alternative, you can still reach the entire netfilter.org
> > software repository through HTTP at this new location:
> > 
> >         https://netfilter.org/pub/
> 
> Maybe make http://ftp.netfilter.org/ an alias to it?

It's just one extra file in apache and an entry on the DNS server.
Yes, I can do that. It's probably convenient to keep this at least
working for a while.

I cannot hide, however, that I would like to simplify the existing
infrastructure to reduce the maintainance burden to adecuate it to the
existing resource availability. Including the consolidation of the
existing virtual servers in apache around one or two instances.

> I think the important part would be some way to conveniently obtain a
> full clone, e.g. by rsync.  This way both public and private mirrors
> can exist in an efficient way, without having to resort to 'wget -r'
> or related hacks, which then only use file size as an indication if a
> file might have changed, ...

Regarding rsync: I'm actually considering to propose to remove
netfilter mirrors or, alternatively, only propose to maintain a number
of them that have worked reliably along these years. So rsync would be
only available for those few people that will be maintaining mirrors.

Regards.

      parent reply	other threads:[~2020-06-03 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 11:37 [MAINTENANCE] Shutting down FTP services at netfilter.org Pablo Neira Ayuso
2020-06-03 17:16 ` Harald Welte
2020-06-03 18:10   ` Jan Engelhardt
2020-06-23  2:37     ` Trent W. Buck
2020-06-03 21:32   ` Pablo Neira Ayuso [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=20200603213235.GA31552@salvia \
    --to=pablo@netfilter.org \
    --cc=laforge@gnumonks.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.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 NNTP newsgroup(s).