Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not using SSH Agent when choosing SSH key. Asking for passkey every time. #1951

Open
eLCHuRiZO opened this issue Jan 9, 2024 · 3 comments
Open
Labels

Comments

@eLCHuRiZO
Copy link

  • Sequel Ace Version (including build number): 4.0.13 Build 20062
  • Sequel Ace Source (App Store/GitHub/Homebrew): App Store
  • macOS Version: 14.2.1
  • Processor Type (Intel/Apple): Apple
  • MySQL Version: Any
  • macOS Localization: English US

Is Issue Present in Latest Beta?

Description
SSH Key's passkey is requested for every connection, even when that identity file is loaded by the SSH Agent.
The Key's passkey isn't only requested once, it's requested every time I establish a connection.

Steps To Reproduce

  1. Create a connection entry using SSH Key authentication.
  2. Connect to that new entry. That's gonna ask you for the passkey regardless of having the identity loaded.
  3. Without closing the app, connect a second time. You'll be asked to enter the passkey again.

Expected Behaviour

The behavior when using Sequel Pro was to use the SSH Agent, so that if the identity had already been loaded, then there's no need to enter the passkey again. In the case that the identity hadn't been loaded, after entering the passkey it's kept loaded.

Related Issues
Couldn't find related issues at this time.

Additional Context
I'm NOT saving the passkey in the keychain. I don't use Apple's keychain.
I'm not attaching a screenshot as there's no particular screen that would help.
Tried this both on Intel and M3.

@Jason-Morcos
Copy link
Member

I'm at a loss on this one. Sequel Ace is designed to use the macOS Keychain which is incredibly secure. If you'd like to use the agent itself, that's probably not supported and that would be a feature request but probably a very low-priority one at that. Not sure if others have info or ideas here

@eLCHuRiZO
Copy link
Author

Okay! Back to Sequel Pro then :)

Thank you for your answer

Kindly,
Elrond Churizo

@Kaspik
Copy link
Member

Kaspik commented Apr 2, 2024

We use old deprecated keychain API, and we will have to migrate to the new one soon. That might fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants