From owner-freebsd-usb@freebsd.org  Mon Mar 19 19:30:09 2018
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0D68F66286
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Mon, 19 Mar 2018 19:30:09 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 718B08086A
 for <freebsd-usb@freebsd.org>; Mon, 19 Mar 2018 19:30:09 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.128.70])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 461692602F6;
 Mon, 19 Mar 2018 20:30:07 +0100 (CET)
Subject: Re: usb's quirks ... how to sniff bios'es messages addressed to usb
 rom chip
To: Vincenzo Di Salvo <ingegneriaforense@alice.it>, freebsd-usb@freebsd.org
References: <!&!AAAAAAAAAAAYAAAAAAAAANB1sR69XHJMoG+MU1AT/qLCgAAAEAAAAP7hvnBBMjhJr+v0J6Z9h1UBAAAAAA==@alice.it>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <77f62042-bb44-7b36-0845-b88d233bfed0@selasky.org>
Date: Mon, 19 Mar 2018 20:30:02 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAANB1sR69XHJMoG+MU1AT/qLCgAAAEAAAAP7hvnBBMjhJr+v0J6Z9h1UBAAAAAA==@alice.it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 19:30:10 -0000

On 03/19/18 19:46, Vincenzo Di Salvo wrote:
> Hello guys,
> 
>   
> 
> reading the FreeBSD forums I learned about the usb freebsd mailing list.
> 
>   
> 
> I try to explain my question.
> 
>   
> 
> Plugging in an hard disk into the usb port (without mounting the
> filesystem), I've noticed that the inserting operation was detected by the
> chip and a counter inside the HD memory was increased by one each time the
> hard disk was inserted.
> 
> So a write operation has been happen !!!!!!
> 
> The drive in question is a solid hard disk SSD 1TB Samsung 850 EVO Sata III.
> 
> 
> This test has been done on a Linux O.S (that is a very disaster in terms of
> security policy, due to the demons of the GUI !)
> 
>   
> 
> This sounds like something done by the BIOS. Some can keep track on a wide
> variety of things. For example, it happens that the Bios keep track of the
> times when the case is opened.
> 
>   
> 
> QUESTION:
> 
>   
> 
> Is the FreeBSD usbdump(8)  the right way to listen on events coming from
> bios (in this case a writing access) and show changes happened into the rom
> memory of the chip of the usb HD ?
> 
>   
> 
> Appreciated is any your help also about the correct sintax of the usbdump.
> 

Hi,

usbdump has a manual page, man usbdump, describing how to use it.

There is also a Google Summer of code project to add wireshark support 
for the FreeBSD usbdump format.

--HPS