reassign 236936 ssh
thanks

I have discovered that if I downgrade ssh from the latest 1:3.8p1-1
back to 1:3.6.1p2-9, the problem goes away entirely. So I am now
attempting to reassign this bug to ssh.


-jonathan



Reply via email to