3ec5be3f51
This file was never truly necessary and has never actually been used in the history of Tailscale's open source releases. A Brief History of AUTHORS files --- The AUTHORS file was a pattern developed at Google, originally for Chromium, then adopted by Go and a bunch of other projects. The problem was that Chromium originally had a copyright line only recognizing Google as the copyright holder. Because Google (and most open source projects) do not require copyright assignemnt for contributions, each contributor maintains their copyright. Some large corporate contributors then tried to add their own name to the copyright line in the LICENSE file or in file headers. This quickly becomes unwieldy, and puts a tremendous burden on anyone building on top of Chromium, since the license requires that they keep all copyright lines intact. The compromise was to create an AUTHORS file that would list all of the copyright holders. The LICENSE file and source file headers would then include that list by reference, listing the copyright holder as "The Chromium Authors". This also become cumbersome to simply keep the file up to date with a high rate of new contributors. Plus it's not always obvious who the copyright holder is. Sometimes it is the individual making the contribution, but many times it may be their employer. There is no way for the proejct maintainer to know. Eventually, Google changed their policy to no longer recommend trying to keep the AUTHORS file up to date proactively, and instead to only add to it when requested: https://opensource.google/docs/releasing/authors. They are also clear that: > Adding contributors to the AUTHORS file is entirely within the > project's discretion and has no implications for copyright ownership. It was primarily added to appease a small number of large contributors that insisted that they be recognized as copyright holders (which was entirely their right to do). But it's not truly necessary, and not even the most accurate way of identifying contributors and/or copyright holders. In practice, we've never added anyone to our AUTHORS file. It only lists Tailscale, so it's not really serving any purpose. It also causes confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header in other open source repos which don't actually have an AUTHORS file, so it's ambiguous what that means. Instead, we just acknowledge that the contributors to Tailscale (whoever they are) are copyright holders for their individual contributions. We also have the benefit of using the DCO (developercertificate.org) which provides some additional certification of their right to make the contribution. The source file changes were purely mechanical with: git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g' Updates #cleanup Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d Signed-off-by: Will Norris <will@tailscale.com>
167 lines
4.4 KiB
Go
167 lines
4.4 KiB
Go
// Copyright (c) Tailscale Inc & contributors
|
|
// SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
package tailscale
|
|
|
|
import (
|
|
"bytes"
|
|
"context"
|
|
"encoding/json"
|
|
"fmt"
|
|
"net/http"
|
|
"time"
|
|
)
|
|
|
|
// Key represents a Tailscale API or auth key.
|
|
type Key struct {
|
|
ID string `json:"id"`
|
|
Created time.Time `json:"created"`
|
|
Expires time.Time `json:"expires"`
|
|
Capabilities KeyCapabilities `json:"capabilities"`
|
|
}
|
|
|
|
// KeyCapabilities are the capabilities of a Key.
|
|
type KeyCapabilities struct {
|
|
Devices KeyDeviceCapabilities `json:"devices,omitempty"`
|
|
}
|
|
|
|
// KeyDeviceCapabilities are the device-related capabilities of a Key.
|
|
type KeyDeviceCapabilities struct {
|
|
Create KeyDeviceCreateCapabilities `json:"create"`
|
|
}
|
|
|
|
// KeyDeviceCreateCapabilities are the device creation capabilities of a Key.
|
|
type KeyDeviceCreateCapabilities struct {
|
|
Reusable bool `json:"reusable"`
|
|
Ephemeral bool `json:"ephemeral"`
|
|
Preauthorized bool `json:"preauthorized"`
|
|
Tags []string `json:"tags,omitempty"`
|
|
}
|
|
|
|
// Keys returns the list of keys for the current user.
|
|
func (c *Client) Keys(ctx context.Context) ([]string, error) {
|
|
path := c.BuildTailnetURL("keys")
|
|
req, err := http.NewRequestWithContext(ctx, "GET", path, nil)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
|
|
b, resp, err := c.sendRequest(req)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
if resp.StatusCode != http.StatusOK {
|
|
return nil, HandleErrorResponse(b, resp)
|
|
}
|
|
|
|
var keys struct {
|
|
Keys []*Key `json:"keys"`
|
|
}
|
|
if err := json.Unmarshal(b, &keys); err != nil {
|
|
return nil, err
|
|
}
|
|
ret := make([]string, 0, len(keys.Keys))
|
|
for _, k := range keys.Keys {
|
|
ret = append(ret, k.ID)
|
|
}
|
|
return ret, nil
|
|
}
|
|
|
|
// CreateKey creates a new key for the current user. Currently, only auth keys
|
|
// can be created. It returns the secret key itself, which cannot be retrieved again
|
|
// later, and the key metadata.
|
|
//
|
|
// To create a key with a specific expiry, use CreateKeyWithExpiry.
|
|
func (c *Client) CreateKey(ctx context.Context, caps KeyCapabilities) (keySecret string, keyMeta *Key, _ error) {
|
|
return c.CreateKeyWithExpiry(ctx, caps, 0)
|
|
}
|
|
|
|
// CreateKeyWithExpiry is like CreateKey, but allows specifying a expiration time.
|
|
//
|
|
// The time is truncated to a whole number of seconds. If zero, that means no expiration.
|
|
func (c *Client) CreateKeyWithExpiry(ctx context.Context, caps KeyCapabilities, expiry time.Duration) (keySecret string, keyMeta *Key, _ error) {
|
|
|
|
// convert expirySeconds to an int64 (seconds)
|
|
expirySeconds := int64(expiry.Seconds())
|
|
if expirySeconds < 0 {
|
|
return "", nil, fmt.Errorf("expiry must be positive")
|
|
}
|
|
if expirySeconds == 0 && expiry != 0 {
|
|
return "", nil, fmt.Errorf("non-zero expiry must be at least one second")
|
|
}
|
|
|
|
keyRequest := struct {
|
|
Capabilities KeyCapabilities `json:"capabilities"`
|
|
ExpirySeconds int64 `json:"expirySeconds,omitempty"`
|
|
}{caps, int64(expirySeconds)}
|
|
bs, err := json.Marshal(keyRequest)
|
|
if err != nil {
|
|
return "", nil, err
|
|
}
|
|
|
|
path := c.BuildTailnetURL("keys")
|
|
req, err := http.NewRequestWithContext(ctx, "POST", path, bytes.NewReader(bs))
|
|
if err != nil {
|
|
return "", nil, err
|
|
}
|
|
|
|
b, resp, err := c.sendRequest(req)
|
|
if err != nil {
|
|
return "", nil, err
|
|
}
|
|
if resp.StatusCode != http.StatusOK {
|
|
return "", nil, HandleErrorResponse(b, resp)
|
|
}
|
|
|
|
var key struct {
|
|
Key
|
|
Secret string `json:"key"`
|
|
}
|
|
if err := json.Unmarshal(b, &key); err != nil {
|
|
return "", nil, err
|
|
}
|
|
return key.Secret, &key.Key, nil
|
|
}
|
|
|
|
// Key returns the metadata for the given key ID. Currently, capabilities are
|
|
// only returned for auth keys, API keys only return general metadata.
|
|
func (c *Client) Key(ctx context.Context, id string) (*Key, error) {
|
|
path := c.BuildTailnetURL("keys", id)
|
|
req, err := http.NewRequestWithContext(ctx, "GET", path, nil)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
|
|
b, resp, err := c.sendRequest(req)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
if resp.StatusCode != http.StatusOK {
|
|
return nil, HandleErrorResponse(b, resp)
|
|
}
|
|
|
|
var key Key
|
|
if err := json.Unmarshal(b, &key); err != nil {
|
|
return nil, err
|
|
}
|
|
return &key, nil
|
|
}
|
|
|
|
// DeleteKey deletes the key with the given ID.
|
|
func (c *Client) DeleteKey(ctx context.Context, id string) error {
|
|
path := c.BuildTailnetURL("keys", id)
|
|
req, err := http.NewRequestWithContext(ctx, "DELETE", path, nil)
|
|
if err != nil {
|
|
return err
|
|
}
|
|
|
|
b, resp, err := c.sendRequest(req)
|
|
if err != nil {
|
|
return err
|
|
}
|
|
if resp.StatusCode != http.StatusOK {
|
|
return HandleErrorResponse(b, resp)
|
|
}
|
|
return nil
|
|
}
|