for the newest Versions of Windows 10, Microsoft require to let sign all drivers from Microsoft. For the signing process Microsoft wants logfiles of HCK and HLK Tests. As I want to build veracrypt myself, I also need to make these test procedures. Would it be possible to get the original testsuites that were used for the signing request of veracrypt?
Thanks a lot
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please contact me directly since such question falls in the context of
professional support that I provide to customers. You can use the
contact form of IDRIX website or send me an email to VeraCrypt email
address.
Normally driver submissions to Microsoft are done by registered business
entities and not end users since it requires some legal agreements and
an EV code signing certificates issued in the name of the organization.
On the other hand, since submitting the driver to Microsoft amounts to a
new product different from VeraCrypt (you can't have two VeraCrypt
drivers signed by two different entities), the license doesn't allow you
to use the name VeraCrypt or IDRIX so you will have to remove all
references to VeraCrypt or IDRIX from your product that is derived from
VeraCrypt.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
for the newest Versions of Windows 10, Microsoft require to let sign all drivers from Microsoft. For the signing process Microsoft wants logfiles of HCK and HLK Tests. As I want to build veracrypt myself, I also need to make these test procedures. Would it be possible to get the original testsuites that were used for the signing request of veracrypt?
Thanks a lot
Thomas
Hi Thomas,
Please contact me directly since such question falls in the context of
professional support that I provide to customers. You can use the
contact form of IDRIX website or send me an email to VeraCrypt email
address.
Normally driver submissions to Microsoft are done by registered business
entities and not end users since it requires some legal agreements and
an EV code signing certificates issued in the name of the organization.
On the other hand, since submitting the driver to Microsoft amounts to a
new product different from VeraCrypt (you can't have two VeraCrypt
drivers signed by two different entities), the license doesn't allow you
to use the name VeraCrypt or IDRIX so you will have to remove all
references to VeraCrypt or IDRIX from your product that is derived from
VeraCrypt.