[ignore this - see edits] i thought one problem with ssh was that it used tcp and too-large packets. hence that other thing that builds on top of it, and whose name i can't remember. having said that, i'm sure there is side channel info - i'm just not sure how precise things are.
also, what cipher suite does ssh use. does it have forward secrecy?
[edit1: to answer that last question; yes it does.]
[edit2: paper on keystroke timing attack - http://users.ece.cmu.edu/~dawnsong/papers/ssh-timing.pdf - each keystroke is a packet; passwords have no echo. this is from 2001 - it has suggestions like sending packets when idle, but i don't think they've been implemented.]
Comments
[ignore this - see edits] i thought one problem with ssh was that it used tcp and too-large packets. hence that other thing that builds on top of it, and whose name i can't remember. having said that, i'm sure there is side channel info - i'm just not sure how precise things are.
also, what cipher suite does ssh use. does it have forward secrecy?
[edit1: to answer that last question; yes it does.]
[edit2: paper on keystroke timing attack - http://users.ece.cmu.edu/~dawnsong/papers/ssh-timing.pdf - each keystroke is a packet; passwords have no echo. this is from 2001 - it has suggestions like sending packets when idle, but i don't think they've been implemented.]