Denton Gentry

As of Thursday,`tailscale logout` on an ephemeral node will immediately clean it up: https://tailscale.com/blog/ephemeral-logout/ In 1.30 (expected to be released next week), if tailscale is started with `--state=mem:` it will...

Related: https://github.com/tailscale/tailscale/issues/5285

Since this bug was filed, an API endpoint was added to create an authkey: https://github.com/tailscale/tailscale/blob/main/api.md#tailnet-keys-post An idea being considered is to use the node key of the device to sign...

The current status is that using an API key one can: - create an authkey: https://github.com/tailscale/tailscale/blob/main/api.md#tailnet-keys-post - assign tags to the authkey: https://tailscale.com/blog/acl-tags-ga/ - revoke an authkey: https://github.com/tailscale/tailscale/blob/main/api.md#tailnet-keys-key-delete To set...

Work on being able to renew/replace API keys automatically has started.

The update posted on this issue some time ago: > Work on being able to renew/replace API keys automatically has started. referred to this project. We don't have a timeline...

Related issue: https://github.com/tailscale/tailscale/issues/662

Seriously: we know people want this. We know. I promise we will update this bug when there is progress to report. We're not going to write up estimates of every...

A potential solution which would work now is to start the server in a third tailnet, and then share it into the other two: https://tailscale.com/kb/1084/sharing/ Shared nodes can accept incoming...

The way you describe is the way the service is supposed to work now. When using an exit node: - you can make direct connections from your node to other...