paramiko

Sorry, it's GNU LGPL. https://github.com/paramiko/paramiko/blob/main/LICENSE IANAL, and I didn't ask for an explanation, but I suspect the problem was that I was making a library, which, from my uneducated reading, would qualify as a derived work. I know our company is especially strict since, from my understanding, significant enough money has already been spent on legal fees.

https://github.com/paramiko/paramiko/issues/1283 Same bug in python ssh library.

Apparently there was an almost identical vulnerability in the Python SSH library Paramiko too: https://github.com/paramiko/paramiko/issues/1283

Use Paramiko (Python) to code a quick server based on : demo_server.py Share what is typed between clients using fifo, shared file (bad!) or SQLite. See: https://github.com/paramiko/paramiko/blob/master/demos/demo_...

Good stuff. Take a look at Fabric for another (and very commonly-used) example of Python wrapping SSH: http://docs.fabfile.org. Also you might look to Paramiko for a native SSH implementation: https://github.com/paramiko/paramiko.

It seems like in the time I've been using python (about 18 months, really) the community has really stepped up the pressure to switch to 3.x. The vast majority of what I use day-to-day has now been ported (just noticed Paramiko support has been merged to master two days ago[1], so Fabric'll follow rapidly after that), and every time I see a new book come out it demands Python 3. I will try to be a good boy and use it going forward (I already find it more useful for CSV and other file I/O type tasks thanks to the unicode support, but am reliant on mysql for some routine drudgery as well). [1] https://github.com/paramiko/paramiko/pull/276

There's no silver bullet, but NumPy comes pretty close sometimes. Here's an example where I achieved a 300x speedup with regular old CPython: http://stackoverflow.com/questions/17529342/need-help-vector... The trick is often to somehow get Python to hand the "real work" off to something implemented in C, Fortran, C++, etc. That's pretty easy for a lot of numerical and scientific applications thanks to NumPy, SciPy, Pandas, PIL, and more. Lots of libraries are exposed to Python, and you can expose more either by compiling bindings (see Boost.Python) or using ctypes. If you do this well, nobody will notice the speed difference, yet your code will still look like Python. And sometimes your performance problem is not Python's fault at all, such as this lovely performance bug: https://github.com/paramiko/paramiko/issues/175 - a 5-10x speed

Fabric is on the way. Paramiko, the ssh library underlying Fabric, now has a Python 3 PR for which all tests pass: https://github.com/paramiko/paramiko/pull/233

How many people have reviewed Paramiko? In particular, how about that ecdsa patch[1] to Paramiko that you'll need to be accessing modern Ubuntu or Fedora (and before long, RHEL/CentOS). What about the python-ecdsa[2] (that paramiko's provisional support for modern Fedora and Ubuntu's default configs is based on)? This entry from its README seems pretty frightening: This library does not protect against timing attacks. Do not allow attackers to measure how long it takes you to generate a keypair or sign a message. This library depends upon a strong source of random numbers. Do not use it on a system where os.urandom() is weak. I'm not saying Paramiko (or its patch sets) are insecure, just pointing out that the same arguments can be made against the libraries and code that Ansible is based on. [1] - https://github.com