Paramiko depends on RandomPool
Bug #271791 reported by
John A Meinel
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
paramiko |
Confirmed
|
Medium
|
Robey Pointer | ||
paramiko (Ubuntu) |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
On Win32 paramiko is very slow to start, because it uses PyCrypto's RandomPool object. However, there are no plans to improve RandomPool because it seems it is deprecated. See bug #248522.
Is RandomPool actually needed? Accessing in on win32 adds 1-2 seconds of startup overhead.
Related branches
Changed in paramiko: | |
assignee: | nobody → robey |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in paramiko: | |
status: | Triaged → Fix Committed |
Changed in paramiko (Ubuntu): | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
To post a comment you must log in.
As a follow up to this, pycrypto 2.1.0 has now been released. Which introduces a different way to get random data. It then wraps RandomPool in the new functionality, and issues a deprecation warning.
It would be nice if paramiko would detect the new functionality is available, and use it instead.