head 1.4; access; symbols pkgsrc-2013Q2:1.4.0.54 pkgsrc-2013Q2-base:1.4 pkgsrc-2012Q4:1.4.0.52 pkgsrc-2012Q4-base:1.4 pkgsrc-2011Q4:1.4.0.50 pkgsrc-2011Q4-base:1.4 pkgsrc-2011Q2:1.4.0.48 pkgsrc-2011Q2-base:1.4 pkgsrc-2009Q4:1.4.0.46 pkgsrc-2009Q4-base:1.4 pkgsrc-2008Q4:1.4.0.44 pkgsrc-2008Q4-base:1.4 pkgsrc-2008Q3:1.4.0.42 pkgsrc-2008Q3-base:1.4 cube-native-xorg:1.4.0.40 cube-native-xorg-base:1.4 pkgsrc-2008Q2:1.4.0.38 pkgsrc-2008Q2-base:1.4 pkgsrc-2008Q1:1.4.0.36 pkgsrc-2008Q1-base:1.4 pkgsrc-2007Q4:1.4.0.34 pkgsrc-2007Q4-base:1.4 pkgsrc-2007Q3:1.4.0.32 pkgsrc-2007Q3-base:1.4 pkgsrc-2007Q2:1.4.0.30 pkgsrc-2007Q2-base:1.4 pkgsrc-2007Q1:1.4.0.28 pkgsrc-2007Q1-base:1.4 pkgsrc-2006Q4:1.4.0.26 pkgsrc-2006Q4-base:1.4 pkgsrc-2006Q3:1.4.0.24 pkgsrc-2006Q3-base:1.4 pkgsrc-2006Q2:1.4.0.22 pkgsrc-2006Q2-base:1.4 pkgsrc-2006Q1:1.4.0.20 pkgsrc-2006Q1-base:1.4 pkgsrc-2005Q4:1.4.0.18 pkgsrc-2005Q4-base:1.4 pkgsrc-2005Q3:1.4.0.16 pkgsrc-2005Q3-base:1.4 pkgsrc-2005Q2:1.4.0.14 pkgsrc-2005Q2-base:1.4 pkgsrc-2005Q1:1.4.0.12 pkgsrc-2005Q1-base:1.4 pkgsrc-2004Q4:1.4.0.10 pkgsrc-2004Q4-base:1.4 pkgsrc-2004Q3:1.4.0.8 pkgsrc-2004Q3-base:1.4 pkgsrc-2004Q2:1.4.0.6 pkgsrc-2004Q2-base:1.4 pkgsrc-2004Q1:1.4.0.4 pkgsrc-2004Q1-base:1.4 pkgsrc-2003Q4:1.4.0.2 pkgsrc-2003Q4-base:1.4 buildlink2-base:1.4 netbsd-1-3-PATCH003:1.3; locks; strict; comment @# @; 1.4 date 98.11.13.15.56.25; author tv; state dead; branches; next 1.3; 1.3 date 98.08.07.10.40.33; author agc; state Exp; branches; next 1.2; 1.2 date 98.07.19.03.37.47; author tv; state Exp; branches; next 1.1; 1.1 date 98.06.07.19.48.47; author frueauf; state Exp; branches; next ; desc @@ 1.4 log @Update pico to 3.4 (from Pine 4.05) @ text @$NetBSD: patch-pine-bugtraq,v 1.3 1998/08/07 10:40:33 agc Exp $ Date: Sat, 25 Apr 1998 14:24:43 +0200 From: Michal Zalewski To: BUGTRAQ@@NETSPACE.ORG Subject: pine/pico vt control characters bug Pico, an editor included with pine 3.96 package, handles vt control characters (eg. 0x9B) improperly, so it's possible to do almost anything when normal text file is viewed with pico. Example? Try viewing file containing only two characters: 0x9B and 0x63... That's not all, pico is called by pine when you're replying to mail message. Anyone may insert any control chars (using quoted-printable encoding) to his signature. Fix (edited for NetBSD's pkg system): --- pico/display.c.orig Fri Jun 19 13:19:53 1998 +++ pico/display.c Sat Jul 18 23:16:33 1998 @@@@ -128,8 +128,7 @@@@ VIDEO **vscreen; /* Virtual screen. */ VIDEO **pscreen; /* Physical screen. */ -#define ISCONTROL(C) ((C) < 0x20 || (C) == 0x7F \ - || ((gmode & P_HICTRL) && ((C) > 0x7F && (C) < 0xA0))) +#define ISCONTROL(C) ((C) < 0x20 || (C) == 0x7F || ((C) >= 0x80 && (C) < 0xA0)) /* (should help, at least in above situation) _______________________________________________________________________ Michal Zalewski [lcamtuf@@boss.staszic.waw.pl] <= finger for pub PGP key Iterowac jest rzecza ludzka, wykonywac rekursywnie - boska [P. Deutsch] [echo "\$0&\$0">_;chmod +x _;./_] <=------=> [tel +48 (0) 22 813 25 86] @ 1.3 log @Add NetBSD RCS Ids. @ text @d1 1 a1 1 $NetBSD$ @ 1.2 log @Update pico to 3.0, part of the pine 4.00 distribution. Build libpico with libtool, enabling a libpico shared object useable with pine. @ text @d1 2 @ 1.1 log @Initial addition of a handy text editor that ships with Pine. Fixes pr 5548 by Tim Rightnour, some portlint cleanups. @ text @d15 12 a26 11 --- pico/display.c.orig Sun Apr 26 00:16:06 1998 +++ pico/display.c Sun Apr 26 00:17:12 1998 @@@@ -266,7 +266,7 @@@@ } while ((vtcol&0x07) != 0); } - else if (c.c < 0x20 || c.c == 0x7F) { + else if (c.c < 0x20 || c.c == 0x7F || c.c == 0x9B) { ac.c = '^'; vtputc(ac); ac.c = (c.c ^ 0x40); @