tailscale/tstest/integration/vms/top_level_test.go
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

115 lines
4.3 KiB
Go

// Copyright (c) Tailscale Inc & contributors
// SPDX-License-Identifier: BSD-3-Clause
//go:build !windows && !plan9
package vms
import (
"context"
"testing"
"time"
"github.com/pkg/sftp"
expect "github.com/tailscale/goexpect"
)
func TestRunUbuntu2404(t *testing.T) {
testOneDistribution(t, 0, Distros[0])
}
func TestRunNixos2505(t *testing.T) {
t.Parallel()
testOneDistribution(t, 1, Distros[1])
}
// TestMITMProxy is a smoke test for derphttp through a MITM proxy.
// Encountering such proxies is unfortunately commonplace in more
// traditional enterprise networks.
//
// We invoke tailscale netcheck because the networking check is done
// by tailscale rather than tailscaled, making it easier to configure
// the proxy.
//
// To provide the actual MITM server, we use squid.
func TestMITMProxy(t *testing.T) {
t.Parallel()
setupTests(t)
distro := Distros[1] // nixos-25.05
ctx, done := context.WithCancel(context.Background())
t.Cleanup(done)
h := newHarness(t)
err := ramsem.sem.Acquire(ctx, int64(distro.MemoryMegs))
if err != nil {
t.Fatalf("can't acquire ram semaphore: %v", err)
}
t.Cleanup(func() { ramsem.sem.Release(int64(distro.MemoryMegs)) })
vm := h.mkVM(t, 2, distro, h.pubKey, h.loginServerURL, t.TempDir())
vm.waitStartup(t)
ipm := h.waitForIPMap(t, vm, distro)
_, cli := h.setupSSHShell(t, distro, ipm)
sftpCli, err := sftp.NewClient(cli)
if err != nil {
t.Fatalf("can't connect over sftp to copy binaries: %v", err)
}
defer sftpCli.Close()
// Initialize a squid installation.
//
// A few things of note here:
// - The first thing we do is append the nsslcrtd_program stanza to the config.
// This must be an absolute path and is based on the nix path of the squid derivation,
// so we compute and write it out here.
// - Squid expects a pre-initialized directory layout, so we create that in /tmp/squid then
// invoke squid with -z to have it fill in the rest.
// - Doing a meddler-in-the-middle attack requires using some fake keys, so we create
// them using openssl and then use the security_file_certgen tool to setup squids' ssl_db.
// - There were some perms issues, so i yeeted 0777. Its only a test anyway
copyFile(t, sftpCli, "squid.conf", "/tmp/squid.conf")
runTestCommands(t, 30*time.Second, cli, []expect.Batcher{
&expect.BSnd{S: "echo -e \"\\nsslcrtd_program $(nix eval --raw nixpkgs.squid)/libexec/security_file_certgen -s /tmp/squid/ssl_db -M 4MB\\n\" >> /tmp/squid.conf\n"},
&expect.BSnd{S: "mkdir -p /tmp/squid/{cache,core}\n"},
&expect.BSnd{S: "openssl req -batch -new -newkey rsa:4096 -sha256 -days 3650 -nodes -x509 -keyout /tmp/squid/myca-mitm.pem -out /tmp/squid/myca-mitm.pem\n"},
&expect.BExp{R: `writing new private key to '/tmp/squid/myca-mitm.pem'`},
&expect.BSnd{S: "$(nix eval --raw nixpkgs.squid)/libexec/security_file_certgen -c -s /tmp/squid/ssl_db -M 4MB\n"},
&expect.BExp{R: `Done`},
&expect.BSnd{S: "sudo chmod -R 0777 /tmp/squid\n"},
&expect.BSnd{S: "squid --foreground -YCs -z -f /tmp/squid.conf\n"},
&expect.BSnd{S: "echo Success.\n"},
&expect.BExp{R: `Success.`},
})
// Start the squid server.
runTestCommands(t, 10*time.Second, cli, []expect.Batcher{
&expect.BSnd{S: "daemonize -v -c /tmp/squid $(nix eval --raw nixpkgs.squid)/bin/squid --foreground -YCs -f /tmp/squid.conf\n"}, // start daemon
// NOTE(tom): Writing to /dev/tcp/* is bash magic, not a file. This
// eldritchian incantation lets us wait till squid is up.
&expect.BSnd{S: "while ! timeout 5 bash -c 'echo > /dev/tcp/localhost/3128'; do sleep 1; done\n"},
&expect.BSnd{S: "echo Success.\n"},
&expect.BExp{R: `Success.`},
})
// Uncomment to help debugging this test if it fails.
//
// runTestCommands(t, 30 * time.Second, cli, []expect.Batcher{
// &expect.BSnd{S: "sudo ifconfig\n"},
// &expect.BSnd{S: "sudo ip link\n"},
// &expect.BSnd{S: "sudo ip route\n"},
// &expect.BSnd{S: "ps -aux\n"},
// &expect.BSnd{S: "netstat -a\n"},
// &expect.BSnd{S: "cat /tmp/squid/access.log && cat /tmp/squid/cache.log && cat /tmp/squid.conf && echo Success.\n"},
// &expect.BExp{R: `Success.`},
// })
runTestCommands(t, 30*time.Second, cli, []expect.Batcher{
&expect.BSnd{S: "SSL_CERT_FILE=/tmp/squid/myca-mitm.pem HTTPS_PROXY=http://127.0.0.1:3128 tailscale netcheck\n"},
&expect.BExp{R: `IPv4: yes`},
})
}