| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
* If there is another redirecting factory method that targets theThis is still a bug which opens up a possibility to breach API surface described by a dynamic interface. Previously we had some discussions about using dynamic interface to enforce security sandbox, so this kind of breach would be undesirable.
Is it urgent enough to land this workaround / incomplete fix now instead of implementing a proper fix? If it is, then consider filing a bug about the incorrect enforcement of dynamic interface which this CL introduces.
case Procedure():This is likely insufficient if the whole library / class is exported via dynamic interface, as we're not going down to members when reading dynamic interface (in order to avoid spending too much time on reading dynamic interface if we only have a few references to validate).
If you implement this traversal down from libraries and classes, consider assessing how it affects bytecode compilation time in case of small dynamic module and huge dynamic interface (such as whole flutter framework).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
* If there is another redirecting factory method that targets theThis is still a bug which opens up a possibility to breach API surface described by a dynamic interface. Previously we had some discussions about using dynamic interface to enforce security sandbox, so this kind of breach would be undesirable.
Is it urgent enough to land this workaround / incomplete fix now instead of implementing a proper fix? If it is, then consider filing a bug about the incorrect enforcement of dynamic interface which this CL introduces.
This is not urgent and we don't have to land this. I had this initial idea and wanted to share it to get feedback and better understand the constraints 😊
case Procedure():This is likely insufficient if the whole library / class is exported via dynamic interface, as we're not going down to members when reading dynamic interface (in order to avoid spending too much time on reading dynamic interface if we only have a few references to validate).
If you implement this traversal down from libraries and classes, consider assessing how it affects bytecode compilation time in case of small dynamic module and huge dynamic interface (such as whole flutter framework).
Great points, makes sense. I appreciate hearing your concern around traversal costs during compilation.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |