Project registration keys for virtual packages

[Tim Vau]

Hello! Is it possible to make an option so that you can bind external virtual containers using project keys? This is necessary so that external virtual containers cannot be used in programs with different activation algorithms. Thank you.

[Enigma]

Hi, if we are talking about Enigma Protector (licensed version), then virtual packages are unique for every protection project.
This section of keys in project file determines uniqueness of virtual packages:

Code: Select all

  <VirtualBox>
    <Secure1>D8C67F5CEEA5BD...8ADC96566DEFB891</Secure1>
    <Secure2>FAF82863B67BE343B07...C47F950D4B625B4A4C4</Secure2>
    <PrivateKey>020KT4B4CTT2ATB...AX3G79QLCBGJ44U9</PrivateKey>
    <PublicKey>0204E66971FF7609DD9D...53E3L9RC9EHBLYA5B</PublicKey>
    <Files>

This does not work for DEMO version, for DEMO version packages of one projects can be used for another project.

This also does not work for Enigma Virtual Box.

[Tim Vau]

Yes, it's true, thanks. But previously I was edited the project manually and changed only program EncryptedConstant/Public/Private values.
It's my mistake what the secure keys for external virtual box files was used by old project.

Can you add ability please to program interface for viewing and generating the secure values and the project keys for VirtualBox as it maded for Common section? Thanks.

[Enigma]

I'm sorry, but you are the first who ask for this feature for a years

I think it is not too hard to edit project file to change the values. So you can create a new protection project and replace just these virtual box constants from old project file.

[Tim Vau]

Sure, no problems. Now I know, and I will do it.
Anyway, would be nice to add VirtualBox keys parameters to custom keygen GENERATE/VERIFY SDK structure.

[Enigma]

OK, will keep your request in mind!