Background ssh requests - Codinn Core Tunnel

nigelm

I use Codinn's Core Tunnel to manage ssh tunnels.

Starting recently (April 2023), when I start a tunnel up (click on menu app entry), rather than getting a 1Password ssh authorization window, I now get a notification dot on the 1Password menu bar entry, and have to notice that, click through the 1Password menu SSH request waiting and then auth the request.

Is there a way I can select which items go to a background request and which are seen as foreground?

---

1Password Version: 8.10.4
Extension Version: Not Provided
OS Version: MacOS 13.3.1
Browser:_ Not Provided

floris_1P

That's a bug we fixed recently. The fix is available already if you switch to the beta channel in the 1Password settings.

saynain

Hi @floris_1P

I have same issue when trying to run a script from Raycast.

I have a script that performs a SSH command with certain parameters. When I trigger it manually from the terminal, it works as expected and I get prompted to authorise SSH access.
But when I run it from Raycast, I get a notification dot on the 1password menu bar and have to click though the "SSH request waiting" and then authorise the request.

Is the fix you mentioned still in beta?

1Password version:
1Password for Mac 8.10.15 (81015001)

Mac version:
Ventura 13.4.1

floris_1P

@saynain Thanks for reporting, we'll have a look! Which Raycast extension are you using?

saynain

I am using the script command extension where I use my own custom bash script.

The script I have created looks like this:

#!/bin/bash

# Required parameters:
# @raycast.schemaVersion 1
# @raycast.title <name>
# @raycast.mode fullOutput

# Optional parameters:
# @raycast.icon ...
# @raycast.argument1 { "type": "text", "placeholder": "Hostname" }
# @raycast.argument2 { "type": "text", "placeholder": "Username" }

# Setting TERM variable defines the terminal type. In other words, it sets the terminal type for which output is to be prepared.
# For the SSH command, the options -ttyq are used to get connected as fast as possible and -q removes the connection closed message.
TERM=xterm-256color ssh -ttYq user@hostname "command on remote host with arguments $1 and $2"

My .ssh/config looks like this with a link to agent.sock:

# 1Password integration
Host *
    IdentityAgent "~/.1password/agent.sock"

When I run the script from the terminal while 1Password is locked, I get prompted for authorisation from 1Password. After I have authorised it works to run both from the terminal and from Raycast.
When I run the script from Raycast while 1Password is locked, it just shows this icon in the toolbar and I have to click on "SSH request waiting" and then authorise the request:

floris_1P

@saynain The fix for Raycast will be out in this weeks beta release. It's already available now on the nightly channel.

saynain

Thank you @floris_1P ! Switched to nightly and it works like a charm now :) Do you have an estimate for when the fix will be available in production version?
Thanks for the great and fast response on this one.

floris_1P

I'd expect it to be available in the production release somewhere next month.