# Prompt for SSH private key passphrase on every connection

**URL:** <https://community.gotempest.app/t/prompt-for-ssh-private-key-passphrase-on-every-connection/37>\
**Category:** General\
**Tags:** desktop\
**Created:** [October 20, 2026, 8:18am UTC](https://community.gotempest.app/t/prompt-for-ssh-private-key-passphrase-on-every-connection/37 "2026-10-20T08:18:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mosi](https://community.gotempest.app/letter_avatar_proxy/v4/letter/m/ecd19e/32.png) [@Mosi](https://community.gotempest.app/u/Mosi)\
**Post date:** [October 20, 2026, 8:18am UTC](https://community.gotempest.app/t/prompt-for-ssh-private-key-passphrase-on-every-connection/37/1 "2026-10-20T08:18:25Z")

</div>

Hello,

I’m using Tempest on macOS with an existing RSA private key protected by a passphrase.

The connection works perfectly with OpenSSH. However, in Tempest, when I leave the key passphrase field empty, authentication fails instead of prompting me for the passphrase.

Is there a way to make Tempest prompt for the private key passphrase on every SSH connection, without storing or caching the passphrase?

Thanks a lot,  
Mosi

---

<div class="post-metadata">

**Author:** ![tearfulDalvik](https://community.gotempest.app/user_avatar/community.gotempest.app/tearfuldalvik/32/25_2.png) [@tearfulDalvik](https://community.gotempest.app/u/tearfulDalvik)\
**Post date:** [October 21, 2026, 5:03am UTC](https://community.gotempest.app/t/prompt-for-ssh-private-key-passphrase-on-every-connection/37/2 "2026-10-21T05:03:42Z")

</div>

Hi Mosi,

Thanks for your feedback! We’ll add this  
in the next release.

Best regards

---

<div class="post-metadata">

**Author:** ![tearfulDalvik](https://community.gotempest.app/user_avatar/community.gotempest.app/tearfuldalvik/32/25_2.png) [@tearfulDalvik](https://community.gotempest.app/u/tearfulDalvik)\
**Post date:** [October 25, 2026, 4:11pm UTC](https://community.gotempest.app/t/prompt-for-ssh-private-key-passphrase-on-every-connection/37/4 "2026-10-25T16:11:41Z")

</div>

Hi Mosi,

This problem has been fixed in the latest v3.17.4, please try it out 🙂
