Help about "Encrypt tool and Protect Tool"

Hi Klaus, (and krpano people)

Before the "Custom" option was available in Encrypt Tool I simply encrypted everything that could be encrypted with the Encrypt Tool -> Encryption key -> Private option and everything came out encrypted, even the krpano plugins.

Then in Protect Tool I selected "Allow loading only private-key encrypted xml and plugins files" and thus created a protected Viewer that could only load files encrypted with the Private option, which were all those that could be encrypted.

Now there is the "Custom" option: EncrypTool->Encryption Key->MyEncrytion But with that option I can't encrypt everything, since as you yourself clarified there are plugins that need "Private" encryption and don't accept "Custom" encryption.

So if you can't encrypt everything with "Custom" encryption when you try to generate a viewer you can't use the "Allow loading only private-key encrypted xml and plugin files" option because you have encrypted with a "Custom" option and not with a "Private" option and in any case there are files like the krpano plugins that couldn't be encrypted with the "Custom" option.

So the generated viewer only has the "Embed Custom Encryption / Decryption Keys" option.

In summary

1- How should files be encrypted and protected, including krpano plugins? That is, if you wanted to use the "Custom" option and not the "Private" option.

(By the way, "Decryption Keys" in the "Embed Custom Encryption / Decryption Keys" option, what does it mean? Can I decrypt files encrypted with Custom Encryption? If so, how?)

Thanks very much for your help.

Best regards.

I've thought about the custom-key-encrypted issue. I have some ideas / questions:

1) Maybe it should be possible to encrypt everything, including krpano plugins, with a custom key to avoid confusion. That would be in the "Encrypt Tool" section. On the other hand, in the "Protect Tool" section, an option like "Allow loading only custom-key encrypted xml and plugin files" could be added.

2) I can understand that a custom key is more secure than a private key in the sense that the custom key doesn't store any information about the license, but if I'm not a plugin developer and I only have the projects online (I don't distribute them) would I really need a custom key?

Anyway, I'd like to fully understand the use of a custom key.

I would greatly appreciate your comments.

Best regards

Fernando

Thanks Klaus,

So it's like if I encrypt a .zip file with a key and send it to someone. If they don't have the key they can't open it.

In the case of krpano it's for sharing plugins with other users or publishing a project for certain users who have or know the key, otherwise they wouldn't be able to open it.

That's what I understood Is that so?

Best regards,

Fdo