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 (199 forks)batch import
bughelp wanted

Repository metrics

Stars
 (8,522 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Investigate why Git LFS triggers three SSH signing requests, and why the third fails with Apple Watch confirmation. Examine Secretive's SSH agent interaction with Git LFS and the Secure Enclave signing flow. Check for potential race conditions or timeout issues.
Tech stack
swift
Domain
authenticationsecurity
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSSHmacOSApple Watch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40