Re: Why update the world because of OpenSSH?

From: Christopher Schulte (schulte+freebsd@nospam.schulte.org)
Date: 04/01/02


Date: Mon, 01 Apr 2002 00:47:52 -0600
To: Larry Vaden <vaden@texoma.net>, Nathan Reilly <nathan@bbuzzed.cx>
From: Christopher Schulte <schulte+freebsd@nospam.schulte.org>

At 12:35 AM 4/1/2002 -0600, Larry Vaden wrote:
>Am I correct in assuming that RELENG_4_5 changes from time to time?

Yup. Whenever critical (security) changes are committed.

>If that is the case, how does one build 4.5-RELEASEp2 without the exposure
>of mods since that release?

The current state of RELENG_4_5 is 4.5-RELEASE-p2. That basically means
there have been 2 changes to RELENG_4_5 since 4.5-RELEASE came to be. As
soon as another commit is made, it will be known as 4.5-RELEASE-p3. You
simply synchronize to RELENG_4_5 and get the most current -px state.

/usr/src/UPDATING documents the changes made, once you cvsup your sources.

>thnx/ldv

--
Christopher Schulte
http://www.schulte.org/
Do not un-munge my @nospam.schulte.org
email address.  This address is valid.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message


Relevant Pages

  • Re: FreeBSD NAT-T patch integration
    ... As Bjoern said in another mail, we're talking about security. ... Yes, I'm doing most of IPSec / NAT-T stuff at work, but it is mainly ... commit the patch", it would already have been done, and we would have ...
    (freebsd-net)
  • Re: Administrivia: Discussion - Making this list subscriber-only
    ... >> Most of the real FreeBSD security experts avoid this list (or treat it ... I'm not stopping folks from reading the list. ... > the faq/doc/handbook and commit it. ... > An security related one is missed at the moment. ...
    (FreeBSD-Security)
  • Re: [stable] Linux 2.6.25.10
    ... consciously do *not* report the security impact of said bugs ... the whole security circus you surely do use their terms as bogeymen ... to catch the latest and greatest security fixes? ... if i submitted a security fix with the commit message ...
    (Linux-Kernel)
  • Re: Is 4.3 security branch officially "out of commission"?
    ... May I merge them into 4.3 security branch without my ... > commit any change to a _RELEASE tag. ... tag should never ever, ever be touched. ... can also approve non-security changes that are deemed critical ...
    (FreeBSD-Security)
  • Re: cvs commit: src/games/fortune/fortune fortune.c
    ... not get involved in a commit war. ... > the real problem, we shouldn't mask it. ... > from a security point of view. ... So it's better to back perfectly valid code rather than to look for ...
    (freebsd-current)