From owner-freebsd-ports@FreeBSD.ORG  Sun Feb  7 15:12:55 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8C951106566C
	for <ports@freebsd.org>; Sun,  7 Feb 2010 15:12:55 +0000 (UTC)
	(envelope-from anon@elhacker.net)
Received: from mail-yw0-f191.google.com (mail-yw0-f191.google.com
	[209.85.211.191])
	by mx1.freebsd.org (Postfix) with ESMTP id 5A1778FC16
	for <ports@freebsd.org>; Sun,  7 Feb 2010 15:12:55 +0000 (UTC)
Received: by ywh29 with SMTP id 29so319771ywh.13
	for <ports@freebsd.org>; Sun, 07 Feb 2010 07:12:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.235.26 with SMTP id i26mr6648405anh.126.1265554257099; 
	Sun, 07 Feb 2010 06:50:57 -0800 (PST)
Date: Sun, 7 Feb 2010 08:50:56 -0600
Message-ID: <619714181002070650q72de2e23r9c7afbb8223630e0@mail.gmail.com>
From: Anon <anon@elhacker.net>
To: ports@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: 
Subject: xterm 253 DECRQSS Again?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 15:12:55 -0000

Hi

long ago I read about the bug in Xterm CVE-2008-2383 and updated xterm. Now
I have the version of xterm 253 and on occasion being in xterm to run a cat
on binary file (executable, images, etc) appear repeatedly on Shell "2c1:
command not found". You will see in the picture you take

http://lh3.ggpht.com/_1zYIthtq7IY/S24v__tlDAI/AAAAAAAAAJk/aWhG5E3fJ4o/s800/xterm_bug.png

This can be a bug again?

Regards

- Anon