mirror of
https://github.com/tailscale/tailscale.git
synced 2026-02-09 17:52:57 +01:00
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>
83 lines
2.5 KiB
Go
83 lines
2.5 KiB
Go
// Copyright (c) Tailscale Inc & contributors
|
|
// SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
// Package neterror classifies network errors.
|
|
package neterror
|
|
|
|
import (
|
|
"errors"
|
|
"fmt"
|
|
"runtime"
|
|
"syscall"
|
|
)
|
|
|
|
var errEPERM error = syscall.EPERM // box it into interface just once
|
|
|
|
// TreatAsLostUDP reports whether err is an error from a UDP send
|
|
// operation that should be treated as a UDP packet that just got
|
|
// lost.
|
|
//
|
|
// Notably, on Linux this reports true for EPERM errors (from outbound
|
|
// firewall blocks) which aren't really send errors; they're just
|
|
// sends that are never going to make it because the local OS blocked
|
|
// it.
|
|
func TreatAsLostUDP(err error) bool {
|
|
if err == nil {
|
|
return false
|
|
}
|
|
switch runtime.GOOS {
|
|
case "linux":
|
|
// Linux, while not documented in the man page,
|
|
// returns EPERM when there's an OUTPUT rule with -j
|
|
// DROP or -j REJECT. We use this very specific
|
|
// Linux+EPERM check rather than something super broad
|
|
// like net.Error.Temporary which could be anything.
|
|
//
|
|
// For now we only do this on Linux, as such outgoing
|
|
// firewall violations mapping to syscall errors
|
|
// hasn't yet been observed on other OSes.
|
|
return errors.Is(err, errEPERM)
|
|
}
|
|
return false
|
|
}
|
|
|
|
var packetWasTruncated func(error) bool // non-nil on Windows at least
|
|
|
|
// PacketWasTruncated reports whether err indicates truncation but the RecvFrom
|
|
// that generated err was otherwise successful. On Windows, Go's UDP RecvFrom
|
|
// calls WSARecvFrom which returns the WSAEMSGSIZE error code when the received
|
|
// datagram is larger than the provided buffer. When that happens, both a valid
|
|
// size and an error are returned (as per the partial fix for golang/go#14074).
|
|
// If the WSAEMSGSIZE error is returned, then we ignore the error to get
|
|
// semantics similar to the POSIX operating systems. One caveat is that it
|
|
// appears that the source address is not returned when WSAEMSGSIZE occurs, but
|
|
// we do not currently look at the source address.
|
|
func PacketWasTruncated(err error) bool {
|
|
if packetWasTruncated == nil {
|
|
return false
|
|
}
|
|
return packetWasTruncated(err)
|
|
}
|
|
|
|
var shouldDisableUDPGSO func(error) bool // non-nil on Linux
|
|
|
|
func ShouldDisableUDPGSO(err error) bool {
|
|
if shouldDisableUDPGSO == nil {
|
|
return false
|
|
}
|
|
return shouldDisableUDPGSO(err)
|
|
}
|
|
|
|
type ErrUDPGSODisabled struct {
|
|
OnLaddr string
|
|
RetryErr error
|
|
}
|
|
|
|
func (e ErrUDPGSODisabled) Error() string {
|
|
return fmt.Sprintf("disabled UDP GSO on %s, NIC(s) may not support checksum offload", e.OnLaddr)
|
|
}
|
|
|
|
func (e ErrUDPGSODisabled) Unwrap() error {
|
|
return e.RetryErr
|
|
}
|