This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [OT] PCYMTNQREAIYR, it really works.


On Thu, 23 Sep 2004, Dave Korn wrote:

> > -----Original Message-----
> > From: Igor Pechtchanski [mailto:pechtcha@XX.XXX.XXX]

Umm, given the subject, this is particularly vile. :-D

> > Sent: 23 September 2004 16:44
>
> > On Thu, 23 Sep 2004, Dave Korn wrote:
> >
> > > > -----Original Message-----
> > > > From: cygwin-owner On Behalf Of Christopher Faylor
> > > > Sent: 23 September 2004 15:40
>
> > > > <idle speculation>
> > > > Hmm.  I wonder if I just replaced all of the '@'s with a png
> > > > of an '@', if that would foil the spammers.
> > > > <pause>
> > > > Nope.  Wouldn't work for the text archives.
> > > > </idle speculation>
> > >
> > >   How about a big ascii-art one then?  THaT WuLd BE SOOooOO B1FF!!1!
> > > AND K00L!!1!2!
> >
> > You mean, like "`banner -c@ @`"? ;-)
>
> dk@mace /win/c/> `banner -c@ @`
> bash: @@@@: command not found
>
> AAAAAAARRRGHGHGHGHG!!!1!!!!     ToO MANy QuOTEZ!:!:!  ;-P~~~

Umm, <http://cygwin.com/acronyms/#YOWTWYWT>.  Try

[user@host] echo "`banner -c@ @`"

> > Ugh, I can just see the following pasted command line getting mungled:
> >
> > user@host>command.com something
>
>   LOL, I was just thinking about what would happen if someone harvested
> that address and tried to spam it, and then I was thinking, hey, I
> wonder.... lookee what I found!
>
> http://www.command.com/

Well, the e-mail address would be invalid anyway (contains a ">"), but the
point was that *mangling* it would result in havoc.

> > (and that's just off the top of my head, there must surely be others).
>
>   Yeh, that's why I suggested clamping down on the chars that would be
> accepted by replacing the .* with a [] charset.
>
> > IOW, it's not as easy as it seems at first.
>
>   I know.  Didn't even attempt to deal with emails of the form
> <root@[127.0.0.1]>.  Sure there are lots of other corner cases too.  It
> was a rough approximation JFTHOI.

Hmm...  If this gets picked up and used, it's definite OLOCA fodder. :-D

> [ There are plenty of rfc822-detecting regexen out there, although not
> all of them are complete nor correct;
> http://www.google.com/search?hl=en&ie=UTF-8&q=regex+rfc822 ]

It might be better/easier/safer to just filter out things like
"mailto:email@address"; or "{date} email@address wrote" (the more common
reply lead-ins) or something.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]