Baa-meh

Hi, The build instructions use VS 2010. The latest VC version compiles on Visual Studio 2022. Are there newer instructions I can't find, or maybe it's the same as for the 2010 version?

So, I got new PKI smart cards with the OEM middleware eps2003csp11_64.dll. This is ALSO blocked with the dynamic code generation check. I got these new cards because the old Athena module was blocked due to dcg. My thought at this point is to hack VeraCrypt and remove this block; hopefully, it is as simple as a condiiton change, but dunno'. Anyway, thanks for this VeraCrypt.

Yes, I agree with the disagree to thing. I hope I have kept this civil, and as earlier stated I have the utmost respect for Mounir. I was anyway getting new smart cards (easier said than done) from Microcosm.uk. I wrote to them about this matter, and they said they did not know because the module was made by an OEM (Feitian). I will update on how this works out, if anyone's interested. Anyway, thanks for your feedback, and I would probably have said the same, if not personally affected by this.

I do not think that is up to anyone but the user. Yes, in the case of Windows hardware changes, their is little choice and if Veracrypt cannot use modules with dcg due to MS security policies, then fine. However, that does not seem to be the case, according to MI: 'Throughout my extensive testing with major PKCS#11 libraries, I did not encounter this unusual behavior. Furthermore, it's uncommon and somewhat suspicious for a PKCS#11 library to modify executable code at runtime.' Obviously, the extensive...

The blocking of pkcs#11, which is told to us via the error message: 'The operation was blocked as the process prohibits dynamic code generation' is not, imho, Mounir's decision to make. In my case the ase dll was suddenly blocked, though I'd been using it for years! I get that MI thinks dynamic code generation is terribly dangerous, and he might be right; however, he has no right to mess up peoples' veracrypts. If I might suggest, the error could still occur, but there is a choice for the user to...

The blocking of pkcs#11, which is told to us via the error message: 'The operation was blocked as the process prohibits dynamic code generation' is not, imho, Mounir's decision to make. In my case the ase dll was suddenly blocked, though I'd been using it for years! I get that MI thinks dynamic code generation is terribly dangerous, and he might be right; however, he has no right to mess up peoples' veracrypts. If I might suggest, the error could still occur, but there is a choice for the user to...

The blocking of pkcs#11, which is told to us via the error message: 'The operation was blocked as the process prohibits dynamic code generation' is not, imho, Mounir's decision to make. In my case the ase dll was suddenly blocked, though I'd been using it for years! I get that MI thinks dynamic code generation is terribly dangerous, and he might be right. However, he has no right to mess up peoples' veracrypts. If I might suggest, the error could still occur, but there is a choice for the user to...

The blocking of pkcs#11, which is told to us via the error message: 'The operation was blocked as the process prohibits dynamic code generation' is not, imho, Mounir's decision to make. In my case the ase dll was suddenly blocked, though I'd been using it for years! I get that MI thinks dynamic code generation is terribly dangerous, and he might be right. However, he has no right to mess up people's veracrypts. If I might suggest, the error could still occur, but there is a choice for the user to...