Commit
4777118
why do i have to specify BRIDGE_SSH_PUBLIC_KEY? can't it be derived?
It can. Dropped BRIDGE_SSH_PUBLIC_KEY: the server now derives it with
ssh-keygen -y at start (checked in Docker with a throwaway key). Delete that line from your env. Pushed 5f49450 to PR #1 @dtinthActually, can't you generate for yourself a private key on the first start? Then the web interface can display the public key to add to the GitHub as SSH key for authentication. This way the key material stays with the service completely and I do not have to do any key exporting.
Yes, good idea. Round:
❓ Q1 Generate an ed25519 key on first start, kept on the data volume so it survives redeploys?
➡️ yes
❓ Q2 Remove BRIDGE_SSH_PRIVATE_KEY entirely (no env key path)?
➡️ yes…
GitHubGitHub · Change is constant. GitHub keeps you ahead. · GitHubJoin the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.
Done: the server makes its own key on first start (kept on the volume), and a Bot key page shows it and whether GitHub lists it. bridge.env needs no SSH key now. Pushed cb40440 to PR #1 @dtinth
I deployed the branch here:…
Server is up. Approve: /approve?code=ZPKF-KKQM (check it shows ZPKF-KKQM). Login expires in 10 min.
Export/import page:
❓ Q1 Export downloads a sqlite backup; import uploads one and replaces threads, subscriptions and messages, but keeps tokens and the bot key?
➡️ yes
Logged in, thanks. status works against the server: poller running, 21 messages stored.
I saw https://dev-null.sh/@Gaurav-Gosain/commits/01a15a1a-26bf-7125-817c-428245142447 and it got me wondering, is it possible to build like an ssh server that allows anyone to commit with their own ssh key? e.g.
echo something | ssh remote commit. Not sure if agent forwarding…
/dev/nullGaurav Gosain (@Gaurav-Gosain) on /dev/null: “this platform should definitely have a TUI served over ssh (:”this platform should definitely have a TUI served over ssh (:
Yes, but only with agent forwarding (ssh -A). A commit is an
ssh-keygen -Y sign signature, and the script already signs through an agent, so the server could reuse your forwarded agent:
↳…GitHubdev-null.sh/resources/scripts/commit.sh at 41d9ecbeb1c2b72774ba13b4cac3f1fa12da0060 · dev-null-sh/dev-null.sha social media for devs. Contribute to dev-null-sh/dev-null.sh development by creating an account on GitHub.
Try building one? But which tech stack would you use?
Happy to. Before I build:
❓ Q1 Stack: Go with charmbracelet/wish? It supports agent forwarding, and Go makes a single binary.
➡️ Yes
❓ Q2 Signing: run dev-null's own commit script with SSH_AUTH_SOCK set to your forwarded agent, so nothing is reimplemented?
➡️ Yes…
Go sounds nice. It becomes its own ssh server? Can -A be set with ~/.ssh/config? Thinking if it is possible to implement ssh server in Go so it runs om its own port so there is no shelling out anywhere
Yes, it can be its own SSH server on its own port: wish embeds a Go SSH server, so no sshd is involved. And -A can go in ~/.ssh/config:
Host devnull
HostName <host>
Port <port>
ForwardAgent yes
❓ Q2 (revised) No shelling out: Go builds the SSHSIG signature itself, has…
Yes. Let's do as a separate repo as you suggested.
Built and tested locally: Go with charm.land/ssh, no shelling out. A real
ssh -A posted commits to a local dev-null.
One change to Q5: ssh logs in with the first key in your agent, which may not be your GitHub key. So the server asks dev-null's key-lookups which agent key is…Give me a grant request code (pull latest dtinth/claw)
Grant request code for dtinth/devnull-ssh: 3ZHXGS (expires in 15 min). I'm waiting on it and will push once it's approved. The repo also has to exist first. @dtinth
3ZHXGS expired before it was approved. Reply when you're at the claw dashboard and I'll post a fresh code right away. @dtinth
commit 4777118