9.1.0 and 9.1.1 no longer able to access anonymous S3 bucket like 9.0.3 and prior #16746
Description
Describe the bug
With CyberDuck v9.1.1, I am not able to connect to this S3 bucket, but with CyberDuck v9.0.3 and prior, I am. It seems something has broke in the later versions. Nothing obvious happens when I try to connect - there are no errors or other messages in the program.
bucket address:
s3.amazonaws.com/gov-fpac-rma-pubfs-production
versions I tested:
v8.6.0 (39818) - works
v8.8.2 (41344) - works
v9.0.3 (42112) - works
v9.1.0 (42520) - broke
v9.1.1 - broke
Exception in the debug log:
2025-01-03 12:16:16,203 [background-5] WARN ch.cyberduck.core.threading.BackgroundCallable - Failure running background task WorkerBackgroundAction{worker=MountWorker{cache=Cache{size=0}}}
java.lang.Exception: null
at ch.cyberduck.core.threading.BackgroundCallable.<init>(BackgroundCallable.java:38) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.DefaultBackgroundExecutor.execute(DefaultBackgroundExecutor.java:71) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.AbstractController.background(AbstractController.java:72) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at cli.Ch.Cyberduck.Ui.Controller.BrowserController$$$003C$$003Ec__DisplayClass229_0.<UnmountImpl>b__0(Unknown Source) ~[Cyberduck.exe:?]
at ch.cyberduck.core.threading.BackgroundCallable$1.run(BackgroundCallable.java:64) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at cli.System.Delegate.DynamicInvokeImpl(Unknown Source) ~[mscorlib.dll:?]
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackDo(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Threading.ExecutionContext.RunInternal(Unknown Source) ~[mscorlib.dll:?]
at cli.System.Threading.ExecutionContext.Run(Unknown Source) ~[mscorlib.dll:?]
at cli.System.Threading.ExecutionContext.Run(Unknown Source) ~[mscorlib.dll:?]
at cli.System.Windows.Forms.Control.InvokeMarshaledCallback(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbacks(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Control.WndProc(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Form.WndProc(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.NativeWindow.Callback(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Application$ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoopInner(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoop(Unknown Source) ~[System.Windows.Forms.dll:?]
at cli.Ch.Cyberduck.Ui.Program.Main(Unknown Source) ~[Cyberduck.exe:?]
Caused by: java.lang.NullPointerException
at ch.cyberduck.core.auth.AWSCredentialsConfigurator$2.getAWSAccessKeyId(AWSCredentialsConfigurator.java:112) ~[Cyberduck.Protocols.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at com.amazonaws.auth.AbstractAWSSigner.sanitizeCredentials(AbstractAWSSigner.java:438) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:227) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1349) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1183) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:838) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:805) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:779) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:735) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:717) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:579) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:559) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.doInvoke(AWSSecurityTokenServiceClient.java:1731) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1698) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1687) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.executeGetCallerIdentity(AWSSecurityTokenServiceClient.java:1298) ~[Cyberduck.Protocols.DLL:?]
at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.getCallerIdentity(AWSSecurityTokenServiceClient.java:1266) ~[Cyberduck.Protocols.DLL:?]
at ch.cyberduck.core.s3.S3Session.login(S3Session.java:347) ~[Cyberduck.Protocols.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.KeychainLoginService.authenticate(KeychainLoginService.java:169) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.LoginConnectionService.authenticate(LoginConnectionService.java:163) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.LoginConnectionService.connect(LoginConnectionService.java:154) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:99) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.pool.StatelessSessionPool.borrow(StatelessSessionPool.java:57) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.SessionBackgroundAction.run(SessionBackgroundAction.java:115) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.SessionBackgroundAction$1.call(SessionBackgroundAction.java:106) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.DefaultRetryCallable.call(DefaultRetryCallable.java:52) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:108) ~[Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.BackgroundCallable.run(BackgroundCallable.java:102) [Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at ch.cyberduck.core.threading.BackgroundCallable.call(BackgroundCallable.java:84) [Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:625) [?:1.8.0]
at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57) [Cyberduck.Core.DLL:de7c4824a60166cce2202a8f80e8cf7a43c9b2e0]
at java.lang.Thread.run(Thread.java:955) [?:1.8.0]
To Reproduce
Steps to reproduce the behavior:
- Open CyberDuck 9.1.1
- Configure a connection as the screenshot above shows
- Double click that connection to attempt to connect to it.
- Notice that nothing happens. A brief text change appears in the bottom status bar and the top title bar, but it disappears before I can read it.
- Now, repeat these steps with version 8.6.0, and it will connect fine and show you all the files in the bucket.
Expected behavior
The current version should connect to the S3 bucket and show the files like v9.0.3 and prior did.
Desktop (please complete the following information):
- OS: Windows 11 Pro 24H2
- Version: CyberDuck 9.1.1
Log Files
cyberduck 9.1.1 snipped.log