You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 

141 lines
5.2 KiB

using Security2;
using System;
using System.Management.Automation;
using System.Security.AccessControl;
namespace NTFSSecurity
{
[Cmdlet(VerbsCommon.Set, "NTFSSecurityDescriptor")]
[OutputType(typeof(FileSystemSecurity2))]
public class SetSecurityDescriptor : BaseCmdletWithPrivControl
{
private SwitchParameter passThru;
[Parameter(Mandatory = true, Position = 1, ValueFromPipeline = true, ValueFromPipelineByPropertyName = true)]
public FileSystemSecurity2[] SecurityDescriptor
{
get { return securityDescriptors.ToArray(); }
set
{
securityDescriptors.Clear();
securityDescriptors.AddRange(value);
}
}
[Parameter()]
public SwitchParameter PassThru
{
get { return passThru; }
set { passThru = value; }
}
protected override void BeginProcessing()
{
base.BeginProcessing();
}
protected override void ProcessRecord()
{
foreach (var sd in securityDescriptors)
{
try
{
// Only the changed sections, so that an unchanged owner, for example, isn't written back (#34)
var changedSections = sd.ChangedSections;
if (changedSections == AccessControlSections.None)
{
WriteVerbose(string.Format("No section of the security descriptor of '{0}' changed since it was read or last written; nothing is written", sd.FullName));
}
else
{
WriteVerbose(string.Format("Writing the changed sections of the security descriptor of '{0}': {1}", sd.FullName, changedSections));
}
sd.WriteChanges();
}
catch (UnauthorizedAccessException)
{
try
{
WriteChangesAsOwner(sd);
}
catch (Exception ex2)
{
// Not what a later command raises, for example when it takes the RestoreOwnerError record.
if (IsFromLaterCommand(ex2))
{
throw;
}
WriteError(new ErrorRecord(ex2, "WriteSdError", ErrorCategory.WriteError, sd.Item));
continue;
}
}
catch (Exception ex)
{
// Not what a later command raises, for example when it takes the verbose message.
if (IsFromLaterCommand(ex))
{
throw;
}
WriteError(new ErrorRecord(ex, "WriteSdError", ErrorCategory.WriteError, sd.Item));
continue;
}
// After the write and outside its retry: before 5.0.0-rc6, a write that needed ownership wrote no
// object, and a denied read started a retry of the write and ended in a WriteSdError.
if (passThru)
{
try
{
WriteObject(new FileSystemSecurity2(sd.Item));
}
catch (Exception ex)
{
if (IsFromLaterCommand(ex))
{
throw;
}
WriteError(new ErrorRecord(ex, "ReadSecurityError", ErrorCategory.ReadError, sd.Item));
}
}
}
}
// Like InvokeAsOwner, takes ownership for the write and sets the previous owner back on every exit path, but not
// after a successful write of a descriptor that sets the owner itself, which would undo that owner, and not when the
// current user owned the item already, so that nothing changed and a descriptor that leaves nobody the right to set
// an owner can't make it fail.
private void WriteChangesAsOwner(FileSystemSecurity2 sd)
{
var setsOwner = (sd.ChangedSections & AccessControlSections.Owner) == AccessControlSections.Owner;
var previousOwner = FileSystemOwner.GetOwner(sd.Item).Owner;
IdentityReference2 currentUser = System.Security.Principal.WindowsIdentity.GetCurrent().User;
FileSystemOwner.SetOwner(sd.Item, currentUser);
var written = false;
try
{
sd.WriteChanges();
written = true;
}
finally
{
if (!(written && setsOwner) && previousOwner != currentUser)
{
try
{
FileSystemOwner.SetOwner(sd.Item, previousOwner);
}
catch (Exception ex)
{
WriteError(new ErrorRecord(ex, "RestoreOwnerError", ErrorCategory.WriteError, sd.Item));
}
}
}
}
}
}