1 Reply Latest reply on Sep 12, 2012 4:37 PM by SafeBoot

    EEFF 4.01 -- Is this expected behavior?

      When encrypting files on a share or local to a computer I have found that if you drag or copy and paste an encrypted file from a directory being encrypted the encryption status remains the same…..(encrypted)  If you open the file and then use the "save as" function, the file becomes unencrypted even though the user does not have a policy which allows permission to decryptfiles.

        • 1. Re: EEFF 4.01 -- Is this expected behavior?

          It depends on your policy. Encryption is "sticky" so for an encrypted file to become decrypted, you need to copy it somewhere where there's an explicit decrypt policy.

           

          Save As creates a new file, so if you're creating it in a folder without an explicit encrypt policy, it will be stored as plain text, unless there's a file type policy in place causing all files of a given extension to be encrypted.

           

          Save As won't decrypt the original file, nore can you "save as" over the top of the file you have open.

           

          So yes, what you say is quite easy to explain in terms of policy settings.