In general, maybe security code (which is what this is) might not be the best place for AI.

> This is why you don't let Claude handle versioning and the release process.

Or anything else without reviewing it.

lol @ the issue in the repo: "module declares its path as: github.com/yourusername/ts-ssh"

- 0.0.1 -> improvements

- 0.1.0 -> breaking changes

- 1.0.0 -> overhaul/refactor needed

I know not every case is easy but this is my rule of thumb. I've honestly never needed a major version change

Semantic versioning isn’t the only way of versioning. Linus Torvalds versions Linux how he sees fit.

You can start your own ssh daemon from the unprivileged account pointing to a random port.

Can you explain what the possible risks are?

> I am scared that this is vibe coded

Totally serious question: would you feel better about this piece of software, if you didn't know that it was vibe coded?

Do we need "build without AI" stickers on every piece of software created these days?

I agree and had the same thought. Tailscale ssh is good and I was interested in something like this but absolutely not if it’s AI generated garbage.

You need one of the following:

Google, Microsoft, Github, Apple or your own OIDC Provider.

They do not have their own account backend.

So you dont technically need a FAANG account if you have a Gitea, Gitlab, Authentik Account or something like that.

Since April 2023 they support custom OIDC providers[1], and as of April 2024 that was extended to the free plan as well[2], so you can bring your own auth.

[1]: https://tailscale.com/kb/1240/sso-custom-oidc

[2]: https://tailscale.com/blog/sso-tax-cut

It's possible to use Tailscale with just a passkey [0], but it's a weird process because they don't let you create a tailnet and a passkey account at the same time. Instead, you need to create an account with a throwaway FAANG credential and send yourself an invite to that account's tailnet, and then use that invite to create a passkey-linked Tailscale account. This account can then create its own tailnet, at which point the original tailnet (and the throwaway FAANG account) can be discarded.

It's a weird process and not particularly user friendly (passkey accounts are tied to a specific passkey and can't have additional ones added, so you need to create a new account if you, say, migrate from one hardware key to another). Hopefully they improve the process before passkey support goes out of beta.

[0] https://tailscale.com/kb/1269/passkeys

You can also use Codeberg.

not sure, but i think this may be a special feature for Show HNs

Show HN's get to have text and a link, most other things don't.