Dennis Kaarsemaker
Dennis Kaarsemaker
Ah, thanks for that. I'll push -f a fixed version in a bit. And no, I won't drop 2.4 support in patches I submit, as I need it :smile:
Rebased and updated to include the suggestion I made on #60.
@earl poke. Any comments?
Those interested in python 3 support: please test pull request #57. I've tested it myself and travis is green, but more eyeballs won't hurt :smiley:
I wouldn't object to doing that, but it's way too early to do such a hostile fork, my PR is only 3 months old.
You'll need to install graphviz for this to work.
[Note to self: the auto_connect logic is inverted, fixed in the policy-plugin branch, needs squashing before resubmitting]
One quite imporant thing to note (and the reason the tests fail on travis, but pass locally for me) is that libscrypt is quite new and may not be widely...
Hmm, and even with libscrypt vendored in (28c1ce780d8675ae49200cc1bddec0d93ab54e24 and 90f4670a166e22e93d92096100eea50aefbbcbca), [tests fail on travis' ancient (4 year old) containers](https://travis-ci.org/seveas/bitlbee/builds/112393414) as its gnutls is too old to understand AES-GCM.
Thanks for the review! bcrypt works too, will change to do bcrypt instead of scrypt. Initially I just went for what was considered best of breed, which seems to be...