Juan Font a0cc20bef9 Ephemeral keys can now be reusable and non-reusable ... Fixes the issue reported in #1712. In Tailscale SaaS, ephemeral keys can be single-user or reusable. Until now, our ephemerals were only reusable. This PR makes us adhere to the .com behaviour.		2024-03-03 10:11:10 +00:00
..
api_key_test.go	Replace the timestamp based state system	2023-09-19 10:20:21 -05:00
api_key.go	Replace database locks with transactions (#1701)	2024-02-08 17:28:19 +01:00
db.go	drop unused last_successful_update field from node table (#1754)	2024-02-18 23:22:07 +01:00
ip_test.go	new IP allocator and add postgres to integration tests. (#1756)	2024-02-18 19:31:29 +01:00
ip.go	new IP allocator and add postgres to integration tests. (#1756)	2024-02-18 19:31:29 +01:00
node_test.go	Replace database locks with transactions (#1701)	2024-02-08 17:28:19 +01:00
node.go	new IP allocator and add postgres to integration tests. (#1756)	2024-02-18 19:31:29 +01:00
preauth_keys_test.go	Ephemeral keys can now be reusable and non-reusable	2024-03-03 10:11:10 +00:00
preauth_keys.go	Ephemeral keys can now be reusable and non-reusable	2024-03-03 10:11:10 +00:00
routes_test.go	new IP allocator and add postgres to integration tests. (#1756)	2024-02-18 19:31:29 +01:00
routes.go	Replace database locks with transactions (#1701)	2024-02-08 17:28:19 +01:00
suite_test.go	new IP allocator and add postgres to integration tests. (#1756)	2024-02-18 19:31:29 +01:00
users_test.go	Replace database locks with transactions (#1701)	2024-02-08 17:28:19 +01:00
users.go	Replace database locks with transactions (#1701)	2024-02-08 17:28:19 +01:00