Skip to content

sftp-handler 0.14 test version (FTP: ZitaFTP big folders)

Pre-release
Pre-release

Choose a tag to compare

@orgin orgin released this 18 Nov 05:00
· 6 commits to main since this release

This is a test version of 0.14. Please try it before it goes to OS4Depot, where the current stable release is 0.9. It is the 0.14 release candidate: only the file name says beta. It replaces the 0.12 test version.

sftp-handler is an AmigaOS 4 filesystem handler: the device SFTP: shows each FTP and SFTP site you have set up as a folder. Sites are added with the prefs program sftphprefs.

New in 0.14

  • FTP: big folders on ZitaFTP Server no longer end in "No disk present", and they open much faster. Workbench reads only the start of each file in a folder it opens (to choose its icon), so most downloads are cut short. ZitaFTP often sent no reply for that, and the handler waited 5 seconds and logged in again for every such file. Sometimes it sent one reply too many, the handler got out of step with the server, and every file after that failed. Cut downloads now end with ABOR, and late replies are dropped.

Also new since 0.9

  • Clearer messages instead of "Error -1": a server that refuses to save a file gives "file is write protected", "file too large" gives "disk is full" (0.13).
  • FTP: when a server has no data connection free ("425 cannot open data connection"), the handler waits and asks again (0.12).
  • Works with AmiSSL 6, and with every AmiSSL 5 from 5.1 on (0.11).
  • SFTP two-factor logins (verification codes from an authenticator app) (0.11).
  • New icons in the AmigaOS 4.1 style, and a volume icon for SFTP: (0.11).

Install

Download SFTPHandler_beta.lha, unpack it and double-click Install. It can update an installed 0.9 or any earlier test version, even while SFTP: is mounted. SFTPHandler.guide has the details.

Requirements: AmigaOS 4.1, filesysbox.library 54.8, clib4.library 2.5 or newer, and for SFTP AmiSSL 5 (5.1 or newer) or AmiSSL 6.

Feedback

Please report problems in the issues: the server software, what you did, and what happened. Adding DEBUG to the DOSDriver's Startup line writes details to the debug output (DumpDebugBuffer); a server log (such as ZitaFTP's) helps too.