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
An uneasiness appeared in the community about prebuilt procmacros, that CairoLS will now happily execute arbitrary code whenever the user pastes whatever Scarb.toml/Cairo code they get from the internet.
A long-term solution is to sandbox procmacros, but a short-term idea is to write a system that will ask the user to explicitly allow running all proc macros in a workspace/particular procmacros (identifier by PackageId?)/something like this.
An uneasiness appeared in the community about prebuilt procmacros, that CairoLS will now happily execute arbitrary code whenever the user pastes whatever Scarb.toml/Cairo code they get from the internet.
A long-term solution is to sandbox procmacros, but a short-term idea is to write a system that will ask the user to explicitly allow running all proc macros in a workspace/particular procmacros (identifier by
PackageId
?)/something like this.Write a design doc, to be shared with #crust.
Important considerations:
The text was updated successfully, but these errors were encountered: