[prev in list] [next in list] [prev in thread] [next in thread]
List: cifs-protocol
Subject: Re: [cifs-protocol] Questions about Validated-SPN validated write
From: Dominic Salemno <doms () microsoft ! com>
Date: 2010-12-17 15:38:56
Message-ID: 5E7269F75DD68F4B9C39BDAB63595FA7083B3634 () TK5EX14MBXC137 ! redmond ! corp ! microsoft ! com
[Download RAW message or body]
Nadezhda Ivanova,
Someone from our team will follow-up with you shortly in regards to your qu=
estions.
Dominic Salemno
Escalation Engineer
Open Specifications
From: didrash@gmail.com [mailto:didrash@gmail.com] On Behalf Of Nadezhda Iv=
anova
Sent: Friday, December 17, 2010 6:08 AM
To: Interoperability Documentation Help
Cc: cifs-protocol@samba.org
Subject: Questions about Validated-SPN validated write
Hello,
Does Validated-SPN validated write allow an account to set an object's SPN =
to the following values:
HOST/samAccountName (without the "$")
HOST/dnsDomainName
if the object is a regular computer object and NOT a DC?
The algorithm described in MS-DRSR 5.5 AccessCheckWriteToSpnAttribute seems=
to indicate that yes, this should be allowed. Ot the other hand, MS-ADTS 3=
.1.1.5.3.1.1.4 servicePrincipalName leads me to believe that the object bei=
ng a DC is mandatory constraint: "The SPN is a syntactically correct two-pa=
rt SPN, or it is a syntactically correct three-part SPN (see
Mutual Authentication (section 5.1.1.4)) and the object is a DC's domain co=
ntroller object (see
sections7.1.1.3.1 and 7.1.1.3.2). "
In addition, I did the following test:
Gave Validated-SPN right to a user on a regular computer object, and got CO=
NSTRAINT_VIOLATION when setting its servicePrincipalName with the above des=
cribed values.
Gave Validated-SPN right to a user on a DC object, and these values were se=
t successfully.
So my questions are:
Is the behaviour of setting servicePrincipalName supposed to be different b=
etween LDAP and DRS?
Does servicePrincipalName modification depend on things other then the synt=
ax restrictions described in MS-DRSR and MS-ADTS?
If an object does not have Validated-SPN on Principal-Self, should the acco=
unt still be allowed to set the above values via DRS?
Best Regards,
Nadezhda Ivanova
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Courier New";
font-variant:normal !important;
color:black;
text-transform:none;
text-decoration:none none;
vertical-align:baseline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Courier \
New";color:black">Nadezhda Ivanova,<o:p></o:p></span></p> <p \
class="MsoNormal"><span style="font-family:"Courier \
New";color:black"><o:p> </o:p></span></p> <p class="MsoNormal"><span \
style="font-family:"Courier New";color:black">Someone from our team will \
follow-up with you shortly in regards to your questions.<o:p></o:p></span></p> <p \
class="MsoNormal"><span style="font-family:"Courier \
New";color:black"><o:p> </o:p></span></p> <p class="MsoNormal"><span \
style="font-family:"Courier New";color:black">Dominic Salemno<br> \
Escalation Engineer<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-family:"Courier New";color:black">Open \
Specifications<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-family:"Courier New";color:black"><o:p> </o:p></span></p> \
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> \
didrash@gmail.com [mailto:didrash@gmail.com] <b>On Behalf Of </b>Nadezhda Ivanova<br>
<b>Sent:</b> Friday, December 17, 2010 6:08 AM<br>
<b>To:</b> Interoperability Documentation Help<br>
<b>Cc:</b> cifs-protocol@samba.org<br>
<b>Subject:</b> Questions about Validated-SPN validated write<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello,<br>
Does Validated-SPN validated write allow an account to set an object's SPN to the \
following values:<br> HOST/samAccountName (without the "$")<br>
HOST/dnsDomainName<br>
if the object is a regular computer object and NOT a DC?<br>
<br>
The algorithm described in MS-DRSR 5.5 AccessCheckWriteToSpnAttribute seems to \
indicate that yes, this should be allowed. Ot the other hand, MS-ADTS 3.1.1.5.3.1.1.4 \
servicePrincipalName leads me to believe that the object being a DC is mandatory \
constraint: "The SPN is a syntactically correct two-part SPN, or it is a \
syntactically correct three-part SPN (see<br> Mutual Authentication (section \
5.1.1.4)) and the object is a DC’s domain controller object (see<br> \
sections7.1.1.3.1 and 7.1.1.3.2). "<br> <br>
In addition, I did the following test:<br>
Gave Validated-SPN right to a user on a regular computer object, and got \
CONSTRAINT_VIOLATION when setting its servicePrincipalName with the above described \
values.<br> Gave Validated-SPN right to a user on a DC object, and these values were \
set successfully.<br> <br>
So my questions are:<br>
Is the behaviour of setting servicePrincipalName supposed to be different between \
LDAP and DRS?<br> Does servicePrincipalName modification depend on things other then \
the syntax restrictions described in MS-DRSR and MS-ADTS?<br> If an object does not \
have Validated-SPN on Principal-Self, should the account still be allowed to set the \
above values via DRS?<br> <br>
Best Regards,<br>
Nadezhda Ivanova<o:p></o:p></p>
</div>
</body>
</html>
_______________________________________________
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
--===============0462605762969640610==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic