Files remain encrypted, there is no intermediary step required to decrypt the file.No additional coding required to decrypt the file and send the file data to an application. Applications will work seamlessly to decrypt files when SED is installed and running as an authorized user of the group. No additional coding required to work with your existing applications.Change keys and provide the new public key to the sender without needing to update code to decrypt that is based on a hard coded key or passphrase! Add/remove users/accounts access privileges without needing to recode anything. Even if compromised, the intruder doesn’t get the private key for later use. Since keys and access are managed by the server, there is no passphrase required and the client machine never has the key stored on it. No need to cache/hardcode a passphrase or keyid.It can be opened by any application running as a user account (service account, or other) that is managed by the Symantec Universal Server that is on the group for that group key. When receiving the Symantec File Share encrypted file from the sender, it will be a Symantec File Share encrypted file to your group key.Add users that you want to be able to decrypt files received to the group.Export and provide the PUBLIC key to the sender of the information.Set up a group and group key (SKM) on the management server.Purchase Symantec Encryption Desktop with a Symantec File Share license.Receiving side (you, and secure if using a management server to manage the group keys): Remember to blacklist SFTP from automatically decrypting files in the Symantec File Share policy settings, so the file remains encrypted when the SFTP application sends it. Send the Symantec File Share encrypted file to the recipient.Command line is simply: pgpnetshare.exe -e -r “recipient keyid” -s “your keyid” -passphrase “passphrase” Encrypt the file to the recipient’s key in a Symantec File Share format.Import the public key provided by the recipient and use pgpnetshare.exe or a Symantec File Share with the Recipient’s public key specified as the encryption key for the share to encrypt the file to the recipient.Purchase Symantec Encryption Desktop (SED) with a Symantec File Share license.If what I described above is what you want to do though, here's how: Symantec Encryption Desktop doesn't do this seem to allow a way to do this in an automated fashion. If you want to do this with the general public or organizations not using Symantec Encryption Desktop with Symantec File Share, then your only option is to script it and store the passphrase somewhere/somehow securely using PGP Command line, or another product. They are different formats, but both use PGP encryption. Note this doesn't work for standard PGP files, only PGP encrypted Symantec File Share files. This may be possible with unmanaged environment, but then keys are stored locally and this is probably not secure for group keys. Also, this bypasses the user's private keys and provides extra security of having the private keys stored only on the management server. You have a managed key environment (Symatec Universal Server). You use Symantec File Share group keys (SKM)ģ. Both you and the sender have Symantec Encryption Desktop with File Share Encryption (PGP Netshare) licensesĢ. If that's the case, then actually, I believe there is a way to do this using Symantec File Share files (PGP Netshare). IF you:ġ. I'm assuming that you are trying to do this with with another organization, or company such as a bank or information sharing partner, and not just the random public.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |