Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #4952
| From | Clark Smith <noaddress@nowhere.net> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: Filtering incoming SSH connections |
| Date | 2021-09-08 21:09 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <shb8pg$e8o$1@gioia.aioe.org> (permalink) |
| References | <sh8qvt$1lgf$1@gioia.aioe.org> <sh8rgb$3qm$1@dont-email.me> <sh93qh$u7e$1@tncsrv09.home.tnetconsulting.net> <shai2o$15pb$1@gioia.aioe.org> <shaopt$p48$1@tncsrv09.home.tnetconsulting.net> |
On Wed, 08 Sep 2021 10:32:44 -0600, Grant Taylor wrote: > You can't use the IP address of a road warrior machine, and MAC > addresses are implicitly only available on the LAN. > > Please clarify if you are trying to reduce log noise from IBR or if you > are just trying to make sure that the client machine in question can > authenticate and log in (presuming no intermediate filtering). A mix of both, I guess. In the extreme I case, I would like to guarantee that my roaming device can always ssh into my server, no matter where the former is attempting to do so from. In a more realistic setting, I am OK letting other people try, as long as they are not trying to brute-force their way into my system, in which case I would block them completely. This latter aspect is already covered - the sticking issue is to make sure that my roaming device can always make it. I am not inclined to use a non-standard port, pretty much for the reasons you mentioned. I am also not so keen on a VPN, for it is a bit painful to set up and manage. Plus, it is slower.
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Filtering incoming SSH connections Clark Smith <noaddress@nowhere.net> - 2021-09-07 23:01 +0000
Re: Filtering incoming SSH connections Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2021-09-07 23:10 +0000
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-07 19:28 -0600
Re: Filtering incoming SSH connections Clark Smith <noaddress@nowhere.net> - 2021-09-08 14:41 +0000
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-08 10:32 -0600
Re: Filtering incoming SSH connections Clark Smith <noaddress@nowhere.net> - 2021-09-08 21:09 +0000
Re: Filtering incoming SSH connections "Carlos E. R." <robin_listas@es.invalid> - 2021-09-08 23:50 +0200
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-08 23:19 -0600
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-09 05:19 +0000
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-09 12:09 -0600
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-11 01:16 +0000
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-11 01:21 +0000
Re: Filtering incoming SSH connections Aragorn <thorongil@telenet.be> - 2021-09-11 05:49 +0200
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-11 19:26 +0000
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-10 23:55 -0600
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-11 19:28 +0000
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-11 15:36 -0600
Re: Filtering incoming SSH connections Grant Taylor <gtaylor@tnetconsulting.net> - 2021-09-07 19:22 -0600
Re: Filtering incoming SSH connections Richard Kettlewell <invalid@invalid.invalid> - 2021-09-08 08:49 +0100
Re: Filtering incoming SSH connections William Unruh <unruh@invalid.ca> - 2021-09-09 05:16 +0000
csiph-web