Linked by Nathan Mace on Tue 19th Mar 2002 17:21 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



I was just configuring a new FreeBSD 4.5 system last night along with an OpenBSD 3.0 system and was running into this issue.
FreeBSD 4.5 and OpenBSD 3.0 were released before the OpenSSH / zlib bugs were found so those two things need to be patched before the systems could be considered safe to connect to the Internet. In OpenBSD this involved cvsing the latest patch cluster for the system and rebuilding the affected binaries. It wasn't this easy on FreeBSD. I had to look up the individual advisories and download each patch from different paths on the server because I couldn't find anything on their site as to how to do it any other way.
This is one of the places where OpenBSD's strict adherance to procedure and documentation made updating the OS much easier then it was under FreeBSD.