Brian L. <br...@blucz.com> wrote: >> From this thread I gather that little or no progress has been made on >> addressing the root cause of this issue. It still seems to be broken >> with the latest 1.7 series packages. >> >> What is the proper method for getting this bug in front of the guys >> who maintain the openssh package? The cygwin website suggests that the >> mailing list is the proper channel, but it doesn't seem like anyone's >> seriously looking into this as an openssh issue. >> >> It's clearly affecting more than a few users and the workaround, while >> reliable, is quite lame. Can this please get a little bit more >> priority?
and another month goes by... If there is work going on behind the scenes, it would be nice to hear from the developer(s) working on it. If it is not being worked on... I agree with Brian. This is a serious impediment to using Cygwin 1.7. I would think it would be of top priority. Thanks. Kevin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple