Any plans to add option to disable key expiry? #259

Closed
opened 2025-12-29 01:25:13 +01:00 by adam · 4 comments
Owner

Originally created by @xj25vm on GitHub (Apr 25, 2022).

Tailscale has an option to disable the key expiry. This would be useful for example for laptops out in the field, where a user would be left with no remote access to a server. Is this something which might be considered for implementation at some point?

Originally created by @xj25vm on GitHub (Apr 25, 2022). Tailscale has an option to disable the key expiry. This would be useful for example for laptops out in the field, where a user would be left with no remote access to a server. Is this something which might be considered for implementation at some point?
adam added the bug label 2025-12-29 01:25:13 +01:00
adam closed this issue 2025-12-29 01:25:13 +01:00
Author
Owner

@kradalby commented on GitHub (Jun 12, 2022):

Hi @xj25vm, could you elaborate what you mean by "key expiry"?

Currently pre-authenticated keys will expired, but they are only needed initially when you authenticate the machine. After that the machine should stay authenticated until it logs out or is manually expired.

@kradalby commented on GitHub (Jun 12, 2022): Hi @xj25vm, could you elaborate what you mean by "key expiry"? Currently pre-authenticated keys will expired, but they are only needed initially when you authenticate the machine. After that the machine should stay authenticated until it logs out or is manually expired.
Author
Owner

@xj25vm commented on GitHub (Jun 12, 2022):

Hi. Thank you for looking into this. I was only going by the information found at the page below in the Tailscale docs. It seems to imply that users will have to go again through the process of authenticating after 180 days. I assumed that it applies to Headscale as well, as it implements the Tailscale protocol? It is possible that I am misinterpreting the info below though?

https://tailscale.com/kb/1028/key-expiry/

@xj25vm commented on GitHub (Jun 12, 2022): Hi. Thank you for looking into this. I was only going by the information found at the page below in the Tailscale docs. It seems to imply that users will have to go again through the process of authenticating after 180 days. I assumed that it applies to Headscale as well, as it implements the Tailscale protocol? It is possible that I am misinterpreting the info below though? https://tailscale.com/kb/1028/key-expiry/
Author
Owner

@restanrm commented on GitHub (Jun 13, 2022):

Key expiry is actually not implemented. You should not expect any disconnection with Headscale.

@restanrm commented on GitHub (Jun 13, 2022): Key expiry is actually not implemented. You should not expect any disconnection with Headscale.
Author
Owner

@xj25vm commented on GitHub (Jun 13, 2022):

Perfect - thank you for clarifying!

@xj25vm commented on GitHub (Jun 13, 2022): Perfect - thank you for clarifying!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#259