LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (October 1999, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 11 Oct 1999 07:46:23 -0400
Reply-To:     john_iwaniszek@worldnet.att.net
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         john_iwaniszek@WORLDNET.ATT.NET
Organization: AT&T WorldNet Services
Subject:      Re: "Secure" macro ?
Content-Type: text/plain; charset=us-ascii

a macro can be 'decompiled' by running it with mprint turned on and also using mfile to route mprint output to a file.

Paige Miller wrote:

> Jack Shoemaker wrote: > > > > Jim, > > > > I've done two things in the past. Neither is 100% secure, but depending > > on your needs, maybe one will help. > > > > 1) Compile macro and then just distribute the catalog which contains the > > compiled macro. > > Why would compiling a macro be less than 100% secure. Could someone take > the binary code that is stored in the catalog and de-compile it? I think > not, other than perhaps someone at SAS Institute who developed the macro > compiler in the first place. Please explain further. Thanks! > > Paige Miller > paigem@kodak.com


Back to: Top of message | Previous page | Main SAS-L page