mirror of
https://github.com/tailscale/tailscale.git
synced 2026-02-11 10:41:43 +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>
80 lines
2.7 KiB
Go
80 lines
2.7 KiB
Go
// Copyright (c) Tailscale Inc & contributors
|
|
// SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
// Package gp contains [Group Policy]-related functions and types.
|
|
//
|
|
// [Group Policy]: https://web.archive.org/web/20240630210707/https://learn.microsoft.com/en-us/previous-versions/windows/desktop/policy/group-policy-start-page
|
|
package gp
|
|
|
|
import (
|
|
"fmt"
|
|
"runtime"
|
|
|
|
"golang.org/x/sys/windows"
|
|
)
|
|
|
|
// Scope is a user or machine policy scope.
|
|
type Scope int
|
|
|
|
const (
|
|
// MachinePolicy indicates a machine policy.
|
|
// Registry-based machine policies reside in HKEY_LOCAL_MACHINE.
|
|
MachinePolicy Scope = iota
|
|
// UserPolicy indicates a user policy.
|
|
// Registry-based user policies reside in HKEY_CURRENT_USER of the corresponding user.
|
|
UserPolicy
|
|
)
|
|
|
|
// _RP_FORCE causes RefreshPolicyEx to reapply policy even if no policy change was detected.
|
|
// See [RP_FORCE] for details.
|
|
//
|
|
// [RP_FORCE]: https://web.archive.org/save/https://learn.microsoft.com/en-us/windows/win32/api/userenv/nf-userenv-refreshpolicyex
|
|
const _RP_FORCE = 0x1
|
|
|
|
// RefreshUserPolicy triggers a machine policy refresh, but does not wait for it to complete.
|
|
// When the force parameter is true, it causes the Group Policy to reapply policy even
|
|
// if no policy change was detected.
|
|
func RefreshMachinePolicy(force bool) error {
|
|
return refreshPolicyEx(true, toRefreshPolicyFlags(force))
|
|
}
|
|
|
|
// RefreshUserPolicy triggers a user policy refresh, but does not wait for it to complete.
|
|
// When the force parameter is true, it causes the Group Policy to reapply policy even
|
|
// if no policy change was detected.
|
|
//
|
|
// The token indicates user whose policy should be refreshed.
|
|
// If specified, the token must be either a primary token with TOKEN_QUERY and TOKEN_DUPLICATE
|
|
// access, or an impersonation token with TOKEN_QUERY and TOKEN_IMPERSONATE access,
|
|
// and the specified user must be logged in interactively.
|
|
//
|
|
// Otherwise, a zero token value indicates the current user. It should not
|
|
// be used by services or other applications running under system identities.
|
|
//
|
|
// The function fails with windows.ERROR_ACCESS_DENIED if the user represented by the token
|
|
// is not logged in interactively at the time of the call.
|
|
func RefreshUserPolicy(token windows.Token, force bool) error {
|
|
if token != 0 {
|
|
// Impersonate the user whose policy we need to refresh.
|
|
runtime.LockOSThread()
|
|
defer runtime.UnlockOSThread()
|
|
if err := impersonateLoggedOnUser(token); err != nil {
|
|
return err
|
|
}
|
|
defer func() {
|
|
if err := windows.RevertToSelf(); err != nil {
|
|
// RevertToSelf errors are non-recoverable.
|
|
panic(fmt.Errorf("could not revert impersonation: %w", err))
|
|
}
|
|
}()
|
|
}
|
|
|
|
return refreshPolicyEx(true, toRefreshPolicyFlags(force))
|
|
}
|
|
|
|
func toRefreshPolicyFlags(force bool) uint32 {
|
|
if force {
|
|
return _RP_FORCE
|
|
}
|
|
return 0
|
|
}
|