Re: two bugs involving certain spam

On Fri, 15 Dec 2006, Patrick J. Collins wrote:

> I just wanted to report two bugs that I see very regularily, both
> involve received spam and really impede Pine's performance.

Worse, this could be a security risk.

> bug #1:  I will be scrolling through my message index, and suddenly
> a message will appear out of place, overlapping on another message..
> I have taken some screen shots:
>
> Here is before placing my cursor on the email:
> http://collinatorstudios.com/www/pine1.png
>
> You can see that usually these emails involve funky characters with
> accents..  So when I move down to this message, this is what happens:
> http://collinatorstudios.com/www/pine2.png
>
> And, if I happen to try to view this message, then I see this:
> http://collinatorstudios.com/www/pine3.png
>
> and pine automatically tries to compose a new email... if I say
> cancel, it will keep trying to compose new email over and over and
> over, and I have to quit.. If I tell it to compose email, then I see
> this:
> http://collinatorstudios.com/www/pine4.png
>
> 1;2c in the To field, and if I try to cancel, it just recreates
> another email with 1;2c in the To field.

That string "1;2c" is part of an ANSI reply (it is consistent with your 
terminal answering "ESC[?1;2c" to an ESC[0c request). Pine should not 
pass any non-whitespace control characters from messages to the terminal 
(in other words, the only control characters that Pine should spit out 
are the ones programmed into Pine).

I've never seen this in real life (and I think I get all Korean and 
Japanese porn spam). However, I was able to reproduce the issue easily. 
Run this Perl script to generate the escape sequence:

% perl >escape.txt
$a = "\233c";
print $a;
^D

Then, use ^R during composition to read escape.txt into the message 
body. All will be hunky dory until you try to copy the escape characters 
to the Subject line using ^K/^U .

This should probably be fixed at the same time the handling of tabs in 
Subject lines gets fixed :-)

Cheers,

 				-- Bert
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info