EFT Specifications

This topic is intended as a quick reference of EFT specifications. The information is provided in detail in the applicable procedures.

Item

Description

Server's Windows user account

The EFT service runs under a user account, which must have full administrative rights to the folder in which you install EFT. With administrative rights, the service can save all of your settings. If the service does not have administrative rights, you will lose settings and user accounts whenever you restart the EFT service, and you will need to reset permissions on the computer on which the EFT service is running. If you are using Active Directory, there are other considerations regarding permissions.

Protocols allowed

FTP/S (SSL/TLS), SFTP (SSH2), HTTP/S, and AS2 (Certain protocols require optional modules and/or  EFT Enterprise.)

Authentication types

Globalscape, AD/NTLM, LDAP, ODBC

Log formats

W3C, Microsoft IIS, and NCSA

SSL Certificate Key lengths supported

Key lengths supported: 1024, 2048, 3072, and 4096 bits

Server-created SSL certificates

x.509 base-64 standard DER encoded

Allowed OpenSSL ciphers for inbound transfers (HTTPS and FTPS)

Refer to Using Ciphers for Inbound SSL Connections for details.

Allowed SSL versions

TLS 1.0, SSL 2.0, or SSL 3.0

  • EFT version 6.5 uses OpenSSL 0.9.8t; FIPS SSL is based on OpenSSL 0.9.8m

SFTP hashing algorithms supported

MD2, MD4, MD5, Haval, RIPE-MD, SHA-1, SHA-Double, Tiger

OpenPGP version

OpenPGP is a standard and has no version. EFT adheres to the OpenPGP standard and is RFC 2440 compliant.

FIPS

EFT supports public key lengths for RSA in FIPS SSL from 1024 to 4096 bits. The FIPS library used by EFT is certified with DSA (1024 bits only) or RSA (1024, 2048, and 4096) keys.

PCI DSS

EFT facilitates compliance with PCI DSS 2.0.

SFTP

EFT supports SFTP versions 2, 3, 4, and 6. The outbound client defaults to version 4, and it is not configurable through the GUI, but can be configured in the registry. The EFT outbound client negotiates the SFTP version with the receiving server during session establishment. That is, if the receiving server only supports version 2, EFT Server will negotiate down and operate at version 2.

AS2 module

EFT uses /n software's IP*Works EDI Engine, in compliance with RFC4130

Maximum Capacity for EFT

Listed below are several EFT object types and the maximum number of each type (both theoretical maximum and tested maximum) that can be defined in EFT. Keep in mind that an excessive number of total objects displayed in the administration interface can affect the responsiveness of the interface.

EFT Object

Theoretical Maximum

Tested Maximum

Maximum number of Server Groups

32768

maximum not tested

Maximum number of Servers (EFTs)

32768

10

Maximum number of Sites

2147483647

40

Maximum number of Settings Templates

2147483647

maximum not tested

Maximum number of users per Server

2147483647

maximum is set per Site

Maximum number of users per Site

2147483647

150,000

Maximum number of users per Settings Template

2147483647

maximum is set per Site

Maximum number of users per Permission Group

2147483647

maximum is set per Site

Maximum number of administration accounts

2147483647

1,000

Maximum number of Permissions (on VFS tab)

2147483647

maximum not tested

Maximum number of VFS entries

2147483647

150,000

Maximum number of Permission Groups

2147483647

maximum not tested

Maximum number of Folders

2147483647

See VFS entries maximum

Maximum number of Event Rules

65536

4,000 Folder Monitor Event Rules

Maximum number of Commands

65536

maximum not tested

Maximum number of AWE tasks

65536

maximum not tested

Maximum number of Custom Reports

65536

maximum not tested

Maximum number of pages in a report

2500

2000

Maximum number of simultaneous connections

65536

1,000

Note: Object type distribution for baseline and testing purposes was roughly 80% users, 10% Folder Monitor Event Rules, 5% other Event Rules, 2.5% AWE tasks, 2.5% other.