Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Sep 2001 01:50:02 -0700 (PDT)
From:      Peter Pentchev <roam@ringlet.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/30571: Error handling by natd causes all communications to cease when ambiguous statement exists in natd.conf making remote administration to fix impossible.
Message-ID:  <200109140850.f8E8o2P22776@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/30571; it has been noted by GNATS.

From: Peter Pentchev <roam@ringlet.net>
To: Bill Daniel <vlaad@baldfewls.net>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/30571: Error handling by natd causes all communications to cease when ambiguous statement exists in natd.conf making remote administration to fix impossible.
Date: Fri, 14 Sep 2001 11:42:28 +0300

 On Fri, Sep 14, 2001 at 01:03:49AM -0700, Bill Daniel wrote:
 > 
 > >Number:         30571
 > >Category:       misc
 > >Synopsis:       Error handling by natd causes all communications to cease when ambiguous statement exists in natd.conf making remote administration to fix impossible.
 > >Originator:     Bill Daniel
 > >Release:        4.4-RC
 > >Organization:
 > Texas Metropolitan Services
 > >Environment:
 > FreeBSD firewall.cargoven.com 4.4-RC FreeBSD 4.4-RC #0: Fri Sep 14 01:02:23 CDT
 > 2001     root@firewall.cargoven.com:/usr/src/sys/compile/cargoven  i386
 > >Description:
 > I made a typo in the natd.conf... the obvious solution is to not make typos in natd.conf... however..
 > The error caused all communications to the unit to cease.. i couldn't get to it internally (via a local user) or externally... 
 [snip]
 > >Fix:
 > My suggestion would be to either abort loading natd on ambiguous statements in the .conf file or to simply ignore the ambiguous statement.
 > 
 > My preference, being security minded, would be to simply abort loading the natd at all when an ambiguous statement is found. and hopefully this would make a *lot* of "noise" via syslog :)
 
 How about another solution - have natd(8) grow an Apache-like 'configtest'
 mode, so it only parses the config file without actually doing anything?
 
 G'luck,
 Peter
 
 -- 
 When you are not looking at it, this sentence is in Spanish.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109140850.f8E8o2P22776>