on code signatures

[Tom Buskey]

On 5/8/05, Benjamin Scott <dragonhawk at iname.com> wrote:
> On May 4 at 11:33am, aluminumsulfate at earthlink.net wrote:
> > ~!fs\ s\a\ ~\/ a\ll al\l#~^~_~g at j-~@^~_ki~-^l~l~~-n~_x/  \~^u~_pa-~R-
> >
> > ^ notice the ~ escape at the beginning of that line.  When piped through
> > /bin/mail ..., mail will interperet ~! as a shell escape and run everything
> > up to the "#" as a shell command.... Oh, what surprises await!!
> 
>    I'm prolly missing something really obvious here, but wouldn't that just run
> this
> 
>         fs\ s\a\ ~\/ a\ll al\l
> 
> as a shell command?  On my system, at least, that results in a "command not
> found" error.  I also don't have command called "fs", assuming that was what
> was intended.

You're not running Solaris.

$ which fs
/usr/openwin/bin/fs

$ fs
/usr/openwin/bin/xfs notice: Fatal Error. No Listening sockets
established.  Exiting. ListenTransCount=0 errno=125
/usr/openwin/bin/xfs error: Cannot establish any listening sockets

$ man -s 1 fs
NAME
     xfs - X font server

SYNOPSIS
     xfs [ -config configuration_file ] [ -ls listen-socket  ]  [
     -port tcp_port ]