Will Norris 3ec5be3f51 all: remove AUTHORS file and references to it
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>
2026-01-23 15:49:45 -08:00

78 lines
2.5 KiB
Go

// Copyright (c) Tailscale Inc & contributors
// SPDX-License-Identifier: BSD-3-Clause
// TODO: docs about all this
package main
import (
"errors"
"fmt"
"net"
"net/http"
"strings"
"tailscale.com/derp/derpserver"
"tailscale.com/net/connectproxy"
)
// serveConnect handles a CONNECT request for ACE support.
func serveConnect(s *derpserver.Server, w http.ResponseWriter, r *http.Request) {
if !*flagACEEnabled {
http.Error(w, "CONNECT not enabled", http.StatusForbidden)
return
}
if r.TLS == nil {
// This should already be enforced by the caller of serveConnect, but
// double check.
http.Error(w, "CONNECT requires TLS", http.StatusForbidden)
return
}
ch := &connectproxy.Handler{
Check: func(hostPort string) error {
host, port, err := net.SplitHostPort(hostPort)
if err != nil {
return err
}
if port != "443" && port != "80" {
// There are only two types of CONNECT requests the client makes
// via ACE: requests for /key (port 443) and requests to upgrade
// to the bidirectional ts2021 Noise protocol.
//
// The ts2021 layer can bootstrap over port 80 (http) or port
// 443 (https).
//
// Without ACE, we prefer port 80 to avoid unnecessary double
// encryption. But enough places require TLS+port 443 that we do
// support that double encryption path as a fallback.
//
// But ACE adds its own TLS layer (ACE is always CONNECT over
// https). If we don't permit port 80 here as a target, we'd
// have three layers of encryption (TLS + TLS + Noise) which is
// even more silly than two.
//
// So we permit port 80 such that we can only have two layers of
// encryption, varying by the request type:
//
// 1. TLS from client to ACE proxy (CONNECT)
// 2a. TLS from ACE proxy to https://controlplane.tailscale.com/key (port 443)
// 2b. ts2021 Noise from ACE proxy to http://controlplane.tailscale.com/ts2021 (port 80)
//
// But nothing's stopping the client from doing its ts2021
// upgrade over https anyway and having three layers of
// encryption. But we can at least permit the client to do a
// "CONNECT controlplane.tailscale.com:80 HTTP/1.1" if it wants.
return fmt.Errorf("only ports 443 and 80 are allowed")
}
// TODO(bradfitz): make policy configurable from flags and/or come
// from local tailscaled nodeAttrs
if !strings.HasSuffix(host, ".tailscale.com") || strings.Contains(host, "derp") {
return errors.New("bad host")
}
return nil
},
}
ch.ServeHTTP(w, r)
}