From owner-freebsd-security Sun Jul 22 20:55: 7 2001 Delivered-To: freebsd-security@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4FD4237B406; Sun, 22 Jul 2001 20:55:03 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6N3stj13517; Sun, 22 Jul 2001 20:54:55 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Jul 2001 20:54:55 -0700 (PDT) From: Matt Dillon Message-Id: <200107230354.f6N3stj13517@earth.backplane.com> To: "Jeroen Massar" Cc: "'Brian Somers'" , "'Hajimu UMEMOTO'" , , , , , Subject: Re: RE: bin/22595: telnetd tricked into using arbitrary peer ip References: <000f01c11315$094851e0$420d640a@HELL> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org All very nice, guys, but not realistic. Only FreeBSD uses an API. Third party programs access the structure directly for the most part so adding new fields to the structure will just cause more garbage to be written to the file (many third party programs don't bother to bzero the structure before writing it out). We aren't going to add a separate hostname[] array... we just got through ripping out the hostname crap, because there was never enough room in the field to actually store the FQDN, and many programs don't bother to verify the forward against the reverse anyway so the data would be suspect. And short of making a 200+ character array to hold it, which would be masive bloat, there is no way to fit it in the structure. If you want to store host names for posterity you will have to log-process the file and store the results somewhere else. Every program under the sun assumes utmp is a fixed-length structure. Pretty much our only option is to extend the size of existing fields and take the 'oh hell the structure size changed' hit. i -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message