Particularly, you should try it if you're interested in PAM fixes or Kerberos/GSSAPI support. If you have access to an unusual system or configuration then tests on those are particularly helpful since we can't test all of them.
You can see the bugs that ought to be fixed before 3.8
Hmm, this asking-for-testing thing usually gets only limited responses, since most people prefer to complain after the event. Maybe I should try a little reverse psychology...
There will be a new OpenSSH release soon. Under no circumstances should you try a snapshot. You especially should not test it if you're interested in PAM fixes or Kerberos/GSSAPI support. This goes double if you have an unusual system or configuration, because since we're psychic we always know what's going to break on system's we've never seen or heard of, and magically know what to do to avoid problems.
Yeah, that ought to do it :-)
More OpenSSH hacking. I'm trying to figure out why the new(ish) PAM chauthtok via keyboard-interactive code displays the PAM messages properly on some platforms (Redhat, AIX) but doesn't on others (Solaris, HP-UX). I added some instrumentation to the PAM code to help debug it and spent some time poking sshd with a debugger, but without definitive results. It seems to be related to to message "style" set by PAM when responding to the request, but needs more investigation.
I also noticed a problem whereby the if the PAM authentication thread dies without completing the authentication (either success or failure), sshd will block indefinitely for that session. I have a fix for that, which will go in once a few style nits are sorted out.
Spent a little time looking at dropbear, another SSH2 server implementation. While fiddling with it I got it running on HP-UX, fixed what I suspect was a bug and sent the patch for both back to the author.
Closed a bunch of OpenSSH bugs that had either already been fixed, or the reporters had not followed up with requested information, and updated a few more.
My family is visiting for Christmas, but it still feels like there should be a week or two until then...
Sifted through 350 messages waiting in my Inbox. There's a few OpenSSH-related things still to be dealt with, but most could be filed. Started looking at the outstanding PAM-related issues.
After the Swen.W32 spam-a-thon (which peaked at 1 every 30 seconds or so, see previous diary entry) I've made my spam filtering more savage and for the first time I'm sending spam straight to the bit-bucket (anything scoring 15+ on the spam-o-meter). It seems like admitting defeat. I used to report every spam I got, then when I started using spamassasin, just the ones that got past it. I rarely got a response. Now I just use spamassassin -r to submit any getting past the filters to DCC. If it wasn't for filtering, my email would be totally unusable. Even that only reduces the human cost and hides the bandwidth and storage costs. The spam didn't start until I started posting to public mailing lists and has got steadily worse. I guess it's the cost of working on a public project.
Sigh. Another day, another freakin' Windows worm. I've already got several megabytes of the damn thing.
Daz's SpamAssassin tip of the day:
echo "score MICROSOFT_EXECUTABLE 10.0" >>/etc/mail/spamassassin/local.cfWhy this isn't the default I don't know.
Now all I need to do is work out if I can filter it before I download them.
Update: 80 copies in 5 hours (about 12MB worth of crap). I think I'm hit worse than normal because I've been more active the SSH mailing lists in the last couple of days, so I'm more likely to be selected as a target.
I just set a size limit in fetchmail (limit 130000 in .fetchmailrc) so at least I don't have to download the suckers. I will have to clean out the mailbox periodically, though.
I've seen release circuses before, I even had a ring-side seat for the last one, but this is my first from inside the ring.
In case you've been living under a rock, you've probably heard that OpenSSH has some buffer management issues. The jury is still out on whether or not it's explotable, but regardless, there was a massive scramble for release. If you haven't already, you should apply the patch or upgrade.
Naturally, since it was a rush release, there was breakage. Despite requests to test for the impending release, it looks like no-one with (IRIX, Tru64, BSDi, MacOS X) ever tested it and those are all broken. There are also other issues with certain configurations (including, sadly, one I'm responsible for). You can check the score over at bugzilla. Meanwhile, the list server is melting down (currently ~12 hours behind, but still delivering!)
By coincidence, my next job was postponed by the customer (again!), so I've been on deck juggling as many of the bug reports as I can. If you get only a terse response from me (or none), that's why.
OpenSSH is now in a feature freeze for the 3.7 release. We're down to the testing and shaking out bugs, so if you have a platform you'd like it to work on, please grab a snapshot from a mirror near you and try it (and report any problems you find).
I haven't seen the proposed release notes yet, but the kind of things that have changed (in no particular order) are:
Since I'm a sucker for oddball OSes, and GNU HURD seems odder than most, I was also going to have a look at why PrivSep doesn't work on it. Unfortunately, it appears that since the GNU ftp server was h4x0red, the HURD packages were taken offline and no one can currently install a HURD system. Oh, well, maybe later.
You can verify a host key like so:
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub
It's documented in the man page for ssh-keygen.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!