Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Nov 2005 00:55:05 -0800
From:      Colin Percival <cperciva@freebsd.org>
To:        suporte@wahtec.com.br
Cc:        freebsd-security@freebsd.org
Subject:   Re: More on freebsd-update (WAS: Is the server portion of freebsd-update open source?)
Message-ID:  <43672D69.2000208@freebsd.org>
In-Reply-To: <200510311625.46334.suporte@wahtec.com.br>
References:  <20051030120107.CD5CF16A422@hub.freebsd.org> <200510311625.46334.suporte@wahtec.com.br>

index | next in thread | previous in thread | raw e-mail

suporte@wahtec.com.br wrote:
> 1- if and when freebsd-update will be the official freebsd system binary 
> update? Like, when it will be part of freebsd structure, with a dedicated 
> server and stuff? ... It's far better then updating by cvs.

FreeBSD Update is now semi-officially supported, in the sense that I make
sure that it works but the rest of the security team isn't involved.  As I
mentioned earlier, I'm planning on rewriting the build code to make it far
simpler and more reliable; this will make it possible for someone else to
take over if I get hit by a bus, at which point FreeBSD Update will become
officially supported. :-)

> 2- for future plans,  is there any possibility to customize or add some 
> features to kernels on official freebsd-update server? IPSEC is quite 
> important on security.  Since there isn't a LKM to use IPSEC (correct me if 
> I'm wrong), when someone compiles the kernel to add it, he looses the 
> freebsd-update kernel update. 

Right now I provide prebuilt GENERIC and SMP kernels; I could build some
other kernel configurations, but there's obviously a limit to what is
practical.  After I rewrite the build code I'll have to consult with the
release engineering team and the user community about which kernels would
be most useful.

Colin Percival


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43672D69.2000208>