Re: libssh followup

For those of you wondering where my ssh extension is, here's the low-down. The md5 symbol conflict turned out to be only the tip of the iceberg. The only reason my build was operating was because of some very delicate library juggling which aren't realistic to expect from end users. I've also since discovered an entire host of thread safety and memory allocation issues. Bottom line, I'm rewriting this library. I considered submitting a mega patch to the maintainer, but there really are just too many issues to resolve without reconstructing significant bits. I'm using his implementation of ssh as a roadmap, but all the code is new (not sure what that means in terms of licensing, probably falls under "derivative works"). It means it'll be an extra couple weeks before we see an extension, but when we do it'll be one which plays much nicer. -Sara