From owner-freebsd-hackers Tue Jan 21 1:58:11 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3DCC37B401 for ; Tue, 21 Jan 2003 01:58:09 -0800 (PST) Received: from postal.sdsc.edu (postal.sdsc.edu [132.249.20.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84B1343E4A for ; Tue, 21 Jan 2003 01:58:08 -0800 (PST) (envelope-from okumoto@ucsd.edu) Received: from multivac.sdsc.edu (IDENT:u2l2y5XuI4aI/m+/dCcsA37n6GpzX02f@multivac.sdsc.edu [132.249.20.57]) by postal.sdsc.edu (8.11.6/8.11.6/server/51) with ESMTP id h0L9vbK10797; Tue, 21 Jan 2003 01:57:37 -0800 (PST) Received: by multivac (8.11.6+Sun/1.11-SolarisClient) id h0L9vaq05562; Tue, 21 Jan 2003 01:57:36 -0800 (PST) To: Kris Kennaway Cc: Miguel Mendez , hackers@FreeBSD.ORG Subject: Re: RFC: Adding a new (safer) data entry function to libdialog References: <20030120121851.30ff961f.flynn@energyhq.homeip.net> <20030121015947.GA7310@rot13.obsecurity.org> <20030121101502.049abd8e.flynn@energyhq.homeip.net> <20030121094405.GA21197@rot13.obsecurity.org> From: Max Okumoto Date: 21 Jan 2003 01:57:36 -0800 In-Reply-To: <20030121094405.GA21197@rot13.obsecurity.org> Message-ID: Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Tue, Jan 21, 2003 at 10:15:02AM +0100, Miguel Mendez wrote: > > On Mon, 20 Jan 2003 17:59:47 -0800 Kris Kennaway wrote: > > >> [making libdialog safer } > > > libdialog is rife with overflowable buffers..I'm not sure it would be > > > safe even with this input method. > > > > Okay, I have another idea that might be a bit more productive, since the > > code in libdialog seems to be nothing but a huge hack. How about > > adopting tvision to replace dialog(3)? Libh uses tvision, and I've > > thought about writing a small API compat glue (libtdialog.{so,a}) that > > would allow legacy libdialog code to be linked with tvision without > > modification. The only (big) drawback I see in tvision is that it's in > > C++, otherwise is lightyears ahead of what dialog(3) currently offers. > > That could be quite a worthwhile project. > > Kris There are alot of problems in the tvision library too. I made the patch that 'allows' it to compile with gcc3.2.1. I did not correct the problems in the since I am trying to focus on libh. Max Okumoto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message