user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/4] imap: reduce impact of bot scanners
Date: Mon,  8 Aug 2022 23:16:44 +0000	[thread overview]
Message-ID: <20220808231648.1954885-1-e@80x24.org> (raw)

There seems to be a fair amount of bot traffic scanning the
IMAP(S) port on public-inbox.org using username+password logins
(which we currently accept combination of).

AUTH=ANONYMOUS traffic is probably more likely to be legit,
and supported by mutt and lei, at least.

To avoid breaking things for legitimate users using
username+passwords, I've decided to deprioritize, but
still allow traffic of clients using username+password
logins.

The initial prefix change is good regardless, since
even legitimate AUTH=ANONYMOUS clients could've caused
fairness problems with the aggressive pipelining to
git-cat-file||Gcf2.

Eric Wong (4):
  imap: limit ibx_async_prefetch to idle git processes
  imap: only give AUTH=ANONYMOUS clients prefetch
  imap: prioritize AUTH=ANONYMOUS clients
  README: recommend AUTH=ANONYMOUS on IMAP URLs

 README                         |  6 +++---
 lib/PublicInbox/DS.pm          |  2 +-
 lib/PublicInbox/GitAsyncCat.pm |  9 ++++-----
 lib/PublicInbox/IMAP.pm        | 16 +++++++++++++---
 lib/PublicInbox/IMAPD.pm       |  7 +++++++
 5 files changed, 28 insertions(+), 12 deletions(-)

             reply	other threads:[~2022-08-08 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 23:16 Eric Wong [this message]
2022-08-08 23:16 ` [PATCH 1/4] imap: limit ibx_async_prefetch to idle git processes Eric Wong
2022-08-08 23:16 ` [PATCH 2/4] imap: only give AUTH=ANONYMOUS clients prefetch Eric Wong
2022-08-08 23:16 ` [PATCH 3/4] imap: prioritize AUTH=ANONYMOUS clients Eric Wong
2022-08-08 23:16 ` [PATCH 4/4] README: recommend AUTH=ANONYMOUS on IMAP URLs Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20220808231648.1954885-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).