Added "pycrypto" as the required dependency

[atykhonov]

No description provided.

[mkushnir]

This is a quick fix. But wouldn't it be better in the upstream shrapnel to replace Crypto.* in its ssh implementation with coro.ssl?

[atykhonov]

Yes, this is a quick fix.
For now, this is a fact that shrapnel requires pycrypto. So I added it into the install_requires with hope that this will save someone else some time to figure out which exactly required dependency is missed..

[samrushing]

Actually I prefer pycrypto over openssl. Openssl is an abomination that must be avoided at all cost.

[mkushnir]

I'd be curious why openssl is in such a disfavor...

[samrushing]

This is just my personal opinion, but openssl is the poster child for everything that is broken in the C language.
One of my biggest complaints is around pointer ownership, several of the API's use conflicting/confusing design for pointer ownership, and it's always full of surprises. Stopping openssl from leaking is a challenge.

One of my fantasy projects for Irken is to write a TLS library with a C API, where the fact that there's a GC is completely hidden from the end user, who would use a simple handle to represent ownership. Free the handle, and everything related to the connection goes away.,