Hi @hhdhhd I'm afraid there is no direct solution for you. I see that you are running Cinema 4D R21, which implies Python 2.7.7.
Looking at the issue Cryptodome developers seem to have messed up Python2 import statement with Python 3 import statement. So the only way is to fix their module for Python 2.7.X.

Slight note their module is working nicely with the latest Cinema 4D R23 which uses Python 3.7.7.

Cheers,
Maxime.

@WickedP yes you can assume it.

Cinema 4D first loads all dlls, then PluginMessage is forwarded to each dlls.

Hi you didnt write the error message

Hi @indexofrefraction unfortunately this is not possible to implement your own interface within Python.
See Maxon API Introduction - Interface.

So I would rather recommend you to take a look at the Python logging module.

Cheers,
Maxime.

Hi @hhdhhd your question is not clear to our team do you want to use AES within your plugin or you asked about AES encryption for plugins in general?

Just for your information as stated in Plugin Structure .pyp file (python plugin file) are standard python file encrypted while pypv (generated via the Extensions Menu -> Tools -> Source Protector) are encrypted file (we don't share any information how this encryption is done).

Cheers,
Maxime.

Hi Unfortunately I didn't found any workaround. I saw you deleted the topic but I restored it since there is still valuable information for the next readers, moreover, I will update the post once the bug will be fixed.

Cheers,
Maxime

Hi @mp5gosu unfortunately this is a bug, I'm still digging it so thanks for the report :)

I will take you informed if I found a workaround.
Cheers,
Maxime.

And another good resource is the Calculate Group per Polygon from Cesar Vonc.
Cheers,
Maxime.

Hi unfortunately it's most likely that the SSL version used in R19 is not anymore compatible with the certificate used to validate the connection from you and the website.

So I don't see a real way to support it without investing a lot of time and unfortunately, we don't support R19 anymore so in this case, the most correct fix will be to update the SSL module which will not happen.
You can give it a try to ssl.SSLError: tlsv1 alert protocol version or either use another networking library that uses its own SSL.
Finally you may take a look to compile SSL yourself and incorporate it see Building NumPy for Cinema 4D on Windows and you can try its updated version of SSL https://public.niklasrosenstein.com/cinema4d/python/modules/ssl/

Cheers,
Maxime.

Hi @velbie unfrotually this is not possible to do it due to a bug in the Python API. I've opened a new bug report.

I will try to find a workaround within the next days (but I'm pretty doubtfully to come with a solution this week)
Cheers,
Maxime.