I'm not sure what the cause of the problem is, after all. It occurred once again with ssh 1:3.8.1p1-8.sarge.3 (both server and client) while the network was temporarily unstable (I've been told by the admin that this was due to spanning-tree announces). -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA