File Mover Blog

  • 20 Oct

    How to verify the pgp signature during decryption

    How to verify the pgp signature during decryption

    Q: I use PGP decryption in some rules and I need to activate the signature checking. Can you tell me if this is available and how to do it ?

    A: We added this option in v2024.10.19.0

    • PGP Decryption, Added Verify Signature option (v2024.10.19.0) [+]

    We added some screenshots in this blog article to get you started.

    • We used a Windows Folder as Destination:

    limagito file mover destination setup

    • We enabled ‘Enable Encrypt – Decrypt’ and selected ‘Decrypt Files’. As Encryption Algorithm we chose  ‘PGP (Pretty Good Privacy)’.

    limagito file mover crypto setup

    • Under the PGP tab we:
      • Added our Private Key file (and password) to decrypt the received files. The files we received were encrypted by a third party using our corresponding public key.
      • Added the Public Key file we received, from this third party, to check the signature. The files we received were signed by the third party using their private key file.
      • Enabled the ‘Verify Signature (Decryption)’ option.

    Important: When ‘Verify Signature’ is enabled then all files must have a valid signature. Also files without a signature will not be allowed (error).

    limagito file mover verify the pgp signature

    • RunTime log example of files with an invalid signature:

    limagito file mover verify the pgp signature

    If you need any help with this “verify the pgp signature” question, please let us know.

    Best Regards,

    Limagito Team

    #pgp #managedfiletransfer #filetransfer #filemanagement

    By Limagito-Team PGP
  • 18 Oct

    How to send files to Azure using limagito file mover

    How to send files to Azure using limagito file mover

    Q: We are trying to send files to Azure. This is the first time we are connecting to Azure and need help. We have page blobs selected and are getting the error messages below, when hitting the “Connect” button in the setup.

    10/17/2024 9:48:55 AM Container Exists Exception Error: Connection failed due to error 96260

    10/17/2024 9:50:31 AM Connect AZURE, ContainerName Exception: Connection failed due to error 96260

    10/17/2024 9:50:46 AM Container Exists Exception Error: Connection failed due to error 96260

    A: We had a remote meeting with the customer and agreed that we would send him the working setup of our test system.

    • Destination setup, AZURE as Destination

    limagito file mover send files to Azure destination setup

    • We asked the customer to check the AccountName he was using (it looked a bit strange to us), only the first part is needed without core.windows.net

    limagito file mover Azure settings

    limagito file mover send files to Azure setup

    • We used a container named “pageblob”:

    limagito file mover azure container setup

    • Default File and Directory setup:

    limagito file mover file and directory setup

    • Default Common setup:
      • In case your account is not allowed to check if a container exists then enable “Do not check is Container exists”.
      • If you need more logging information, enable “Add Control Information to Log”.

    limagito file mover common setup

    • RunTime Log result:

    limagito file mover send files to azure log

    • Feedback customer:

    Thanks for your help today.  I believe we have all the settings correctly in place on Limagito. We determine I didn’t truncate our account name correctly.  Once I fixed that, it started to work.

    If you need any help with this “send files to Azure” question, please let us know.

    Best Regards,

    Limagito Team

    #azure #managedfiletransfer #filetransfer #filemanagement

    By Limagito-Team Azure
  • 18 Oct

    The x-amz-content-sha256 header does not match what was computed

    The provided x-amz-content-sha256 header does not match what was computed

    Q: I was able to setup a non aws s3 (wasabi) as source but I’m not able to do so as destination. Is it possible to have some help?

    A: The customer was using an older version so we first asked him to update his version. We created a new build with extra logging information for AWS as Destination (v2024.10.14.0 or higher).

    <Error><Code>XAmzContentSHA256Mismatch</Code><Message>The provided &apos;x-amz-content-sha256&apos; header does not match what was computed.</Message><ClientComputedContentSHA256>8AFBD736EC2917807F5FF5D8A9018846AA9D6B25EC839506DACE0D588DE491C5</ClientComputedContentSHA256><S3ComputedContentSHA256>8afbd736ec2917807f5ff5d8a9018846aa9d6b25ec839506dace0d588de491c5</S3ComputedContentSHA256><RequestId>1CF8F37CAA85D906:A</RequestId><HostId>KKwBla460dUwWRytyBUsvPQBw/z9QNkAg8mFuYQtBNOUHDXQhPG1vYAHfC5djS/fwa0VH2J0qIHx</HostId><CMReferenceId>MTcyODkyMjIzMDgxOCAxMzAuMTE3LjE4NS4xMDIgQ29uSUQ6ODA5NDI1OTAwL0VuZ2luZUNvbklEOjc5MDkwODgvQ29yZTo0Ng==</CMReferenceId></Error>

    We found out that Wasabi was expecting the lowercase of the sha256 hash. This was adjusted in version v2024.10.17.0 and since this version we are using the lowercase of the sha256 hash.

    If you need any help with this question, please let us know.

    Best Regards,

    Limagito Team

    #awss3 #managedfiletransfer #filetransfer #filemanagement

1 4 5 6 7 8 9 10 151
SEARCH