Nope, current.
my entire userland isn't in sync, however, because current is broken for
this machine. it panics trying to startx. hence, my kernel is at 1.6A until
somebody fixes it... i've received no responses to my PR. perhaps i'll try
to get a core and followup...
but I have updated ssh and such, and still see 3.2.1.

On Tue, Jun 25, 2002 at 08:51:51AM +0900, itojun@iijlab.net wrote:
> >Shouldn't we have 3.3 in basesrc/crypto/dist/ssh now? I know I saw commits
> >yesterday (or perhaps the day before) saying it was updated to 3.3, but
> >after a CVS update just now, I still get 3.2.1. I updated crypto/dist/ssh
> >and usr.bin/ssh, and see no differences. Am I doing something wrong?
> 
> 	are you on 1.6 branch?  1.6 branch has 3.2.1 with privilege separation
> 	on by default.
> 
> itojun

-- 
/~\ The ASCII                         Sean Davis
\ / Ribbon Campaign                    aka dive
 X  Against HTML
/ \ Email!                   http://endersgame.net/~dive/