-
Notifications
You must be signed in to change notification settings - Fork 121
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
Discussion about policy-integrity integration on Windows #856
Comments
Hi Robert, I'll include it o the agenda, so you can join the next one (Jan 19th) |
Thanks! |
@mhdawson , sorry I missed this notification and didn't realize there was a security WG meeting today. Could we get on the agenda for the next security WG meeting? Looking at the meeting notes history, it seems like the next meeting will be on Feb 16. If that's the case I'll put it in my calendar now. |
It will be discussed in the next meeting (Feb 16). |
nodejs/node#47609 is made for
|
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Hi,
A while back we presented a prototype of Node’s Policy integrity integration with Window’s code integrity system. As quick refresher (it’s been a while 😃), we discussed integrity verification using a detached pkcs7 signature that’s then verified by the platform. We’ve done the work to light this feature up, and it’s currently in Windows insider builds. I’d like to take some time to discuss how this would integrate with Node, and brainstorm other platform features that would make using code integrity features easier for devs and sys admins.
I won't be able to attend the upcoming Jan 5th meeting. Do you have time on the agenda during the following security wg meeting to discuss this?
Thanks,
Robert
The text was updated successfully, but these errors were encountered: