You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of relying on the existence of SCARY_MUF_PRIMS
to handle access to things like PROGRAM_SETLINES and
TOADPLAYER, why not force them to only be allowed if
the program is blessed? That way, if the text is
changed in any fashion, the program can't run that set
of primitives.
TOADPLAYER should be M4+ (I'm using the plus sign to
designate blessing), but PROGRAM_SETLINES should be
M1+ (so that people can write programs to modify their
own programs, even at M1.)
The text was updated successfully, but these errors were encountered:
For context, SCARY_MUF_PRIMS was taken out as a #define in part since users of the Winfuzz binary couldn't enable it. Program blessing is definitely an interesting idea worthy of discussion.
Instead of relying on the existence of SCARY_MUF_PRIMS
to handle access to things like PROGRAM_SETLINES and
TOADPLAYER, why not force them to only be allowed if
the program is blessed? That way, if the text is
changed in any fashion, the program can't run that set
of primitives.
TOADPLAYER should be M4+ (I'm using the plus sign to
designate blessing), but PROGRAM_SETLINES should be
M1+ (so that people can write programs to modify their
own programs, even at M1.)
The text was updated successfully, but these errors were encountered: