maxgoedjen/secretive

Git LFS enabled repository requests confirmation three times (via Apple Watch), fails on third

Open

#222 opened on Jun 1, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Swift (8,522 stars) (199 forks)batch import
bughelp wanted

Description

I have a Git LFS enabled git repository. When I try to push (with a commit unknown to remote), it

  1. triggers a dialog "SecretAgent" is trying to sign a request from "launchd" using secret "ssh". Since I have an AppleWatch, I can double tap to confirm.
  2. It again triggers the same dialog "SecretAgent" is trying to sign a request from "launchd" using secret "ssh" again I can confirm with the AppleWatch
  3. It again triggers the same dialog "SecretAgent" is trying to sign a request from "launchd" using secret "ssh" This time my watch get's the notification, I can double tap, but the confirmation does not change anything and I am left with the open dialog for which I then have to click on "Use password..." and enter the password manually.

I have two questions

  1. Is there a way to only make the process ask for confirmation once?
  2. Is there a way to fix the third time request to sign to make it work with the Apple Watch?

Furthermore: What steps can I take to aid in the resolution?

macOS 11.4 (20F71) Secretive 2.1.0 (1.494736918)

Contributor guide

Tech stack
swift
Domain
securityauthentication
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
SwiftmacOS securitySSH/Git LFSSecretive internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the SSH signing request handling in Secretive, particularly the dialog presentation logic for multiple consecutive requests. Look for timeouts or state management issues that cause the third confirmation to fail. Review the Apple Watch confirmation flow in the codebase, and consider adding a single confirmation per session option. Test with Git LFS over SSH.