From owner-freebsd-security@FreeBSD.ORG Fri Dec 2 05:24:21 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 1CCA516A41F for ; Fri, 2 Dec 2005 05:24:21 +0000 (GMT) (envelope-from dr2867@pacbell.net) Received: from smtp109.sbc.mail.mud.yahoo.com (smtp109.sbc.mail.mud.yahoo.com [68.142.198.208]) by mx1.FreeBSD.org (Postfix) with SMTP id 449B543D5C for ; Fri, 2 Dec 2005 05:24:18 +0000 (GMT) (envelope-from dr2867@pacbell.net) Received: (qmail 24467 invoked from network); 2 Dec 2005 05:24:17 -0000 Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@68.126.181.25 with plain) by smtp109.sbc.mail.mud.yahoo.com with SMTP; 2 Dec 2005 05:24:17 -0000 Message-ID: <438FDA92.4080306@pacbell.net> Date: Thu, 01 Dec 2005 21:24:34 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 5.4-RELEASE-p7; en-US; ja-JP; rv:1.7.12) Gecko/20050915 MultiZilla/1.6.2.0c Mnenhy/0.7.2.0 X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: iwan@staff.usd.ac.id References: <52765.202.65.114.229.1133424317.squirrel@webmail.usd.ac.id> In-Reply-To: <52765.202.65.114.229.1133424317.squirrel@webmail.usd.ac.id> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-security@freebsd.org Subject: Re: exploiting kernel 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: Fri, 02 Dec 2005 05:24:21 -0000 At about the time of 12/1/2005 12:05 AM, iwan@staff.usd.ac.id stated the following: > Hi, > Can kernel's freeBSD exploited by tools hacking ? If true, > can I know how to fix this problem, and what tools can do > that. > > Thanks alot > > > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" > Absolutely. There is no such thing as bug proof software. All software has bugs or flaws in them. Generally, when a security related bug is discovered, the programmers fix the problem, then make a patch available by any one of several means. Then a security advisory is issued. As for the bug, it depends on the nature of the bug to determine how to exploit it. Unchecked buffers are suseptible to buffer overflow attacks, etc. It all depends on the nature of the code and any details that the programmer overlooked. Even well written software, when subjected to different types of abuse, will fail in unexpected and spetacular ways. Unfortunately, you cannot secure against future unknown security problems in software. The best that you can do it mitigate the risks of compromise as much as possible by using ACLs, chflags, securelevel, jails, and other security related features of the operating system. The other participents on this list have provided you with a number of resources to secure your system. I strongly suggest that you use them. Later. -- Daniel Rudy