as the current nova requirements on the "master" branch are "paramiko>=1.16.0" (see http://git.openstack.org/cgit/openstack/nova/tree/requirements.txt?id=5bafd5fba508174f557acfeddbf85de0438c51d7#n24) i believe paramiko 2.0.0 will be pulled in for all future releases (though this also means that unit tests will break / are breaking as they were changed to ber with the original commit (that prompted this "bug" report) and need to change back to the original der.
@marco-voelz
as the current nova requirements on the "master" branch are "paramiko>=1.16.0" (see http:// git.openstack. org/cgit/ openstack/ nova/tree/ requirements. txt?id= 5bafd5fba508174 f557acfeddbf85d e0438c51d7# n24) i believe paramiko 2.0.0 will be pulled in for all future releases (though this also means that unit tests will break / are breaking as they were changed to ber with the original commit (that prompted this "bug" report) and need to change back to the original der.
@all
for the record my PR (see https:/ /github. com/paramiko/ paramiko/ pull/572) was not merged, but the larger pycrypto- to-cryptography PR (see https:/ /github. com/paramiko/ paramiko/ pull/394), which obviated my PR, was merged and present in paramiko 2.0.0.