So, I’ve installed the latest HLK, gotten the latest playlist, and run my FS driver and my FS mini-filter through the required tests. They all pass. Yay!.
Now it comes to creating a submission package so I can get an MS signature for upcoming Windows 2016 server. The HLK has a nice “package” function to put together an HLKX file for submission. Obviously, I need to create a “signed” package using my company’s EV certificate.
Here’s the problem: I run my tests on a pair of systems set up with the HLK. But our EV certificate is on a hardware token attached to an official build machine that I’m not allowed to touch. So far, that machine doesn’t have any HLK installed on it, and certainly doesn’t have all my test results. I’m not allowed to touch the machine with the EV certificate, but I can get someone to deliver files to that machine if needed.
Am I going to have to get the HLK installed on the machine that owns the EV cert so I can create a submission package? If so, how do I get my test results on that machine so they can be part of the submission package?
If your machine where ev certificate hardware token is connected is windows server ( 2016 or others) , you can install hlk server on it.
On hlk server where you have test results , you can create hlk package without signing.
Then use this package and recreate another package with ev signing on ev certificate machine .
Sent from my Windows 10 phone
From: xxxxx@veritas.com
Sent: 27 July 2016 10:44 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Creating an HLK submissing package for an FS mini-filter
So, I’ve installed the latest HLK, gotten the latest playlist, and run my FS driver and my FS mini-filter through the required tests. They all pass. Yay!.
Now it comes to creating a submission package so I can get an MS signature for upcoming Windows 2016 server. The HLK has a nice “package” function to put together an HLKX file for submission. Obviously, I need to create a “signed” package using my company’s EV certificate.
Here’s the problem: I run my tests on a pair of systems set up with the HLK. But our EV certificate is on a hardware token attached to an official build machine that I’m not allowed to touch. So far, that machine doesn’t have any HLK installed on it, and certainly doesn’t have all my test results. I’m not allowed to touch the machine with the EV certificate, but I can get someone to deliver files to that machine if needed.
Am I going to have to get the HLK installed on the machine that owns the EV cert so I can create a submission package? If so, how do I get my test results on that machine so they can be part of the submission package?
NTFSD is sponsored by OSR
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:>
Thanks. I guess that’s what I’ve figured out. Install HLK on machine with EV certificate, run tests on a different machine, then use HLKX “merge” function to move the test result package to build machine and sign the resulting merged package.
Carl
From: Hariom Kesh [mailto:xxxxx@gmail.com]
Sent: Wednesday, July 27, 2016 12:29 PM
To: Carl Appellof; Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Creating an HLK submissing package for an FS mini-filter
If your machine where ev certificate hardware token is connected is windows server ( 2016 or others) , you can install hlk server on it.
On hlk server where you have test results , you can create hlk package without signing.
Then use this package and recreate another package with ev signing on ev certificate machine .
Sent from my Windows 10 phone
From: xxxxx@veritas.commailto:xxxxx
Sent: 27 July 2016 10:44 PM
To: Windows File Systems Devs Interest Listmailto:xxxxx
Subject: [ntfsd] Creating an HLK submissing package for an FS mini-filter
So, I’ve installed the latest HLK, gotten the latest playlist, and run my FS driver and my FS mini-filter through the required tests. They all pass. Yay!.
Now it comes to creating a submission package so I can get an MS signature for upcoming Windows 2016 server. The HLK has a nice “package” function to put together an HLKX file for submission. Obviously, I need to create a “signed” package using my company’s EV certificate.
Here’s the problem: I run my tests on a pair of systems set up with the HLK. But our EV certificate is on a hardware token attached to an official build machine that I’m not allowed to touch. So far, that machine doesn’t have any HLK installed on it, and certainly doesn’t have all my test results. I’m not allowed to touch the machine with the EV certificate, but I can get someone to deliver files to that machine if needed.
Am I going to have to get the HLK installed on the machine that owns the EV cert so I can create a submission package? If so, how do I get my test results on that machine so they can be part of the submission package?
—
NTFSD is sponsored by OSR
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></mailto:xxxxx></mailto:xxxxx>