Skip to content

Fix sentinel connect unstable#75

Merged
hsinatfootprintai merged 2 commits intomainfrom
fix---sentinel-connect-unstable
Mar 31, 2026
Merged

Fix sentinel connect unstable#75
hsinatfootprintai merged 2 commits intomainfrom
fix---sentinel-connect-unstable

Conversation

@hsinatfootprintai
Copy link
Copy Markdown
Contributor

No description provided.

hsinhoyeh and others added 2 commits March 31, 2026 16:57
When a tunnel client reconnects, the sentinel was allocating a new
loopback IP (e.g., 127.0.0.23 → 127.0.0.27) while sshpiper config
still referenced the old IP, causing SSH "Permission denied" errors
until the next key sync cycle (30-60s window).

Now reuse the same loopback IP for the same spot ID across reconnects,
eliminating the stale sshpiper config window.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Two issues prevented `ssh user@host "command"` from working:

1. containarium-shell only checked SSH_ORIGINAL_COMMAND (set by ForceCommand),
   but sshpiper forwards exec requests as `shell -c "command"`. Now handles
   both the -c argument and SSH_ORIGINAL_COMMAND.

2. sshpiper's authorized_keys parser stopped at blank lines, never reaching
   the user's key. keysync now strips blank lines and comments before writing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hsinatfootprintai hsinatfootprintai force-pushed the fix---sentinel-connect-unstable branch from f957719 to c33bcb7 Compare March 31, 2026 09:00
@hsinatfootprintai hsinatfootprintai merged commit abebf65 into main Mar 31, 2026
3 checks passed
@hsinatfootprintai hsinatfootprintai deleted the fix---sentinel-connect-unstable branch March 31, 2026 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants