From: Sergey Zhilkin <szhilkin@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] banishment of nuisance IP addresses
Date: Tue, 5 Nov 2019 19:28:10 +0300 [thread overview]
Message-ID: <CAOFTvPLTJHP9JgQV6AGRS136DuQCHXA2cQ_yFBpyA_qQUgooZw@mail.gmail.com> (raw)
In-Reply-To: <03D70A3E-99D6-4734-BCC4-109B8BEC1727@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
>no “fw” not sure what that is.
firewall :)
вт, 5 нояб. 2019 г. в 13:06, Steve Simon <steve@quintile.net>:
> no “fw” not sure what that is.
>
> as it happens i turned off ipv6 last night. it was causing problems with
> smtp which i fail to understand, maybe tls certificate, i am not sure.
>
> the banishment code works fine for ipv6
>
> -Steve
>
>
> On 5 Nov 2019, at 10:02 am, Sergey Zhilkin <szhilkin@gmail.com> wrote:
>
>
> I wonder .... if it will be system with IPv6 enabled and connected
> directly to internet.
> There is no fw in plan 9 ....
> May be time to think about it ?
>
> вт, 29 окт. 2019 г. в 14:27, Steve Simon <steve@quintile.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
>>
>> ------------------------------------------
>> 9fans: 9fans
>> Permalink:
>> https://9fans.topicbox.com/groups/9fans/Te00ed62cf5d85d9e-M4d3ca138d4a82de48a303955
>> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>>
>
>
> --
> С наилучшими пожеланиями
> Жилкин Сергей
> With best regards
> Zhilkin Sergey
>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Te00ed62cf5d85d9e-Mf70fb7e29d4e9df88f57dd6e>
>
--
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey
[-- Attachment #2: Type: text/html, Size: 4149 bytes --]
next prev parent reply other threads:[~2019-11-05 16:28 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
2019-11-05 10:02 ` Sergey Zhilkin
2019-11-05 10:05 ` Steve Simon
2019-11-05 16:28 ` Sergey Zhilkin [this message]
-- 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=CAOFTvPLTJHP9JgQV6AGRS136DuQCHXA2cQ_yFBpyA_qQUgooZw@mail.gmail.com \
--to=szhilkin@gmail.com \
--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).