Xterm, and um, kerberos, kinda

This past week, we released security updates for xterm. Kerberos got a bit of a clean up, and 1.4 finally got unmasked. That was fun. OK, so I need a favour. Can the people who’ve tried to use xterm-202 please report as to what went wrong with it? Like, the different behaviour in Gentoo, as compared to xterm-200. Please report in your comments to the blog, rather than bugzilla. The reason I ask this is that xterm-202 behaves really badly for me. And Thomas asked me to send him debugging output for both 200 and 202 weeks ago, but I haven’t had the time.

The nice thing is that at work, I’ve been learning how to deploy subversion and trac for a specific subset of our developers. Maybe we’ll get to show off how nice it is (I really like them both so far!), and the main development stuff can move over to those as well in the future? Here’s hoping. Also, started deploying OpenVPN. The first guinea pigs are trying this weekend. Well, we got some USB keys this past week, so I was able to generate certificates for people and then have them take those home on the keys (after they entered passphrases). I also generated some ssh keypairs for some people to remotely log in. Now, we can have remote access capabilities start to come back up.

More this week.

2 thoughts on “Xterm, and um, kerberos, kinda”

  1. I’ve had severe problems with xterm-202 that made me mask it out. Scrolling is uneven, choppy and unpredictable, especially on a loaded system (mine is a Pentium-III @ 870MHz). No such problems with xterm-200-r1, even under high system load (like compiling KDE in the background) – it just stays responsive.

    The issue is documented in Bugzilla Bug 92438

  2. As I recall, xterm-202 hosed cluster-ssh, which I use constantly. I don’t remember the exact nature of the breakage, other than “didn’t work”.

Comments are closed.