From owner-freebsd-security@FreeBSD.ORG Mon Jun 5 13:14:27 2006 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 6B3F716AE4B for ; Mon, 5 Jun 2006 13:14:27 +0000 (UTC) (envelope-from artifact.one@googlemail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C8B143D64 for ; Mon, 5 Jun 2006 13:14:25 +0000 (GMT) (envelope-from artifact.one@googlemail.com) Received: by py-out-1112.google.com with SMTP id m51so1385531pye for ; Mon, 05 Jun 2006 06:14:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=anX4rl1hhHn/yILevHr/dFBxKHlTpaoEcHbSw1D3fdd5d3ftUHcuOPm0QoSz77zdVzxarjnIn5yOhAOA2FEVke7Cm3EdGEwttqd08kDTuivpBXWYGZulfLSJQxnuqw8WDlRhl67ka/yj4F7xe56NOpsg6nTlm9TY6EX+/uU7wG4= Received: by 10.35.18.4 with SMTP id v4mr6394520pyi; Mon, 05 Jun 2006 06:14:24 -0700 (PDT) Received: by 10.35.121.7 with HTTP; Mon, 5 Jun 2006 06:14:24 -0700 (PDT) Message-ID: <8e96a0b90606050614l26db50f2nfcb26669d02a7ad9@mail.gmail.com> Date: Mon, 5 Jun 2006 14:14:24 +0100 From: "mal content" To: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: PE disassembler for unix 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, 05 Jun 2006 13:14:32 -0000 Hello, I'm looking for a disassembler to examine a malicious Win32 binary on FreeBSD. Does anybody have any favourites? I see pedisassem in ports, but it looks to be broken and unmaintained (it crashes with a floating point error, currently). MC