cyberduck
cyberduck copied to clipboard
iterate-ch
Crashing only on specific bookmark
Describe the bug After restarting the application, some saved SFTP bookmarks would prompt for a .pem even though it is already configured. You can even edit the config the see that it is correctly configured.
Doing any action (clicking cancel, selecting the original correct .pem or even selecting a random .pem) would crash the application.
The work around I've found is to edit the config for my bookmark SSH private key to "none", then again going back to select the correct .pem.
As long as I do not close the application I can disconnect and open a new window to connect as many times without facing the issues.
This bookmark is not any way special or different from the other bookmarks I have. Recreating this bookmark with a different name does not help.
To Reproduce Steps to reproduce the behavior:
- Start application
- Create SFTP bookmark with SSH private key
- Connect successfully for testing the bookmark is valid
- Disconnection and close the application
- Start application again
- Double click on the bookmark created in step 2
- See that the application prompts for SSH private key
- Do anything
Expected behavior The application should not crash
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: macOS
- Version 12.5.1 (m1)
Log Files No new error visible in log files. (Sorry will not be posting debug logs as it contains private information, including and not limited to some of my actual SSH keys)
Additional context
Process: Cyberduck [26403]
Path: /Applications/Cyberduck.app/Contents/MacOS/Cyberduck
Identifier: ch.sudo.cyberduck
Version: 8.4.3 (38269)
App Item ID: 409222199
App External ID: 851648099
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2022-08-23 11:21:25.1403 +0800
OS Version: macOS 12.5.1 (21G83)
Report Version: 12
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000103124000
Exception Codes: 0x0000000000000002, 0x0000000103124000
Exception Note: EXC_CORPSE_NOTIFY
Can you post the full crash report in particular including the stacktrace for Crashed Thread 0.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x192ae6d98 __pthread_kill + 8
1 libsystem_pthread.dylib 0x192b1bee0 pthread_kill + 288
2 libsystem_c.dylib 0x192a56340 abort + 168
3 libc++abi.dylib 0x192ad6b08 abort_message + 132
4 libc++abi.dylib 0x192ac6950 demangling_terminate_handler() + 336
5 libobjc.A.dylib 0x1929bc320 _objc_terminate() + 144
6 libc++abi.dylib 0x192ad5ea4 std::__terminate(void (*)()) + 20
7 libc++abi.dylib 0x192ad8c1c __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 36
8 libc++abi.dylib 0x192ad8bc8 __cxa_throw + 140
9 libobjc.A.dylib 0x1929b3f6c objc_exception_throw + 420
10 Foundation 0x193ba0e88 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 204
11 AppKit 0x195a82584 -[NSApplication endSheet:returnCode:] + 136
12 libjnidispatch.dylib 0x10716004c 0x107150000 + 65612
13 libjnidispatch.dylib 0x10715ea18 0x107150000 + 59928
14 libjnidispatch.dylib 0x107156814 0x107150000 + 26644
15 libjnidispatch.dylib 0x107156be8 Java_com_sun_jna_Native_invokeVoid + 44
16 ??? 0x112b9ba0c ???
17 ??? 0x112de0700 ???
18 ??? 0x190000 ???
Is this Bug resolved as I notice the other thread on this has been closed out? Is there an update or new version out?
As a workaround please move the private key to the {{.ssh}} folder in your home directory.