Dencrypting File with different key | Community
Skip to main content
derrickr8850025
derrickr8850025
Level 2
October 26, 2017
Solved

Dencrypting File with different key

  • October 26, 2017
  • 3 replies
  • 2217 views

I have 2 different files coming from 2 different locations with 2 different keys on them.

When attempting to load the data, does anyone know how to specify which key goes with each file.

I know you can pre-process the file in  File Import, but not sure how to specify a key.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Philippe_Ferdin

    If using GPG, I believe you don't have anything to do.

    The key is referenced in the encrypted files so GPG would known which one to use (see https://superuser.com/questions/920793/how-to-specify-private-key-when-decrypting-a-file-using-gnupg)

    Just make sure both keys are available on the Campaign server.

    3 replies

    P
    Adobe Employee
    Philippe_FerdinAdobe EmployeeAccepted solution
    Adobe Employee
    October 26, 2017

    If using GPG, I believe you don't have anything to do.

    The key is referenced in the encrypted files so GPG would known which one to use (see https://superuser.com/questions/920793/how-to-specify-private-key-when-decrypting-a-file-using-gnupg)

    Just make sure both keys are available on the Campaign server.

    derrickr8850025
    derrickr8850025Author
    Level 2
    October 26, 2017

    Thanks for the reply

    I am using GPG.

    So basically I need to send the private key to Adobe to install on the server?

    And then when running my gpg --decrypt, reference the passphrase and the filename and it should decrypt the file

    P
    Adobe Employee
    Philippe_FerdinAdobe Employee
    Adobe Employee
    October 26, 2017

    Yes, but I'm not sure about the passphrase. Not sure you can provide the passphrase as an argument. So far I've always used gpg keys with not passphrase for automation.

      Terms & ConditionsAccessibility statement

      Loading footer...