<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">There are a few places within Conch which currently export PyCrypto objects as part of a public interface in Twisted.</div><div class=""><br class=""></div><div class="">These include:</div><div class=""><ul class=""><li class="">twisted.conch.ssh.keys.Key.keyObject</li><li class="">twisted.conch.ssh.keys.objectType</li></ul></div><div class="">I'm working on a ticket - <a href="https://twistedmatrix.com/trac/ticket/7413" class="">https://twistedmatrix.com/trac/ticket/7413</a> - to eliminate the dependency on PyCrypto. Right now, in that branch, those objects are Cryptography key objects instead of PyCrypto key objects.</div><div class=""><br class=""></div><div class="">It is <i class="">possible</i> to preserve compatibility with keyObject, and we could deprecate and then remove objectType, with conditional dependencies on PyCrypto. But before I go through the effort there, I'm wondering if any users of conch actually care.</div><div class=""><br class=""></div><div class="">-glyph</div><div class=""><br class=""></div></body></html>