linux-kernel - RE: Kernel Debugging Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Aug 2014 19:40:15 +0000
From:	Paul Zimmerman <Paul.Zimmerman@...opsys.com>
To:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>
CC:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"Nyman, Mathias" <mathias.nyman@...el.com>,
	Nick Krause <xerofoify@...il.com>
Subject: RE: Kernel Debugging Support

> From: Valdis.Kletnieks@...edu [mailto:Valdis.Kletnieks@...edu]
> Sent: Monday, August 04, 2014 12:23 PM
> 
> On Mon, 04 Aug 2014 19:07:53 -0000, Paul Zimmerman said:
> 
> > Are you sure about that? Last I heard, xHCI debug support was a logo
> > requirement from Microsoft for Windows 8 and above, so I would have
> > thought that most vendors would have implemented it by now.
> 
> There's a lot of gear out in the real world that was manufactured before
> Windows 8 was released.
> 
> And the actual requirement, as listed at:
> 
> http://msdn.microsoft.com/en-us/library/windows/hardware/jj128256
> 
> doesn't actually require USB debug -it requires a debug port, and xHCI
> is below ethernet on the preference list.  As it says:
> 
> ---
> The next version of Windows will support several different debug transports.
> They are listed below in the preferred order of implementation.
> 
> Hardware Debugging Transports
> 
> Ethernet Network Interface Card from the supported list: http://msdn.microsoft.com/en-
> us/library/windows/hardware/hh830880
> 
> USB 3.0 - xHCI controller compliant to xHCI debug specification.
> 
> 1394 OHCI compliant Firewire controllers.
> 
> USB2 OTG (on supported hardware for Windows, recommend XHCI debug instead).
> 
> USB 2.0 EHCI debug (the debug enabled port must be user accessible). Legacy Serial (16550 compatible
> programming interface).

Ah, you didn't read far enough down the page :)

---
System.Fundamentals.DebugPort.USB.SystemExposesDebugInterfaceUsb
USB 3 system exposes debug interface that complies with Debug Port Specification
 
Target Feature
 System.Fundamentals.DebugPort.USB
 
Applies to
 Windows 8 Client x86, x64, ARM (Windows RT)
 Windows 8.1 Client x86, x64, ARM (Windows RT 8.1)
 Windows Server 2012 R2 x64
 Windows Server 2012 x64

Description

Systems that support USB 3 are required to have xHCI controller(s) compliant to the xHCI debug specification. The xHCI controller(s) shall be memory mapped.

There must be at least one user accessible USB 3.0 debug port on the machine.

...

Enforcement Date
 Mar. 01, 2012
---

So I have to believe there are a *lot* of systems out there that do support xHCI debug.

-- 
Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/