From owner-freebsd-hackers Wed Nov 27 22:27:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08636 for hackers-outgoing; Wed, 27 Nov 1996 22:27:52 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA08625 for ; Wed, 27 Nov 1996 22:27:27 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vSzua-0005ND-00; Wed, 27 Nov 1996 23:25:28 -0700 To: roberto@keltia.freenix.fr (Ollivier Robert) Subject: Re: libc Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 28 Nov 1996 00:41:14 +0100." References: Date: Wed, 27 Nov 1996 23:25:28 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Ollivier Robert writes: : "_" has never been officially allowed in hostnames. Paul Vixie decided to : enforce this in 4.9.4. There is a command you can put in named.boot to : allow them. That's an area open to much debate, much of it due to older RFCs that weren't explicit enough. The valid set of characters in a hostname are [A-Za-z0-9.-] in case someone is curious. The reason that this is now enforced in the name server is that characters outside of these can cause extreme problems for programs that are written to only accept these characters. While allowing _ would likely be no problem, it is outside of the spec. One of these is the famous overflowing the buffer onto the stack to execute code hack... Warner