X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Matthew Woehlke <mw_triad AT users DOT sourceforge DOT net>
Subject:  Re: Waiting for //.terminfo or //.termcap
Date:  Thu, 29 Mar 2007 11:09:55 -0500
Lines: 13
Message-ID: <eugock$gpn$1@sea.gmane.org>
References:  <Pine DOT GSO DOT 4 DOT 63 DOT 0703281515030 DOT 16390 AT access1 DOT cims DOT nyu DOT edu> <OF7A35DF0E DOT BDD92CB1-ON852572AC DOT 006C325F-852572AC DOT 006D53B2 AT gdeb DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.0
In-Reply-To: <OF7A35DF0E.BDD92CB1-ON852572AC.006C325F-852572AC.006D53B2@gdeb.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Ken Fast wrote:
> I will check into the ncurses
> issue and maybe even go poking around in the source code.

That would be great. I am pretty sure it *is* a bug, because IIRC POSIX 
explicitly allows '//' to mean something other than '/'. This means that 
looking for //.terminfo if HOME=/ is Bad and Just Plain Wrong. It would 
even be a security issue if it is possible for a .terminfo/.termcap to 
be dangerous...

-- 
Matthew
<insert witty signature here>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/