Opened 11 years ago
Closed 10 years ago
#2665 closed Feature Request (Completed)
Support for EFS (Encrypting File System)
Reported by: | anonymous | Owned by: | Jon |
---|---|---|---|
Milestone: | 3.3.13.2 | Component: | AutoIt |
Version: | Severity: | None | |
Keywords: | Cc: |
Description
I've got my first Windows (8.1 Pro) with EFS support. I started using EFS and noticed that some of the FileCopy commands in my AutoIt scripts were no longer functioning properly.
If I FileCopy a "normal" (=no EFS) file, the FileCopy returns a 1=success.
But if I FileCopy an EFS encrypted file, the FileCopy returns a 0=failure.
The destination folder is located on my NAS (Network Attached Storage).
There are no problemens whilst copying/moving (EFS and non-EFS) files within the 2 hard drives in my PC.
If I drag&drop the file with Windows I get this nice little popup: "you are copying the file to a destination that does not support encryption" (with the possibility to stop or continue).
I think my problems are not new and may go back some years when Microsoft first introduced EFS.
I would like AutoIt to support EFS.
My suggestions:
1) FileGetAttrib command. A new ReturnValueLetter. For example the "E" for Efs.
2) FileCopy/FileMove commands. A new flag allowing an EFS encrypted file to be copied whilst losing its encryption.
3) A FileCopy/FileMove return code explaining the EFS-failed-reason.
I hope I've explained my problem/feature request properly (english is not my native language).
Thank you for "listening".
Kind regards,
Gordon
from The Netherlands
My workaround for now looks like this:
$Source = "D:\Test.txt" $Dest = "N:\" $Result = FileCopy($Source, $Dest, 1) If $Result = 0 Then $Result = RunWait(@ComSpec & " /c " & "Copy /D """ & $Source & """ """ & $Dest & """", "", @SW_MAXIMIZE) ;"/D" means "Allow the destination file to be created decrypted". If $Result <> 0 Then MsgBox(0, "Fail", "Both 'AutoIt FileCopy' and 'DOS Command Copy' failt!" & @LF & "Source=" & $Source & @LF & "Dest=" & $Dest) Exit EndIf EndIf
Attachments (0)
Change History (2)
comment:1 Changed 11 years ago by TicketCleanup
- Version 3.3.8.1 deleted
comment:2 Changed 10 years ago by Jon
- Milestone set to 3.3.13.2
- Owner set to Jon
- Resolution set to Completed
- Status changed from new to closed
Added by revision [10277] in version: 3.3.13.2
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Automatic ticket cleanup.