From owner-freebsd-questions@FreeBSD.ORG  Fri Feb 20 23:12:10 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B4E7A60A
 for <freebsd-questions@freebsd.org>; Fri, 20 Feb 2015 23:12:10 +0000 (UTC)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com
 [IPv6:2607:f8b0:4003:c06::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7AE30A4B
 for <freebsd-questions@freebsd.org>; Fri, 20 Feb 2015 23:12:10 +0000 (UTC)
Received: by mail-oi0-f41.google.com with SMTP id z81so5187031oif.0
 for <freebsd-questions@freebsd.org>; Fri, 20 Feb 2015 15:12:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=ntOIrPG/Ni+UnHWZbvhkuYDVqOsjdyGeLp5fRzn7rBM=;
 b=ZfW/Q0uF7M1fj6iIS8aTe49+P7nRZCZ3+UguVSU6WU5Prx6u0Xb0PqzY7AOwKlQED0
 6moAI8Rs3QbinoOLKpDu7+HUZeJig31cB6mnKfIJ5y2iK3BB7VkqiWlPnb0WLXHWeyv1
 HP2mbtoLtotbcOPzzwHKynx2+5dHNZTIb1N5Cxl03P6/kGhnHfeU9ywP7q9bSXVuJuJh
 2JddxlUO6TLqPGo0pWDoATgsq6WycSzUgaKy3GlM3JMNgRkLkw09KyrxQl2Wi2+5InFD
 QTdFOoCz2yUBY1qHcBWbpNQrTBB7Lq5OsbpyaXKQ+HNJLC76VnXKntw1TAkghd7TxxuI
 J2Ng==
MIME-Version: 1.0
X-Received: by 10.182.165.202 with SMTP id za10mr137494obb.8.1424473929816;
 Fri, 20 Feb 2015 15:12:09 -0800 (PST)
Received: by 10.60.140.199 with HTTP; Fri, 20 Feb 2015 15:12:09 -0800 (PST)
Date: Fri, 20 Feb 2015 18:12:09 -0500
Message-ID: <CAD2Ti2_ztSG4-eirWJ3UepNhJiteMqvKQmuq3S4zqOL+ujxOfg@mail.gmail.com>
Subject: trojans in the firmware [How can protect my drive]
From: grarpamp <grarpamp@gmail.com>
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 23:12:10 -0000

There is a ongoing thread linked below about enhancing freebsd
kernel to only permit those opcodes needed for production use of
disk / usb / bios, and to filter out all others (of which firmware
updates, vendor specifics, fuzzing/bashing are all therefore blocked).
This obviously only for the system is clean to begin with, and not
bulletproof, but is defense in depth.

http://docs.freebsd.org/mail/current/freebsd-security.html