🚀 go-pugleaf

In article <227@dino.cs.iastate.edu>, shaver@cs.iastate.edu (Dave Shaver) writes:
> woody@rpp386.cactus.org (Woodrow Baker) writes:
> 
> >Many of the internal undocumented functions reside in an internal dictionary.
> >Decrypting any adobe font (there was a decryptor that is floating around
> >somewhere) will give you a magic number that unlocks  internaldict.  The
> >newerones have goodies like   superexec   which bypasses nearly all invalid
> >access messages (fonts still give you invalid access).
> 
> Take a look at Don Lancaster's "Ask the Guru" column, November 1988,
> Computer Shopper.  He defines his "snoop" command like this:
> 
> 	/snoop {1183615869 internaldict begin} def % activates superexec
> 
> And describes it like this:
> 
> 	"The snoop command will activate superexec for your use.  For
> 	instance, if a forall gives you an invalidaccess error, a
> 	{forall} superexec often will not.  The same trick will often
> 	work for {get} superexec.
> 
> 	Calling snoop also does open up internal dict along with all
> 	its many strange and wonderous denizens.  Very handy.  And most
> 	interesting."
> 
> 	[He goes on to describe the "hidden" FlxProc command.]
> 
> Now, does anyone have the decryptor "floating about?"  How about sharing?
> 
> /\  Dave Shaver  -=*=-  CS Systems Support Group, Iowa State University
> \\  UUCP:  {hplabs!hp-lsd, uunet!umix!sharkey}!atanasoff!shaver
> \/  Internet: shaver@atanasoff.cs.iastate.edu
> 
> 		...In stereo where available...

One problem here, is that Don got this information about superexec from me.
My biggest gripe, is that 1. he did not credit me, and 2. he published it,  
thus knocking a large contract out from under me.  Authors have loud mouths
sometimes.  Super exec is only available on certain versions, I thing V 41
and greater.  There is a way to hijack the ps printer for decryption.
first download the errhandler.  then edit the code and insert some random
character in the encrypted part, keeping track of what and where.  Send it
to the printer, and it will cause an error.  The stack will dump, and the
decrypted code to that point can be read, alternately you can alter the
error handlr to return the stackdump to the serial port, then you can
capture it.  This is admittedly slow, but works.  This was discovered
by Don, and published.

Cheers

Woody