libssh followup

Yannick- I'm curious how much headway you've made into libssh cause....well.... um.... I got impatient.... First off, the library you forwarded to me was version 0.1, but the guy's site is (slowly) comming back online and I was able to get version 0.11 from him. Since then I've implemented an sftp:// fopen/opendir wrapper, and a resource/object based interface (a la mysqli's dual interface). Extending it to scp, pty, and other subsystem support will be a trivial matter at this point. Anyway, I don't want to steal your thunder (great find on this library btw), but if you're not very far anyway, I'd just as soon submit the package I've got together and then we can both put our collective effort into improving/maintaining it. While you chew on that I should mention that I've found some....issues with libssh. #1 namespace issues cause the md5 routines used by ssh_pubkey_get_hash to miss a byte alignment and crash out. #2 It doesn't make any concerted effort to locate openssl during ./configure and consequently (on any system which doesn't have everything in specific paths) has no support for any >actual< crytography making key exchange a futile attempt. Maybe you've come across one or both of these issues already. I'm cataloging these and other (less major) issues to submit a patch to the library maintainer. Wez- FYI: libssh is licensed LGPL, shouldn't be an issue, but there it is on your radar oh King of PECL. -Sara