· David Kocher · Posted in Cyberduck
Cyberduck speaks to a lot of servers, and every server interprets a protocol slightly differently. To catch incompatibilities before you do, we have greatly extended the automated test coverage. Integration tests now run against disposable containers started with Testcontainers, instead of a handful of hosted accounts and embedded test servers.
Tests against hosted services depend on shared credentials, network access and the state of someone else's server. Containers are reproducible: each server is started on first use, shared for the lifetime of the test run and thrown away afterwards. Anyone can run the same tests on their own machine with Docker.
Cyberduck
Mountain Duck
CLImod_sftp and SFTPGo. See #18622.mod_dav and SFTPGo. See #18622.The same test is run once per server implementation, and the Cryptomator vault tests additionally per vault version. Where a server legitimately does not implement a feature, such as server side copy, symbolic links or partial uploads, the test is skipped with a stated reason rather than silently passing.
The tests are part of the source code. If a server you rely on is missing, or you see a difference in behavior between implementations, open an issue or send a pull request.
· David Kocher · Posted in Cyberduck
With Cyberduck 9.5 with have adopted the user interface for Liquid Glass, but the application icon with the duck objects tinted colours always remaining yellow and escapes the squircle jail imposed by default on application icons on macOS 26. We posted about this on @cyberduck back in September last year.
With the recent blog post Free the Icons from Paul Kafasis this has again gained some traction from other developers and we sure hope others join like the fine folks from Cryptomator. The application icon of Mountain Duck concedes we have to admit.
For the technically interested, this is implemented as a simplistic Dock Tile Plugin.
· David Kocher · Posted in Mountain Duck
Mountain Duck 5.3 and later runs natively on Windows 11 for ARM.
· David Kocher · Posted in Cyberduck
Cyberduck 9.5 adopts user interface changes known as Liquid Glass in macOS Tahoe. Besides rounded corners, the update also includes other refinements the list of bookmarks and editing connection details in the bookmark window.
Controls for unavailable connect options depending on the current protocol selection are hidden but the Open Connection window now features the all available options likewise the Edit Bookmark window. Non-frequent options have been moved to a More Options tab. Additionally a Connect button is available when editing a bookmark.
in the main window, the navigation bar is only shown in list and outline view but not when not applicable when displaying bookmarks. Additionally a progress indicator is shown for the bookmark when a connection is being opened.
You can read the full details in the changelog.
· David Kocher · Posted in Cyberduck, Mountain Duck
Managing access to Amazon S3 across multiple AWS accounts and users has traditionally required juggling access keys, secret credentials, and complex IAM policies. With support for AWS IAM Identity Center (formerly AWS Single Sign-On) now available in Cyberduck 9.5.0 and Mountain Duck 5.3.0, connecting to S3 has never been easier or more secure.
AWS IAM Identity Center is AWS’s centralized access management solution that lets users sign in once using their existing corporate credentials—whether that’s through Okta, Microsoft Entra ID (formerly Azure AD), or other identity providers. Instead of managing permanent access keys, users get short-lived credentials that automatically expire, significantly improving your security posture.
Traditional S3 access requires creating and managing AWS access keys for each user. These long-lived credentials pose security risks if accidentally exposed or shared. IAM Identity Center solves this by:
Setting up IAM Identity Center authentication for S3 requires two main steps:
First, enable IAM Identity Center in your AWS account and configure your identity source. You can use AWS’s built-in directory or connect to an external identity provider like Microsoft Entra ID or Okta. Create a permission set that defines what S3 resources users can access—for example, read-only or full access to specific buckets. Add users through IAM Identity Center (or sync them from your external identity provider) and assign them to AWS accounts with the appropriate permission sets. Users will receive an invitation to set up their access to the AWS access portal.
Creating a connection is straightforward:
The browser will redirect back to the application, and you’re connected—no access keys to copy or store.
For teams already using the AWS CLI, Cyberduck and Mountain Duck can read configuration directly from your ~/.aws/config file. Simply configure your profile once with aws configure sso, allowing you to skip the manual input.
AWS IAM Identity Center support is available now in Cyberduck 9.5 and Mountain Duck 5.3. For detailed setup instructions and configuration options, check out our complete tutorial.