[12183] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Time to update those CGIs again

daemon@ATHENA.MIT.EDU (Wise Cat)
Fri Oct 8 19:19:12 1999

Mime-Version: 1.0
Content-Type: text/plain; charset=Windows-1251
Content-Transfer-Encoding: 8bit
Message-Id:  <18773.991008@tomcat.ru>
Date:         Fri, 8 Oct 1999 18:33:38 +0400
Reply-To: Wise Cat <wise@tomcat.ru>
From: Wise Cat <wise@TOMCAT.RU>
X-To:         Tymm Twillman <tymm@coe.missouri.edu>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <Pine.SGI.4.05.9910061314450.211473-100000@tiger.coe.missouri.edu>

Hello Tymm Twillman,

qped`, 6 njrap 1999 c., you wrote:

TT> As I reported in my message, tried with 4.51 and 4.7 under
TT> Linux/English... And same reported with at least some Solaris versions.

TT> -Tymm

I  found  it  works  on  FreeBSD with 4.6 too but: only with (default)
iso-8859-1  encoding.  It  doesn't  work  if  the  page  has different
codepage,  for example iso-8859-2 or iso8859-15 or koi8-r. So it seems
to be the problem with Netscape translation table for this codepage.

To  patch server quickly you can set up different default codepage for
your documents.

TT> On Wed, 6 Oct 1999, 3APA3A wrote:

>> Hello Tymm Twillman,
>>
>> 05.10.99 19:50, you wrote: Time to update those CGIs again;
>>
>> T> Seems that at least some Unix versions of Netscape treat characters 0x8b
>> T> and 0x9b (NOT the strings "0x8b" and "0x9b" but the characters with these
>> T> ascii values) just like < and > respectively...
>>
>> I've  tested  Netscape Communicator 4.6 under both Windows and FreeBSD
>> $ netscape -v
>> Netscape 4.6/Export, 04-May-99; (c) 1995-1998 Netscape Communications Corp
>> -  there  is no such problem. Can you say the version of Netscape with
>> this bug?

         /\_/\
        { . . }     |\
+--oQQo->{ ^ }<-----+ \
|  3APA3A  U  3APA3A   }
+-------------o66o--+ /
                    |/

home help back first fref pref prev next nref lref last post