All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven M Campbell <Netfilter@SCampbell.net>
To: netfilter@lists.netfilter.org
Subject: Re: Dynamic DNS
Date: Wed, 09 Mar 2005 15:58:14 -0500	[thread overview]
Message-ID: <422F6366.5000500@SCampbell.net> (raw)
In-Reply-To: <422F5F90.6080005@SCampbell.net>

Steven M Campbell wrote:

> Sebastian Docktor wrote:
>
>> Hi,
>>
>> I want to allow a Dynamic DNS Client to Access the SSH-Server on my 
>> Firewall. But I don't want to open SSH for all IPs,
>> Is it possible that iptables always looks up the ip address from the 
>> hostname, so that only the ip has access which is registrated under
>> the dyndns?
>>
>>
>>
>
> IMO, it's a very bad idea to lower the security of iptables firewall 
> by making it dependent on DNS for any portion of authorization 
> certification. DNS isn't exactly known for it's stellar security :) 
> Allow me to suggest an alternate path. Use RSA keyfiles and disallow 
> ssh password authentication, this way you can leave the port open but 
> user's without public keys installed on the server cannot gain access. 
> Generally speaking DNS should have nothing to do with anyone's 
> firewall because DNS would then become the weak link in the security 
> chain and SSH has methods that are better applied to these needs.
>
>
A quick look at the sshd_config man pages reveals

AllowUsers
This keyword can be followed by a list of user name patterns, separated 
by spaces. If specified, login is
allowed only for user names that match one of the patterns. ‘*’ and ‘?’ 
can be used as wildcards in the pat‐
terns. Only user names are valid; a numerical user ID is not recognized. 
By default, login is allowed for
all users. If the pattern takes the form USER@HOST then USER and HOST 
are separately checked, restricting
logins to particular users from particular hosts.

Sorry for straying off the topic folks, I think you might care to take 
this route.


  reply	other threads:[~2005-03-09 20:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  6:25 Dynamic DNS Sebastian Docktor
2005-03-09  6:29 ` Brent Clark
2005-03-09  8:04   ` Kenneth Kalmer
2005-03-09 22:35     ` R. DuFresne
2005-03-09  9:07 ` Jose Maria Lopez Hernandez
2005-03-09 10:35   ` Nick Drage
2005-03-09 11:03     ` Jose Maria Lopez Hernandez
2005-03-13 16:28     ` Sebastian Docktor
2005-03-09 15:17 ` Maxime Ducharme
2005-03-09 15:26   ` Maxime Ducharme
2005-03-09 19:34   ` Jason Opperisano
2005-03-09 20:33     ` Maxime Ducharme
2005-03-09 20:41 ` Steven M Campbell
2005-03-09 20:58   ` Steven M Campbell [this message]
2005-03-09 22:51   ` R. DuFresne
     [not found]     ` <42304A9A.7050207@SCampbell.net>
     [not found]       ` <Pine.LNX.4.60.0503102052440.16999@darkstar.sysinfo.com>
2005-03-12 15:25         ` Steven M Campbell
  -- strict thread matches above, loose matches on Subject: below --
2005-03-09  8:53 Sietse van Zanen

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=422F6366.5000500@SCampbell.net \
    --to=netfilter@scampbell.net \
    --cc=netfilter@lists.netfilter.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.