Shaders and security?

[Ben Constable]

Hello group – it has been a while but I have some questions about how Dawn is thinking about security and device contexts.

 

When I was last contributing to the group there was discussion around which parts of the shading language were secure and not, and about how to subset things. What is the current state of affairs of this? Can somebody please link me to where I can catch up on this?

[Corentin Wallez]

Hey Ben,

Nice to hear from you, it's been a while. The discussions around shading language are still contentious in the group but we basically agree that the security of the language is a programming model issue and not a property of this or that shading language. On the SPIR-V side we have the start of an execution environment that explains how SPIR-V is embedded in WebGPU. This is the basis of securely embedding SPIR-V in WebGPU. The code transform to sandbox SPIR-V itself didn't change from the investigation we produced a while ago.

Hopefully this answers your question!

Cheers,

Corentin

On Tue, Apr 30, 2019 at 2:05 AM Ben Constable <ben...@gmail.com> wrote:

Hello group – it has been a while but I have some questions about how Dawn is thinking about security and device contexts.

 

When I was last contributing to the group there was discussion around which parts of the shading language were secure and not, and about how to subset things. What is the current state of affairs of this? Can somebody please link me to where I can catch up on this?

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To post to this group, send email to dawn-g...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/e3cb5819-6a25-4f55-9a38-c550d6ace9ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.