From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] open ports on WAN
Date: Sat, 19 Apr 2014 10:52:28 -0700 [thread overview]
Message-ID: <CAA93jw5SMBTPpvdMShLo0JbPY746sdRruo=2iazkb+rQL+vEiA@mail.gmail.com> (raw)
In-Reply-To: <20140419163638.GX16334@angus.ind.WPI.EDU>
On Sat, Apr 19, 2014 at 9:36 AM, Chuck Anderson <cra@wpi.edu> wrote:
> I was curious to see what services were open on the WAN to the CeroWrt
> router itself. It looks like the following services are open and not
> firewalled via iptables directly:
>
> 21 telnet
> 22 ssh
> 23 ftp
> 873 rsync
> 12865 netserver
>
> The only thing blocking access is the xinetd configuration:
>
> defaults
> {
> per_source = 16
> only_from = 192.168.0.0/16 172.16.0.0/12
> instances = 18
> max_load = 16
> }
> Is this a good idea, relying only on this default config to block
> access to those services? Or should the iptables firewall default to
> blocking everything and only poke holes where they are needed rather
> than how it is now--only blocking a list of ports which doesn't
> include the above ports?
telnet and ftp are actually sensors that detect probe attempts and
block off attempts to access any other services from the offending
IP.
I like the sensor capability, and wish it could trigger adding firewall
rules as well.
Rsync has no conf file by default, and ssh and netserver are limited by
default to the common internal IP addresses.
You can tighten these down further if you like.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
prev parent reply other threads:[~2014-04-19 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 16:36 Chuck Anderson
2014-04-19 17:52 ` Dave Taht [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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5SMBTPpvdMShLo0JbPY746sdRruo=2iazkb+rQL+vEiA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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