pycrypto | Crypto application code for the zkSNARKs toolbox ZoKrates | Cryptography library

pycrypto doesn't work with python3, you can use instead pycryptodome :

I'd wager something is missing, or that version of Pycrypto just doesn't work on your Python 3.10 on 64-bit Windows. (Pycrypto hasn't been updated since 2013. You probably don't want to use it.)

Could you get whatever you want done with cryptography, i.e. pip install cryptography? There seem to be pre-compiled wheels for Windows for it.

There's also a fork of pycryptodome, pycryptodomex, that might help.

I've fixed the build issue. It required adding meta-python2 as I did; but instead of IMAGE_INSTALL_append = " python-dev", TOOLCHAIN_HOST_TASK_append = " nativesdk-python-core" is needed instead in local.conf.

Go to your terminal/cmd and write this command if you have pip/pip3:

Looks like this is part of an actively tracked issue with Tkinter in PyCharm. You can find the reference on the Pycharm's developer's issue tracker. The issue is undiagnosed, but if looking at similar problems with Tk on StackOverflow, one can see that it's an issue with thread safety and/or multithreading.

All I can do is speculate as to the cause, which is not helpful, however, I can at least collate the suggested workarounds:

1. Switch to a different Matplotlib backend (See docs: What is a backend?). Such as Qt5, but you will need to make sure they are available in your environment.

   This approach is the most promising as other backends are better able to deal with not being the main thread or are explicitly safe for multi-threading. It's also the simplest unless you have a really specific reason for preferring TkAgg.

2. Do not use the debugger with interactive plots.

3. Set "Variables Loading Policy" to "Synchronously" in Debugger as suggested by a PyCharm dev in the linked issue.

4. Enable "Scientific mode" in Pycharm.

5. More esoteric workarounds such as closing your figures within the code before drawing the second one. Example, after plotting the first figure:

You need everything to be the exact same between both versions. This is not currently true; fix that.

Your java code uses:

• AES at block size 128, because that's just how AES rolls. Nothing to configure.
• AES key size of 128, 192, or 256 bits.
• The key.
• The Mode of Operation. Your java code uses ECB (which is insecure). You've told your python code to use GCM. That's, obviously, not going to work. You need to specify ECB there, too.
• Given that it's ECB, there is no IV.
• The padding mode. Java code is doing PKCS5Padding here.
• Crypto is fundamentally byte based but you're trying to encrypt strings, which aren't. That means the string is being converted to bytes, and that means a charset encoding is used. You didn't specify in your java code which means you get 'platform default'. Horrible idea, but if you can't change the java side, figure out what that is, and use the same encoding in your python code.
• Finally, your java code base64's the result.

For most of these, I simply can't tell you; the code you pasted is insufficient. For example, AES key size and whether the keys are actually identical? I have no idea - you tell me. How did you make that SecretKey key object?

I'm not as familiar with python but it sure looks like you base64-encode it, and then decode it again. That's.. no, don't do that. Your java code encodes and that's that. Your python code should base64 encode and that's that.

I'm pretty sure python also defaults to PKCS5Padding.

That leaves the encoding mode which you 100% mismatched between java and python give what little code you pasted, and the way you construct the keys. If the text you're encrypting isn't straight ASCII, it's somewhat likely charset encoding is also causing a difference.

It's crypto. One tiny difference and the outputs will be quite different.

I'm not familiar with VSCode, but you can manually force the chosen architecture slice of anything you launch with the arch command (see man arch).

If you have a script that you'd normally launch like:

Firstly, you don't need to declare it as a private variable. There's no way to do this or purpose in doing this. Responding to your suggestion in the comments that you might be able to use double underscores (__x) analagous to Python: there's no way for Cython to generate C++ code that can access the private variable therefore there's no value in this.

As a general rule, Cython only needs to know about the parts of the public interface that you want to access. So if you don't need the other functions you can happily omit them too. I'll assume you do though.

Cython does have some understanding of C++ templates using square brackets. There are limitations here but you can cover most code:

When I create my_ven at least with conda 4.9.2 the environment seems to be empty.