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

Enable TPM support for WSL2 #10777

Closed
clockcode-fernandosilva opened this issue Nov 16, 2023 · 3 comments
Closed

Enable TPM support for WSL2 #10777

clockcode-fernandosilva opened this issue Nov 16, 2023 · 3 comments

Comments

@clockcode-fernandosilva

When development scenarios that require keys/secrets handling are implemented using TPM devices, today WSL doesn't provide support for it as far as I could research.

I would like to add in the feature request list support for TPM device under WSL2.

I have been using Hyper-V Gen2 VM with TPM enabled as workaround but WSL2 support would be much simpler, easier and more convenient.

With growing attention by the community zero trust deployments and secure key storage requirements by many applications, having a way to easily develop and test would be of great value. One scenario would be developing attestation based scenarios using TPM as secure key storage. It would be helpful to be able to deploy a docker image locally with WSL2 backend and be able to test identity and attestation on it.

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

You can give me feedback by thumbs upping or thumbs downing this comment.

@craigloewen-msft
Copy link
Member

craigloewen-msft commented Nov 20, 2023

/dupe #5178

Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants