GlobalSCAPE Knowledge Base

Globalscape YouTube Channel

ivasquez — Fri, 19 Dec 2025 17:50:56 GMT

Discover Our YouTube Channel – Your Hub for Expert Tips and Tutorials

Stay ahead with our official YouTube channel! Explore videos that help you master tools, troubleshoot issues, and learn best practices—all in one place.

✅ Why Subscribe?

Step-by-Step Tutorials – Learn how to configure, optimize, and troubleshoot with ease.
Feature Highlights – Get the most out of new releases and updates.
Expert Insights – Hear from specialists on best practices and advanced techniques.

🔗 How to Access

Visit our channel: Click Here
Click Subscribe and turn on notifications to stay updated.

🎥 Popular Playlists

Getting Started Guides
Advanced Configuration Tips
Troubleshooting Common Issues
Featured Playlist

Subscribe Today and Never Miss an Update!

SharePoint File Upload Limitations – Files Larger Than 2GB Fail to Upload

ivasquez — Fri, 10 Oct 2025 20:23:28 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.2.x and later

DISCUSSION

Users have reported that attempts to upload files larger than 2GB to SharePoint result in failure. This limitation affects both SharePoint Online (365) and On-Premises SharePoint (2016/2019) environments.

Root Cause

The file size limitation is dictated by SharePoint’s server configurations and Microsoft’s platform boundaries.
In Automate, all SharePoint operations rely on CSOM (Client-Side Object Model), which itself does not impose file size limits. However, SharePoint’s backend enforces these restrictions.
The default maximum file size for uploads is 2GB in most configurations.

Details

SharePoint On-Premises (2016/2019):
See official Microsoft documentation for software boundaries and limits:
https://learn.microsoft.com/en-us/sharepoint/install/software-boundaries-limits-2019
SharePoint Online (365):
For cloud environments, refer to:
https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits
These limits may vary depending on the SharePoint version, authorization type, and server setup configured by SharePoint administrators.

Workarounds and Alternatives

Some third-party tools may use alternative SDKs or APIs that support chunked uploads, potentially bypassing the 2GB limit.
Automate does not support partial/chunk uploads, so files must be within the allowed size limit.

Recommendations

Before uploading, verify the file size and ensure it does not exceed the 2GB limit.
For larger files, consider splitting them or using alternative storage solutions.
Consult your SharePoint administrator for possible configuration changes or approved third-party tools.

Is EFT affected by the CVE-2020-14145 vulnerability?

ivasquez — Mon, 24 Mar 2025 13:34:44 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT 8.1 or older

QUESTION

Is EFT vulnerable to the CVE-2020-14145 vulnerability?

ANSWER

No. EFT uses OpenSSH differently and does not order host key algorithms, as a result this vulnerability does not apply to EFT.

If you want to avoid this false positive in your environment, update to EFT 8.2.1 that uses a newer version of OpenSSH.

Additionally, when your EFT server connects to an external server, you must define the connection profile with a valid and accessible path to the certificate. For detailed instructions refer to our online documentation: Defining a Connection Profile. If clients are connecting to your EFT server, they need to include your certificate in their connection string.

MORE INFORMATION

Online article about discovery of vulnerability: CVSS 5.9 CVE-2020-14145 — SSH-MITM

CVE website: CVE: Common Vulnerabilities and Exposures

DMZ Gateway and OpenJDK Vulnerabilities

ivasquez — Mon, 03 Mar 2025 21:24:15 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

DMZ Gateway 4.0

DISCUSSION

This notice is for informational purposes only and is intended to provide you with the latest update from Globalscape regarding the vulnerabilities in OpenJDK which is part of Java. Globalscape deems the risk posed by this issue to be low or not applicable, but we strive to be transparent with any issues that may arise.

The following list will be updated with any new identified vulnerabilities or customer requests.

CVE

Vulnerability

Globalscape Response

CVE-2022-

21426

Oracle Java SE

Oracle GraalVM Enterprise edition

in JAXP component

This vulnerability applies to Java deployments, typically in clients running sandboxed

Java Web Start applications or sandboxed Java applets, that run untrusted code.

DMZ does not have any interface which can execute outside code.

Additionally, DMZ does not have any API endpoints that can be called from outside to exchange data.

CVE-2022-

21434

Oracle Java SE

Oracle GraalVM Enterprise edition

in JAXP component

This vulnerability applies to Java deployments, typically in clients running sandboxed

Java Web Start applications or sandboxed Java applets, that run untrusted code.

DMZ does not have any interface which can execute outside code.

Additionally, DMZ does not have any API endpoints that can be called from outside to exchange data.

CVE-2022-

21443

Oracle Java SE

Oracle GraalVM Enterprise edition

in JAXP component

This vulnerability applies to Java deployments, typically in clients running sandboxed

Java Web Start applications or sandboxed Java applets, that run untrusted code.

DMZ does not have any interface which can execute outside code.

Additionally, DMZ does not have any API endpoints that can be called from outside to exchange data.

CVE-2022-

21476

Oracle Java SE

Oracle GraalVM Enterprise edition

in JAXP component

This vulnerability applies to Java deployments, typically in clients running sandboxed

Java Web Start applications or sandboxed Java applets, that run untrusted code.

DMZ does not have any interface which can execute outside code.

Additionally, DMZ does not have any API endpoints that can be called from outside to exchange data.

CVE-2022-

21496

Oracle Java SE

Oracle GraalVM Enterprise edition

in JAXP component

This vulnerability applies to Java deployments, typically in clients running sandboxed

Java Web Start applications or sandboxed Java applets, that run untrusted code.

DMZ does not have any interface which can execute outside code.

Additionally, DMZ does not have any API endpoints that can be called from outside to exchange data.

If you would like more information on the new vulnerabilities in Java, please view the following link:

If you have any further questions or concerns, please do not hesitate to contact Support.

Is EFT vulnerable to OpenSSH 9.5 CVE-2025-26465 (VerifyHostKeyDNS)?

ivasquez — Fri, 21 Feb 2025 21:02:11 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, version 7 and later

QUESTION

Is EFT vulnerable to OpenSSH 9.5 vulnerability CVE-2025-26465 (VerifyHostKeyDNS)?

ANSWER

No. After thorough review, Globalscape development confirmed that EFT code base does not use the ssh client application of OpenSSH, so EFT is not vulnerable to that specific vulnerability. In any event, Globalscape Engineering will update our OpenSSH library from 9.5.0 to version 9.8 in a future release.

MORE INFORMATION

CVE-2025-26465 [Medium severity] 18th February 2025: A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.

OpenSSH: Release Notes

NVD - CVE-2025-26465

CVE: Common Vulnerabilities and Exposures

DMZ Gateway 4.0

ivasquez — Wed, 05 Feb 2025 02:52:21 GMT

DMZ Gateway 4.0 Release Notes

Version: DMZ 4.0.0.14

Release Date: February 5th, 2025

Fixes

Properly signed the DMZ Gateway Admin Launcher for Windows

Features

Bundled OpenJDK version 17.02 on Windows and 17.07 on Linux
- Java dependency is no longer needed
Updated Tanuki Service wrapper
- Allows DMZ to run as a Windows service
Updated DMZ's Apache libraries
Updated DMZ Gateway branding to match Fortra branding
Updated OS supported list
- Windows Server 2022
- Windows Server 2019
- Limited support for Windows Server 2016
- Red Hat Enterprise Linux (RHEL) 9.4
- Ubuntu LTS 24.04
- Ubuntu LTS 22.04
Updated default list of cipher suites
- "TLS_AES_128_GCM_SHA256"
- "TLS_AES_256_GCM_SHA384"
- "TLS_CHACHA20_POLY1305_SHA256"
- "TLS_DHE_DSS_WITH_AES_128_CBC_SHA"
- "TLS_DHE_DSS_WITH_AES_128_CBC_SHA256"
- "TLS_DHE_DSS_WITH_AES_128_GCM_SHA256"
- "TLS_DHE_DSS_WITH_AES_256_CBC_SHA"
- "TLS_DHE_DSS_WITH_AES_256_CBC_SHA256"
- "TLS_DHE_DSS_WITH_AES_256_GCM_SHA384"
- "TLS_DHE_RSA_WITH_AES_128_CBC_SHA"
- "TLS_DHE_RSA_WITH_AES_128_CBC_SHA256"
- "TLS_DHE_RSA_WITH_AES_128_GCM_SHA256"
- "TLS_DHE_RSA_WITH_AES_256_CBC_SHA"
- "TLS_DHE_RSA_WITH_AES_256_CBC_SHA256"
- "TLS_DHE_RSA_WITH_AES_256_GCM_SHA384"
  
  "TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256"
- "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA"
- "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256"
- "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256"
- "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA"
- "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384"
- "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"
- "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256"
- "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA"
- "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256"
- "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"
- "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA"
- "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384"
- "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
- "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256"
- "TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA"
- "TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256"
- "TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256"
- "TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA"
- "TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384"
- "TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384"
- "TLS_ECDH_RSA_WITH_AES_128_CBC_SHA"
- "TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256"
- "TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256"
- "TLS_ECDH_RSA_WITH_AES_256_CBC_SHA"
- "TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384"
- "TLS_EMPTY_RENEGOTIATION_INFO_SCSV"
- "TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384"
- "TLS_RSA_WITH_AES_128_CBC_SHA"
- "TLS_RSA_WITH_AES_128_CBC_SHA256"
- "TLS_RSA_WITH_AES_128_GCM_SHA256"
- "TLS_RSA_WITH_AES_256_CBC_SHA"
- "TLS_RSA_WITH_AES_256_CBC_SHA256"
- "TLS_RSA_WITH_AES_256_GCM_SHA384"

Known Issues

None

Other Notes

Recommendation is to upgrade from our previous DMZ Gateway GA (General Availability) 3.5.0.35 to 4.0.0.14

Supported EFT versions:

8.2.1.x
8.2.0.x
8.1.0.16
Other EFT versions may work but were not validated by our QA team

Installer Location

Modifying the Automate Desktop 2024 service account breaks functionality

kmarsh — Mon, 02 Dec 2024 16:00:36 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.2.x and later

DISCUSSION

EFT administrators should not modify the Automate Desktop 2024 service (also known as the Task Service, AMTS.exe) as this will break functionality in EFT. The EFT help article Automate Desktop Service Account explains how to configure EFT's Automate Service Account on the Server > Administration tab in the EFT administration interface to continue to run event rules when the Windows session is logged out or locked, or the EFT server service account is logged out.

For use with EFT Event Rules, you should NOT change the permissions noted below. Creating an Automate Service account in EFT is all you need to do.

Here is the feedback from the Automate Team:

Service Log On Settings:

The customer attempted to assign a specific username and password under Service Properties > Log On tab. This alters the logon behavior from running under the default Local System Account to a specified user account. (Do not do this.)
- Automate Desktop 2024 can’t run in context of different user than Local System account, because it is critical for the service to execute WTSQueryUserToken to run AMEM.exe (Automate Desktop Event Monitor) under the specific user, otherwise Automate Desktop 2024 will not be able to function properly.
For the service to function properly with the Local System Account, the assigned user needs specific rights to execute certain Windows API functions (i.e., WTSEnumerateSessions and WTSQueryUserToken) and access certain system resources, such as files and directories.
Permissions for WTSEnumerateSessions and WTSQueryUserToken:

WTSEnumerateSessions requires the user to have permission to enumerate remote desktop sessions. Typically, the user needs to be part of the Remote Desktop Users group or have SeRemoteInteractiveLogonPrivilege.
WTSQueryUserToken obtains the primary access token of the logged-on user specified by the session ID. To call this function successfully, the calling application must be running within the context of the LocalSystem account and have the SE_TCB_NAME privilege. (Per Microsoft’s documentation)

Caution WTSQueryUserToken is intended for highly trusted services. Service providers must use caution that they do not leak user tokens when calling this function. Service providers must close token handles after they have finished using them.

File System Access (Folder C:\ProgramData\Automate\Automate Desktop 2024\AutomateDesktop2024TaskFile.atl):

The user in this scenario needs read and write access to the file located at C:\ProgramData\Automate\Automate Desktop 2024\AutomateDesktop2024TaskFile.at

Does EFT support US Federal regulation 21 CFR Part 11?

Chris_Le — Wed, 20 Nov 2024 20:25:29 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, all versions

DISCUSSION

21 CFR Part 11, is a Federal regulation meant to protect electronic records. Securely transferring electronic records (documents) is what EFT was designed for, regardless of the information in those records. Below is information about the 21 CFR 11 regulation and how EFT can help you protect your files.

What is 21 CFR Part 11?

Key elements of 21 CFR Part 11 include:

Scope: The regulation covers electronic records and electronic signatures used in FDA-regulated activities, such as clinical trials, manufacturing, quality control, and laboratory operations.
Electronic Records: Part 11 outlines requirements for the creation, modification, maintenance, and retention of electronic records. These records can include various types of documents, such as clinical trial data, laboratory results, and manufacturing records.
Electronic Signatures: The regulation defines the requirements for electronic signatures, which are digital equivalents of handwritten signatures. Electronic signatures are used to indicate approval, authorization, or review of electronic records.
Validation: Part 11 mandates the validation of electronic systems and processes to ensure that they meet the required standards for accuracy, reliability, and security. This validation process involves demonstrating that the system consistently produces accurate and reliable results.
Security Controls: The regulation requires the implementation of appropriate security controls to protect electronic records from unauthorized access, tampering, and data breaches. This includes user authentication, access controls, and audit trail mechanisms.
Audit Trails: Electronic systems covered by Part 11 should have audit trail capabilities to record and retain a secure record of all actions taken with electronic records and electronic signatures.
Record Retention: Part 11 specifies the requirements for record retention periods and the methods for ensuring records are accessible and legible throughout their retention period.
Electronic Copies of Records: The regulation allows for the use of electronic copies of paper records, provided certain requirements are met.

How can EFT help?

An EFT event rule can be created with the "File Uploaded" event and the "OpenPGP" action to verify signatures on files submitted to the server.

In this example, uploading a file to the server triggers the OpenPGP module to verify the signature on the file that was uploaded. Subsequent actions can be added to the event rule depending on success or failure of the upload.

EFT modules can be used to encrypt/ decrypt and sign/ verify documents, create an audit trail via reports and electronic receipts, and secure portals for sending and receiving files, meeting the following requirements of the regulation:

Validation – Files can be signed by EFT's OpenPGP module and, when uploaded to EFT Globalscape Servers, can be verified using the expected signature.
Audit Trail – EFT with Auditing and Reporting provides audit trails for any transfers entering and leaving the server.
Copies of Records – EFT’s Auditing and Reporting module provides historical records on file transfers within EFT.
Record Retention - EFT’s Auditing and Reporting module provides historical records on file transfers within EFT as well as any administrative changes done to the server.
Security Controls – EFT provides protection of multiple security compliance standards to ensure proper security controls are enforced within our application.

Refer to the Online Help documentation regarding Event Rules, Event Triggers (File Upload), and Event Actions (Cryptography: OpenPGP Action).

SFTP connections failing in Automate 2024 after upgrading to 8.2.0.46

kmarsh — Tue, 05 Nov 2024 15:12:03 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.2.x and later

SYMPTOM

SFTP connections failing in Automate 2024 after upgrading to 8.2.0.46

CAUSE

Automate is using KEX algorithms disabled/ not supported in EFT.

RESOLUTION/WORKAROUND

The workaround solution for this is to either use EFT's connection profiles and connect to remote clients using EFT's SFTP protocol or EFT, or the remote server must have the following KEXes enabled/supported. These are required and only supported by Automate:

diffie-hellman-group-exchange-sha1
diffie-hellman-group1-sha1
diffie-hellman-group14-sha1
diffie-hellman-group-exchange-sha256

Refer to Upgrading the Advanced Workflow Module for more details of upgrade the Advanced Workflow module with EFT.

How do I back up my EFT Arcus data?

kmarsh — Fri, 18 Oct 2024 16:47:46 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.x and later

QUESTION

How do I back up my EFT Arcus data?

ANSWER

As part of Arcus DR policies, customer file share volumes are backed up nightly. These incremental file backups are retained for 30 days. In the event of a disaster recovery or accidental deletion by a customer, our support team can help coordinate your request with our CloudOps team to restore your data. Please note, backups are not limited in size and are performed for the purpose of business continuity, which are not charged directly to our customers.

Can we configure Duo to work with EFT?

kmarsh — Tue, 15 Oct 2024 17:26:44 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.x and later

QUESTION

My organization uses Cisco Duo Single Sign-On to add two-factor authentication and flexible security policies to the applications that we use. Can we configure it to work with EFT?

ANSWER

Yes, Cisco Duo Single Sing-On can be configured to work with Globalscape EFT SAML 2.0 logins.

Refer to the Duo Single Sign-On for Globalscape EFT procedure on their website for details.

ERROR: AutoMate Task Builder is currently unlicensed for continued use

kmarsh — Wed, 02 Oct 2024 16:52:12 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT, v8.2.0.45 - 8.2.0.46 with Advanced Workflow module

SYMPTOM

In EFT, when attempting to edit an existing Advanced workflow remotely, it attempts to open the AWE task Builder but fails, presenting this error: "AutoMate Task Builder is currently unlicensed for continued use."

RESOLUTION

Option (1) :

Copy the following file from your EFT Server: C:\ProgramData\Automate\Automate Desktop 2024\OEMData.txt and copy this to your local system (same path in the remote system).
On your local system create the following directory C:\ProgramData\Globalscape\EFT Server\AWE\Temp
Attempt to open a workflow again

Option (2):

Upgrade to EFT 8.2.1

Option (3):

Stop the EFT service, re-install the EFT application as a Repair, and then log in to EFT as normal and retry.

MORE INFORMATION

This scenario assumes that the module is licensed, and the EFT Admin GUI is being accessed remotely using the remote administration tool.

Advanced workflows do not return modified variables to the calling event rule

kmarsh — Mon, 30 Sep 2024 15:34:18 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8.2.0.46
EFT v8.2.1.26

SYMPTOM

Advanced workflows do not return modified variables to the calling event rule. Not returning the modified variable breaks functionality in which EFT event rules rely on data manipulation within workflows.

RESOLUTION/WORKAROUND

To make the AML work with variables passed from external sources

When defining the workflow in the Task Builder, select the Treat as parameter check box and edit the "Create a variable" statement. This parameter is disabled/unselected by default.

In Automate 24 and later versions of the Advanced Workflows module, this option is mandatory to make EFT custom variables work in the event rule.

List of Third-party Tools Preferred by Client Services Team

ramiroguzman — Thu, 26 Sep 2024 18:17:18 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT all version

DISCUSSION

The Support Team recommends installing theses third-party troubleshooting tools to assist in resolving issues.

WireShark (Ethereal) – an open-source multi-platform packet analyzer used for network troubleshooting.
Process Monitor (ProcMon) – a Windows SysInternals tool that monitors and displays real-time file system activities.
Process Explorer – a Windows SysInternals tool that displays detailed information about a process including but not limited to the handles and DLLs opened or loaded.
ProcDump – a command-line utility that monitors an application for CPU spikes or crash and generates memory dumps that can be used to determine the cause of the spike or crash.
ADPlus – a Microsoft debugger that is used to capture memory dumps of any process or application that stops responding (hangs) or fails (crashes).
DebugDiag – another Microsoft debugger used to assist in troubleshooting hangs, slow performance, memory leaks or crashes.
VMMap – a Windows SysInternals tool that displays a process’s committed virtual memory as well as the amount of physical memory assigned by the OS.

These tools are optional to have readily available on your end to save time during a troubleshooting session with Globalscape Support.

“Error opening file for writing” during EFT upgrade

kmarsh — Fri, 13 Sep 2024 16:51:29 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT all versions

SYMTPOM

While upgrading EFT, an error message pops up stating “Error opening file for writing” and provides three options.

IMPORTANT Do not, under any circumstances, select the option to “Ignore” as this will cause future issues with EFT.

(Screenshot is for example only; error is not specific to file shown.)

CAUSES

This issue is due to EFT being unable to access this file through the service account. This can occur during the upgrade process between different versions of EFT.

RESOLUTION

Leave this error message open and follow the below instructions:

Open Windows File Explorer and navigate to the location stated in the error message.
Locate the file stated in the error message and rename the file. (Make sure the EFT server service is stopped.)
- You can add “_old” or “.old” to the end of the file.
After that, go back to the error message and select “Retry.”
This will resolve this error message unless there are multiple files that EFT is unable to write to, in which case, you would repeat these steps until the error message does not appear anymore.

"MAC Input Error" when attempting to establish an SFTP connection to Globalscape EFT server version 8.2.1

ivasquez — Thu, 12 Sep 2024 20:59:52 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8.2.1.26 - v8.2.1.30

SYMTPOM

Users of newer versions of WinSCP (as of Sept 2024) that use Putty version 0.81 may encounter a "MAC Input Error" when attempting to establish an SFTP connection to Globalscape EFT server version 8.2.1, this is not an EFT Globalscape issue but an issue with WinSCP. This error causes a connection failure.

CAUSE

The issue stems from an incompatibility between the specific cryptographic algorithms used in Putty 0.81 and the ones supported by Globalscape EFT 8.2.1 during the SFTP handshake process. To determine which version of WinSCP with Putty you are using in WinSCP, click Help > About, then look in the Portions copyright area to see the version of Putty WinSCP is using. (Refer to the image below.)

WORKAROUND

Upgrade EFT to version 8.2.1.33
Use an alternative FTP client such as CuteFTP or FileZilla
Update your WinSCP SSH connection profile encryption cipher to prioritize the "AES-GCM" cipher
+

Additional Notes:

It is always recommended to keep your software up to date to benefit from the latest features, security patches, and bug fixes.
If you continue to experience issues, consult the Globalscape EFT documentation or contact their support team for further assistance.
Please note that modifying cryptographic settings might have security implications. Ensure you understand the potential risks before making any changes.
In the EFT logs, you will see this error message: “incorrect MAC received on packet”

Disclaimer: This article provides general information and troubleshooting steps. Always refer to official product documentation and support channels for the most accurate and up-to-date information. Here are a few forum links in relation to this that you will want to look into that have provided information on this issue:

Incorrect MAC received on packet Errors in Versions 6.1–6.3 :: Support Forum :: WinSCP

Incorrect MAC received on packet :: Support Forum :: WinSCP

Automate reports "12002 the operation timed out" error

Aarongskns — Tue, 03 Sep 2024 14:20:51 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8.2 and later

DISCUSSION

In EFT, if you are running multiple concurrent Automated Workflows that may take some time to complete (usually when the action to complete can take longer than 60 seconds) and you experience failures (such as EFT is logging error “12002: The operation timed out”) you can add this advanced property to the advancedproperty.json file. This advanced property sets Automate's REST API request timeout and should be set to a time (in seconds) longer than it would take for the task to complete.

Add the name:value pair below to the AdvancedProperties.JSON file:

{
"AutomateRestApiRequestTimeoutSecs": 120
}

The default value is 60, minimum value is 15, and maximum is 300.

For details of using advanced properties, refer to KB article 11526, Advanced Properties.

Upgrading RAM to v8.2.1

kmarsh — Fri, 23 Aug 2024 19:06:10 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT Remote Agents v8.2.0.45 and v8.2.0.46

DISCUSSION

Upgrading from EFT 8.2.0 to EFT 8.2.1 with RAM configured will require manual upgrade on Remote Agent; this does not affect upgrades from EFT 8.1.x.

Before upgrading your Remote Agents to EFT v8.2.1, please read and understand the following information.

If the deployed agent is version 8.2.0.45 or 8.2.0.46, you must manually upgrade or redeploy the agent after EFT is upgraded.
Also note that v8.2.0.45/46 agents will STOP working once EFT is upgraded until they are manually upgraded.
v8.1.0.16 agents will auto upgrade going to v8.2.1.26.
Remote Agent automatic updates do not work when coming from v8.2.0.45/46 and the admin will need to either manually upgrade or uninstall the current agent, then re-deploy the new version.

Below are the steps to manually upgrade the agent.

v8.2.0.45/8.2.0.46 agent is already deployed.
Upgrade EFT to 8.2.1.26.
The agent will download the new v8.2.1.26 agent installer but will fail to run the installer. The agent will then disable itself.
The new agent installer will be located in C:\ProgramData\Globalscape\EFT Remote Agent\update\.

Note that there may be multiple agent installers, so verify that you have the correct version.
If the agent failed to download the new agent installer, you will need to transfer it to the machine.

CMD to the same directory and run the corresponding agent template installer script.

Note that if the agent template was set to auto enroll, the enrollment period may have expired; you will need to re-create a new agent template and use that agent install script.

The agent should then update and automatically be reconfigured without needing to uninstall the old agent.
If the above steps fail, you will need to uninstall the current agent and re-deploy the agent as you would in a fresh deployment. (Refer to the help documentation for your version of EFT.)

Treat double slash as a single one in path arguments

Aarongskns — Wed, 07 Aug 2024 19:07:43 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

This advanced property specifies whether to treat double slash as a single one in path arguments of FTP commands.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"FixDoubleSlashInPathsForFTP": true
}

Set to 1 to enable. Default is 0.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Run Transfer actions in parallel (in an IF group)

pmaynard — Wed, 07 Aug 2024 18:56:09 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

This advanced property determines whether to run a group (grouped by IF Statement) of transfer actions in parallel.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"ExecuteTransferActionsInParallel":true
}

Set to 1 to enable. Default is 0.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For more information about using the IF statement, search for "File System Conditions" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Including or excluding VFS folders in quota

Aarongskns — Wed, 07 Aug 2024 17:11:40 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later
In EFT v8.1 and later, you can enable and set upload quota in the VFS. (search the help in EFT for "upload quota.")

DISCUSSION

This advanced property determines whether Virtual Folders are included in the disk quota calculation.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"ExcludeVFolderInQuotaCalc": true
}

If this value is set to 1, virtual folders are not evaluated when calculating a user's quota restriction.
If set to the default of 0, virtual folders are used in the calculation.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For more information about disk quota, search for "disk quota" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Enable or disable client logs (Advanced Property)

ivasquez — Wed, 07 Aug 2024 15:59:03 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

To monitor EFT client activity, you can reference EFT’s log files, including the registration state of the modules, server/site functions, SFTP, SSL/TLS connections, and of course, errors and warnings. The EFT client activity log (also known as "TED6" logs) is used to log client connection information (event rules and outbound transfers), client commands/requests, remote server responses, and status messages. EFT client log files are saved in the C:\ProgramData\Globalscape\EFT Server\Logs\ folder.

The advanced property below is used to enable or disable client logs.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"EnableClientLogging":true
}

The default is false, meaning that logging is disabled. A value of true, enables logging.

MORE INFORMATION

This advanced property only enables or disables logging. If you want to change the format or location of the logs, that is done in the admin interface Server > Logs tab.

For more information about client logging, search for "EFT Client Activity Log" in the help for your version of EFT.

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Decompress Action Scan Timeout

kmarsh — Wed, 07 Aug 2024 15:49:41 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

The advanced property sets the timeout in milliseconds for a decompression action scan operation. Scan is used primarily when autodetecting the archive format.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"DecompressActionScanTimeout":"3000"
}

The default is 0, meaning that the timeout is disabled. A non-zero value is the number of milliseconds before timeout.
An example value is 30000 milliseconds, which is 30 seconds.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For more information about compression, search for "compression" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Set timeout in ms for the first BeginFile callback during decompression (Advanced Property)

pmaynard — Wed, 07 Aug 2024 15:46:37 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

The advanced property sets the timeout in milliseconds for the first BeginFile callback during decompression.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"DecompressActionBeginFileTimeout":3000
}

The default is 0, meaning that the timeout is disabled. A non-zero value is the number of milliseconds before timeout.
An example value is 30000 milliseconds, which is 30 seconds.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For more information about compression, search for "compression" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2

Compress Action Timeout

pmaynard — Wed, 07 Aug 2024 14:30:31 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT v8 and later

DISCUSSION

The advanced property sets the timeout for compression is seconds.

Add the name:value pair below to the AdvancedProperties.JSON file in the \ProgramData\ folder for EFT (for example, C:\ProgramData\Globalscape\EFT Server):

{
"CompressActionTimeout":300
}

The default is 0, meaning that the timeout is disabled. Non-zero value is the number of seconds before timeout. An example value is 300 seconds, which is 5 minutes.

MORE INFORMATION

For more information about Advanced Properties, search for "Advanced Properties" in the help for your version of EFT.

For more information about compression, search for "compression" in the help for your version of EFT.

For pre-v8 versions of EFT, the registry value is

SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.2