General

IDN (Internationalization of Domain Names) support by converting Unicode to Punycode upon use. From a user (presentation) perspective and EFT’s internal representation, it will be Unicode.

Conversion to Unicode for storage, but downgrade on usage. No risk/potential for loss of fidelity, as all chars limited to <128 ASCII.

You can paste in Punycode ASCII characters directly for the domain portion if you must have Unicode domains for email addresses.

Conversion to Unicode for storage, but downgrade on usage. No risk/potential for loss of fidelity, as all chars limited in GUI/usage to <128 ASCII.

See Installer – ASCII ONLY below for potential problems

Keys and OpenPGP

RFC allows for Unicode but OpenSSL handles the value as ASCII

Passwords stored as octets sequence using same encoding as UI (ASCII)

Passwords stored as octets sequence using same encoding as UI (ASCII)

Veridis limitation. Passwords stored as octets sequence, 8-bit ASCII.

Unicode filenames will be supported, but the will be temporarily converted to ASCII.

OpenPGP module does not support Unicode

OpenPGP module does not support Unicode

RSA

RSA dll only takes ASCII path values

RSA does not support Unicode. We will downgrade to ASCII on usage. Potential loss of fidelity resulting in failed authentication attempts.

ARM

Loss of fidelity for UTF-8 chars that don’t match local code page for ext. ASCII. The VSReport Designer does not support Unicode.

AS2

AS2 does not support Unicode encoded filenames. We can’t downgrade to ASCII as we would be violating Drummond, thus we will simply disallow and log error.

AS2 does not support Unicode encoded filenames. Unlike offloads, EFT inbound can’t detect whether the incoming file is Unicode encoded or not, thus we will always hand the file off to the AS2 component, with potential for mixed results. The outcome will be: a) an ASCII encoded filename, b) a failed transaction, or c) an ASCII encoded unique filename. Reference the AS2 Inbound Operations Use Case Cheat Sheet for additional guidance.

RADIUS

EFT 6.4 used 8-bit ASCII. EFT 6.5 will represent as UNICODE strings (internally) and then downgrade to 8-bit ASCII on use. Also limited to ASCII in UI.

RADIUS special cases

RFC says nothing about RADIUS password. EFT 6.4 used 8-bit ASCII. EFT 6.5 uses UTF-8. This difference (between earlier versions of EFT and version 6.5 and the resulting potential loss of fidelity is why this item is included on this list (even though it is UTF-8)

RADIUS usernames and the shared secret can be UTF-8 strings.  

HTTP

Filename integrity maintained. No loss of encoding fidelity. Normal use case. This is essentially 7 and 8-bit ASCII transfers when working with standard ASCII only AS2 clients works perfect.

/n component will fail to process because "????" is an invalid filename. The transfer will result in a failure to write to disk. EFT must log this as an error in eft.log.

Filename integrity is NOT maintained. /n component will process but will convert the filename to a unique 8-bit ASCII filename. However, there won’t be a loss of encoding fidelity.

EFT will log as warning that filename was changed.

Filename integrity is NOT maintained. /n component will process but will convert the filename to a unique 8-bit ASCII filename; There is also a loss of encoding fidelity as it is down converted to ASCII. EFT will log as warning that filename was changed.

AS2 Other/Miscellaneous Limitations

Will fail to generate SDA

Works perfect. Everything preserved

Will fail to extract