test cases failed with python 3.6.6 about beefish HOT 7 CLOSED

Not sure, it seems to work fine for me on Python 3.6.3. What version of beefish?

from beefish.

Latest is 0.2.0

from beefish.

Maybe your pycrypto is out-of-date, also? This seems illustrative of a similar problem:

https://stackoverflow.com/questions/50302827/object-type-class-str-cannot-be-passed-to-c-code-virtual-environment

from beefish.

pycrypto                           2.6.1
beefish                            0.2.0

The issue was that beefish produces different output (credentials.yml.enc) every time with the same IV. Yesterday I have to use AES directly to work around this issue.

from beefish import encrypt_file, CIPHER_AES
__master_key = "aaa"
encrypt_file('credentials.yml', 'credentials.yml.enc', __master_key, cipher_type=CIPHER_AES)

from beefish.

Weird... On my machine (Python 3.6.5, PyCrypto 2.6.1 'final' and beefish 0.2.0) all the tests are passing.

I see from the StackOverflow link that someone else is running into a similar problem with Anaconda.

The issue was that beefish produces different output (credentials.yml.enc) every time with the same IV.

The IV is randomly chosen by beefish when encrypting a file (regardless of which cipher you use). The generate_iv() function returns a series of random bytes. So encrypting a file twice, even with the same passphrase, will return different output because the IV will presumably be different.

from beefish.

I added a new test in 42ccee7 that shows that beefish produces the same ciphertext when given 1) same input, 2) same passphrase and 3) same IV. The tests are passing for both blowfish and aes modes.

I'm not sure what to do as I can't replicate your issue or the error you initially reported.

from beefish.

Oh I see. The IV is written to the file. Sorry about this.

from beefish.