Lockable Storage Device Study Group

Curtis Stevens curtis.stevens at wdc.com
Wed Oct 12 13:48:58 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Curtis Stevens" <curtis.stevens at wdc.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5CF6E.5E031A98
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I have had several inquiries about the purpose of this study group.

=20

There is work going on within USB to enable a capability that allows =
the
device to prevent access to user data.  The possible capabilities are =
as
follows:

=20

1.	Mechanism to detect that the device can prevent media access
2.	Mechanism to define a password(s)
3.	Mechanism to prevent access to user data areas the works across
power cycles
4.	Mechanism to allow access to user data areas
5.	Mechanism to gain access if passwords are lost
6.	Mechanism to cause OSes to prompt for a driver if they do not
natively support this capability

=20

I think that defining mechanisms for turning on the passwording as well
as preventing or allowing access to the media are straight forward.  =
The
problem is that some OSes develop issues when they see a device but get
failures when they issue reads...

=20

USB devices use SCSI commands (mainly SPC and SBC) and package them in =
a
USB transport layer.  To the best of my knowledge there are no USB
specific CDB's defined.  If work is started as a part of this study
group, I expect that SAT would use this mechanism to access the ATA
security feature set.  It is also possible that SCSI devices would
implement this capability.

=20

=20

-------------------------------------------------

Curtis E. Stevens

20511 Lake Forest Drive #C-214D

Lake Forest, California 92630

Phone: 949-672-7933

Cell: 949-307-5050

E-Mail: Curtis.Stevens at WDC.com

Ambition is a poor excuse for not having enough sense to be lazy.

=20


------_=_NextPart_001_01C5CF6E.5E031A98
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1944262412;
	mso-list-type:hybrid;
	mso-list-template-ids:1415216124 826179116 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have had several inquiries about the purpose of =
this study
group.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>There is work going on within USB to enable a =
capability
that allows the device to prevent access to user data.=A0 The possible =
capabilities
are as follows:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>=A0<o:p></o:p></span></font></p>

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to detect =
that the
     device can prevent media access<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to define a =
password(s)<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to prevent =
access to
     user data areas the works across power =
cycles<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to allow =
access to
     user data areas<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to gain =
access if
     passwords are lost<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Mechanism to cause =
OSes to prompt
     for a driver if they do not natively support this =
capability<o:p></o:p></span></font></li>
</ol>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I think that defining mechanisms for turning on the
passwording as well as preventing or allowing access to the media are =
straight
forward.=A0 The problem is that some OSes develop issues when they see =
a device
but get failures when they issue reads=85<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>USB devices use SCSI commands (mainly SPC and SBC) =
and
package them in a USB transport layer.=A0 To the best of my knowledge =
there are
no USB specific CDB=92s defined.=A0 If work is started as a part of =
this study
group, I expect that SAT would use this mechanism to access the ATA =
security
feature set.=A0 It is also possible that SCSI devices would implement =
this
capability.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></f=
ont></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>---------------------------=
----------------------<o:p></o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Curtis E. =
Stevens<o:p></o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><st1:Street =
w:st=3D"on"><st1:address
 w:st=3D"on"><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
  Arial'>20511 Lake Forest =
Drive</span></font></st1:address></st1:Street><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> =
#C-214D<o:p></o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><st1:place =
w:st=3D"on"><st1:City
 w:st=3D"on"><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
  Arial'>Lake Forest</span></font></st1:City><font size=3D2 =
face=3DArial><span
 style=3D'font-size:10.0pt;font-family:Arial'>, <st1:State =
w:st=3D"on">California</st1:State>
 <st1:PostalCode =
w:st=3D"on">92630</st1:PostalCode></span></font></st1:place><o:p></o:p><=
/p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Phone: =
949-672-7933<o:p></o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Cell: =
949-307-5050<o:p></o:p></span></font></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>E-Mail: =
Curtis.Stevens at WDC.com<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Ambition
is a poor excuse for not having enough sense to be =
lazy.</span></font><b><font
size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:red;font-weight:bold'><o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C5CF6E.5E031A98--





More information about the T10 mailing list