Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: Program Blessing (SF issue) #635

Open
tanabi opened this issue Jul 7, 2021 · 1 comment
Open

Idea: Program Blessing (SF issue) #635

tanabi opened this issue Jul 7, 2021 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@tanabi
Copy link
Collaborator

tanabi commented Jul 7, 2021

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.)

@tanabi tanabi added the enhancement New feature or request label Jul 7, 2021
@tanabi tanabi added this to the 7.7 milestone Jul 7, 2021
@wyld-sw
Copy link
Member

wyld-sw commented Jul 7, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants