From owner-freebsd-security@FreeBSD.ORG Mon Nov 7 22:41:07 2005 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2828916A423 for ; Mon, 7 Nov 2005 22:41:07 +0000 (GMT) (envelope-from full-disclosure@csilva.org) Received: from jupiter.nswebhost.com (jupiter.nswebhost.com [72.9.236.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B0843D4C for ; Mon, 7 Nov 2005 22:41:05 +0000 (GMT) (envelope-from full-disclosure@csilva.org) Received: from 55-246.dial.nortenet.pt ([212.13.55.246]:34801 helo=[192.168.1.10]) by jupiter.nswebhost.com with esmtpa (Exim 4.52) id 1EZFfY-0000aq-Sm for freebsd-security@freebsd.org; Mon, 07 Nov 2005 17:40:53 -0500 Message-ID: <436FD807.7080008@csilva.org> Date: Mon, 07 Nov 2005 22:41:11 +0000 From: Carlos Silva aka |Danger_Man| User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-security@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - jupiter.nswebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - csilva.org X-Source: X-Source-Args: X-Source-Dir: Subject: Security updates without rebooting X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 22:41:07 -0000 Hello all, Can someone explain how to apply security patches on the system without rebooting the machine? I guess that I cant patch the kernel without compiling and rebooting the machine, so the only way is with iptables and keeping the daemons "fresh"? Regards, Carlos Silva, http://osiris.csilva.org/