Skip to content

Sanity check ACL #334

Description

@sohkai

A few things:

  • User input should be restricted, and checked to only be within a certain bounds / certain OPs
  • Potential infinite loops may occur in the ACL scripting
  • Potential ability for encoded params to pass off as OPs (by going into the 200+ range)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions