Sequel-ace: Issues with password protected SSH keys

[categoryshell]

With Sequel Pro, i could add my SSH keys to my session via the terminal and SP would use the session
to authenticate myself with those SSH keys.
The reason i add my SSH keys to my session is that they're password protected and i don't want to enter that password everytime i use that key, that day.

Unfortunately, Sequel Ace ignores this session and asks me for the password every time, which gets quite tedious.
So i said Sequel Ace can store that password in Keychain. After that, Sequel Ace is unable to find/use my key anymore and the SSH connection is out the window.
I need to manually remove that password from Keychain to get it asking for my password again.

Please make Ace working the same as Pro did, and read my SSH session.
Honestly, all my applications do that so i know it's not impossible.

I'm on OSX 10.15.4 and Sequel Ace 2.1.5 build 2073

[Jason-Morcos]

Unfortunately, Sequel Ace is a sandboxed app - we simply cannot share your session like Sequel Pro used to. It sounds like the core issue here is that there is something wrong with the store-password-to-key-in-keychain system if I understand correctly?

[categoryshell]

Then why did you sanbox it? Because it’ a App Store requirement? The place where tools like this don’t belong?

IntelliJ can do it. iTerm2 can do it. You should to it too. This kinda renders the tool useless and makes me keep using the good ol’ Sequel Pro until there is an alternative :)

App Store is evil, and good for Candy Crush. Not dev apps like this :)

[Jason-Morcos]

I'm gonna go ahead and reopen this issue until someone in the @Sequel-Ace/all is able to verify whether or not there may be an issue with remembering ssh key passwords in the keychain so that other users don't encounter this issue!

[matzeso]

@categoryshell
You are not really helping here. You could decide to help move this project forward, answer the questions about the keychain issues for example, but you decide to disencourage people that use their spare time to develop for the community.
You should really try to be more thankful to contributors.

There are people out there that prefer a sandboxed app, especially in companies, because it provides way more security.
Especially in open source projects, it would be easier to introduce backdoors if the app is not sandboxed.

So there is a very valid and good reason for an IT infrastructure related tool to be sandboxed. Also, the app being in the app store gives it creditbility to some extend, which should help boost its usage, which in turn encourages more people to contribute, etc. I don't see any downsides here.

It would be great if you considered giving feedback about the keychain issue - as that is likely a bug that can be fixed.

[wrmoon]

Is this related to #285 I wonder?