From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] banishment of nuisance IP addresses
Date: Tue, 29 Oct 2019 11:26:50 +0000 [thread overview]
Message-ID: <093e2b63a02b86b45ad0ac0e4d0522e6@quintile.net> (raw)
In-Reply-To: <BD84209928A92906C06BFE2A8B44F315@felloff.net>
re: anyone can banish ano IP address
You are quite right, not a problem for me, but not a general solution.
Ok, chmod og-w /lib/ndb/banished first.
I could then write a file server, envoked in cpurc as bootes and thus
has rights to update the files in /lib/ndb/banished/*.
The file server would have to ensure its /srv/xxx file is not accessable
by others.
This could be mounted by the network listners before they becomenone() so
they retain access. They would also need to ensure they unmount
the writable access to the banishment directory before starting their
child process (if the incomming connection is successful).
ugh. Even _if_ that would work its a real pain.
oh well, nice idea, but no bananna.
-Steve
next prev parent reply other threads:[~2019-10-29 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 10:51 cinap_lenrek
2019-10-29 11:26 ` Steve Simon [this message]
2019-11-05 10:02 ` Sergey Zhilkin
2019-11-05 10:05 ` Steve Simon
2019-11-05 16:28 ` Sergey Zhilkin
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 9:13 Steve Simon
2019-10-29 9:56 ` [9fans] " hiro
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=093e2b63a02b86b45ad0ac0e4d0522e6@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).