Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261846AbTEDXod (ORCPT ); Sun, 4 May 2003 19:44:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261847AbTEDXoc (ORCPT ); Sun, 4 May 2003 19:44:32 -0400 Received: from siaab1ab.compuserve.com ([149.174.40.2]:39102 "EHLO siaab1ab.compuserve.com") by vger.kernel.org with ESMTP id S261846AbTEDXob (ORCPT ); Sun, 4 May 2003 19:44:31 -0400 Date: Sun, 4 May 2003 19:55:57 -0400 From: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: [Announcement] "Exec Shield", new Linux security feature To: "H. Peter Anvin" Cc: linux-kernel Message-ID: <200305041956_MC3-1-375E-31DB@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 689 Lines: 15 > There is another issue: x86 uses relative jumps, so although "ASCII > armor" addresses aren't easily accessible using return address smashes > (although the \0 at the end thing is a real issue), you may be able to > get to them through a jump instruction. Does the instruction-pointer-relative data addressing mode added by AMD64 make these exploits easier? Maybe someone should be working on a version of this patch for that platform... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/