Ok, not really, since SSH has made my life much simpler than it would be otherwise, but really, it has some usability issues.
And I mean real usability issues, not the usual crap.
It can't be integrated into kdewallet
While there is a mechanism to have a GUI asking the password, this helper app (askpass) doesn't get any session info, so it's meaningless, unles you are trying to directly start a X app over ssh.
Which you probably aren't.
Fingerprint management sucks.
Suppose you have a firewall. You keep port 22 as a way to log into it, and forward port 23 to a mail server in the DMZ. Well, it will complain and print huge, scary warnings each time you login into one or the other, depending on which one you used first.
Or, it can simply refuse to connect.
And that's just the easy two.
What can be done?
Take the dropbear client (not openssh, dropbear code seems simpler), and put a putty-like UI into it. Use the konsole kpart for display.
Take the GTK version of Putty and hack it into KDE shape, put kdewallet in it. I don't quite like the idea of having a seaparate, different terminal app for remote sessions.
I would probably go the dropbear route if:
I had a working PyKDE (maybe someday)
The idea of delving into someone else's C code didn't make me nauseous. (probably after I surgically remove my sense of taste).