The FTP Accounts option in the Home tab opens the FTP account manager where you can create FTP accounts on a per-server basis. These FTP accounts are used for FTP Open, FTP Save As, and the FTP Browser.
All SFTP and FTPS transfers are encrypted. The encryption algorithm is negotiated with the server. If any of these are set the transfer dialogs will show a "lock" symbol indicating the transfer is secure.
Password
The password of the FTP account to use to authenticate on the server during connection. This should be the password for the username as provided by the site administrator, or for anonymous login this might be the email address of the user. Note: If the password is saved it is encrypted and stored on the system. However, the encryption mechanism is unsophisticated and should not be relied upon as a method of security.
No Password
Check this checkbox if your account does not have a password and UltraEdit will send the server a blank / null password. You will not be prompted to enter a password upon connection.
Connection Limit
This setting limits the number of concurrent connections that UltraEdit's FTP client will make with the server. For example, if you select 10 files to open or save via FTP, and your connection limit is set to 4,, the selected files would be transferred in blocks of 4 or less until all selected files are transferred.
Initial Directory
This is the initial directory to change to on the FTP server after the connection has been established. This setting is not required. If this is not set, UltraEdit will remember the last directory for the account when connecting to the server.
Initial Local Directory
This is the initial local directory used when connecting to the FTP server. This is only used on the local pane of the FTP browser. This is not required. If this is not set, UltraEdit will default to your user account's Documents folder.
Server Type
For most FTP servers the default "Auto" or "Unix" should work without problem. However, for other special FTP server types, you may need to configured this as appropriate. Currently supported are:
LIST Command Filter
The LIST Command Filter allows you to set the filter arguments to be used when the LIST command is issued. On most FTP servers, if "-al" is passed, a full listing including hidden files is returned. You can also pass wildcards. For example "*.txt" would list all .txt files. Note that some servers (VMS, MVS, etc) do not handle filter arguments like Unix/Linux servers.
Name Index
This allows you to specify the column number where the name of the file is stored. The default for this value is "-1". This should not be changed unless you're sure of the value that should be used.
Size Index
This allows you to specify the column number where the size of the file is stored. The default for this value is "-1". This should not be changed unless you're sure of the value that should be used.
Use MDTM and SIZE
If the modified time and size of files does not appear to be returned correctly, try selecting this option to force these values to be explicitly requested for every file returned in the directory listing. Selecting this will likely cause slower FTP performance.
Passive transfers
This checkbox should be set with most FTP accounts, especially for servers using a firewall. Because FTP is a port-hopping protocol (i.e., data channels use a random port chosen during the communication), many firewalls have the ability to understand the FTP protocol and allow the secondary data connections. However if the control connection is encrypted using any method, then the firewall is not able to get the port numbers of the data connections from the control connection (since it is encrypted and the firewall cannot decrypt it). Therefore in many firewalled networks clear FTP connections will work while SFTP/FTPS connections will either completely fail or require the use of passive mode.
Do not use IP address returned by server
This can only be set when the Passive Transfer option is selected. This option forces the account to use the IP Address specified by the firewall when connecting to the server. Please note: If you do not control the server you're connecting to or are not sure of its content, there might be a security risk involved in selecting this option.
Local Copy Directory
This allows you to specify where a local copy of the file should be automatically saved when an existing file is transferred to an FTP server via the FTP Save command (not Save As). The local copy is created before the file is transferred to the server. If another local file exists with the same name, it will be overwritten without warning. Leave this blank for no local copy.
Cache password for session if not saved
If this is checked, once entered, the password for the account is cached for the period UltraEdit is running and will not need to be re-entered. If the password is entered incorrectly and needs to be changed, then open and close the Accounts dialog to clear out the cache.
Default Transfer Type
This allows you to specify ASCII or Binary as the default transfer type. ASCII transfers will attempt to convert line terminators in plain text files between server and client. Binary transfers avoids this, and files are transferred byte-for-byte with no conversion. Depending on the FTP server/client, an ASCII transfer may corrupt the file since it is a 7-bit transfer. For this reason, Binary is the recommended transfer type.
Use Proxy
Checking this activates the proxy settings and configures this account to connect through the proxy you specify. If you're connecting directly to the Internet, the proxy settings most likely shouldn't be enabled. If connecting via a proxy on a LAN it will likely be necessary to configure the proxy settings.
The authentication method must be supported by the server. For SFTP, the private key used should be in PPK format. For FTPS, a certificate encapsulated in the PEM or PFX format should be used. PFX files with multiple certificates are not currently supported.
You can activate UltraEdit / UEStudio and unlock trial mode by entereing your license ID and password into the activation dialog. (You receive your license ID and password via email after placing a successful order online, over the phone, or via purchase order.)
After entering your license ID and password, click the Activate button to finalize the activation and unlock trial mode. After your license ID and password have been validated, you should see a dialog indicating that the activation was successful:
Please note: If you purchased an IDM All Access subscription license, you will only need to activate your license one time. Once one IDM application has been activated on the system with the All Access license, all other IDM applications on that system will be automatically activated as well.
If necessary, click the Support options button and then the Proxy button to input proxy server information. For most users this should not be necessary as all IDM applications will use the proxy settings specified for Internet Explorer, if configured, on the system.
If online activation is not possible because there is no Internet connection available, you will need to use the offline activation dialog to register. To access the offline activation options, press Ctrl + Shift, then click the Activate button in the Activation dialog. This will open the offline activation dialog as shown below.
The License ID and Password fields must be entered as provided in your license email. The User Code 1 and User Code 2 fields will be pre-populated with numeric values. You must call or email this information to [email protected] in an email, and we will reply with the value to enter into the Authorization Code 1 field.
Please note: If any values other than those provided by IDM Computer Solutions, Inc. are entered here, this will cause the values in the user code fields to be recalculated the next time the offline activation dialog is opened. Please do not enter any values except those provided by our support team.
I was very excited about the built-in Telnet/SSH terminal that comes with UltraEdit, but it stops working after entering the connection password. Any UltraEdit users out there in the Kawasaki universe?
I was wondering the same thing since I am using Linux for a few weeks now and just cannot get the communication via telnet working properly.
Arrow keys/backspace do(es) not work, SEND/LOAD does not work (HUGE ISSUE), always have to press some key in order to execute the command I just wrote...
Wouldn't have anything against a convenient and powerful editor for Linux
We include an option, by design, that allows the user to *not* save the password, and instead enter the password on a per FTP session basis. This would provide the highest level of security. If the user decides to have UltraEdit save the FTP password in the INI, it is encrypted for the benefit of the user moving their settings from one system to another. However, even with the highest level of encryption of the saved password, if the user decides to save their password in the INI, there will always be a level of vulnerability as a result of the users decision to save the password. References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to n...@nist.gov.
b1e95dc632