OpenSSH 4.0 & Portable OpenSSH 4.0p1 Released
UnderScan writes "As seen on openssh-unix-announce: 'OpenSSH 4.0 has just been released. It will be available from the
mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. We would like to thank the OpenSSH community for their continued support to the project, especially those who contributed source and bought T-shirts or posters.' See the changelog or the freshmeat.net changes summary for more details."
Hasn't hit ports. :\
Karma: Chameleon (mostly due to the fact that you come and go).
I just updated to something like 3.95pl1 last weekend.
Now I get to do it again....
There sure is a lot to timing isn't there.
Have you compiled your kernel today??
MD5 (openssh-4.0p1.tar.gz) = 7b36f28fc16e1b7f4ba3c1dca191ac92
Source: http://www.undeadly.org/cgi?action=article&sid=200 50309172736
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
To my understanding Openssh is still the same 2.0 protocol. Not like a new 4.0 protocol. Correct me if I am mistaken....
One feature I have been waiting for is the ability to chroot my users when they log in, even if just for file transfers. This would ensure that users would not be able to wander the entire directory tree of the server. I have had some success (on FreeBSD) with creating single jail for all client logins, and then applying some clever directory permissions for the higher directories (usualy o-x for directories). There was a commercial version of SSH that had a chroot feature, but I would prefer to stick with openssh. IMHO, this is the one area that FTP outdoes SFTP (but not enough for me to dumb my security down and allow FTP!!).
Any other ideas?
Tab completion in sftp!
I don't use sftp nearly as much as I would if I could actually navigate and download files with any efficiency instead of copying and pasting...
This is 2005, come on.
"Does anyone else find it a bit odd that 4.0p1 is listed as Minor Feature Enhancements, yet it gets a whole-digit version bump?"
The last release was 3.9. They simply rolled over to a new major number. Also, I think it's justified. Connection multiplexing was introduced in 3.9, but now it's had the major bugs fixed and so might be considered "stable". It's a big feature.
I rarely criticize things I don't care about.
A new release of Gnome got the front page, but a new release of OpenSSH doesn't? Someone's priorities are out of wack.
-d
"Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
It got a whole-digit bump because we ran out of minor digits and don't want double-digit minor version numbers (or hex :-).
$ find
That would be hpn-ssh. No, it's not in 4.0. Will it be included in future releases? Maybe, it needs to be looked at more closely.
$ find
I have OpenSSH 4.0p1 running on a variety of OSes, all built against OpenSSL 0.9.7e. They're all built with a standard ./configure and no other options, and just X11 forwarding in the ssh_config file. Whenever I connect to a system followed by another system, regardless of the SSH server version running, after I put in a password, it pauses for a full 5 seconds every time with the following (from ssh -vv):
/usr/X11R6/bin/xauth -f /tmp/ssh-PZhTm22307/xauthfile generate unix:10.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null /usr/X11R6/bin/xauth list unix:10.0 . 2>/dev/null
debug2: x11_get_proto:
(pause 5+ seconds here)
debug2: x11_get_proto:
This doesn't happen on any system that I'm logged in to locally and initiate a connection, but if I jump from one machine to another with X11 forwarding turned on, the second machine is always doing this 5-second pause. This is most easily reproducible if I SSH to localhost twice in a row (one connection within another).
Interested in open source engine management for your Subaru?
Does ./configure handle cross-compile situations correctly yet?
... test.
For example, I want to build OpenSSH on an i386 Linux for an embedded MIPS Linux. Configure will detect that it is cross-compiling, but will still insist on performing its compile-and-run tests, either by erroring when it tries to run the MIPS binary on i386, or by saying it won't proceed any further because I'm cross-compiling which means it can't do its
I had to tediously hand-edit the configure script to shut off those errors (I lost count of how many instances) -- after which everything worked fine. But with each new release, I will need to edit that script again, which I don't enjoy.