Skip to content

Conversation

@maciej-lech
Copy link

This PR implements the feature discussed in #2473.

It introduces a new --trust CLI flag and a corresponding remote.trust configuration option in taskrc. These options are available when the Remote Taskfiles experiment is enabled.

The --trust flag can be specified multiple times to define trusted hosts (optionally including ports). Any remote Taskfiles fetched from these trusted hosts will not prompt for confirmation on their initial download or when their checksums change.

Closes #2473

Signed-off-by: Maciej Lech <maciej.lech@mlit.pro>
@curtbushko
Copy link

Looking forward to this feature!

// Extract host from server URL for trust testing
parsedURL, err := url.Parse(srv.URL)
require.NoError(t, err)
trustedHost := parsedURL.Host
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't I trust URLs? I trust github.com/myself but I don't trust github.com/shady.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about that, but using URLs requires more assumptions how to compare provided URL with the trust config.

  1. Exact match, so full URL comparison. In my case it would require configuring every single remote taskfiles (more than dozen now) which is not a big deal, but may not be a best DX.
  2. Prefix match. A problem: I want to trust https://github.com/myself but not https://github.com/myselfHackedByShady - which could be easily solved by setting https://github.com/myself/ and not https://github.com/myself. So maybe this is the best way.
  3. Glob-like style: https://github.com/myself/* or extended version https://github.com/myself/**/*
  4. Regex: https:\/\/github\.com\/myself\/.*

@vmaerten vmaerten self-requested a review November 29, 2025 10:05
Copy link
Member

@vmaerten vmaerten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR!
I would prefer using trusted-hosts instead of trust (both in the CLI and in the config file).

@maciej-lech
Copy link
Author

maciej-lech commented Dec 2, 2025

Thanks for your PR! I would prefer using trusted-hosts instead of trust (both in the CLI and in the config file).

Thank you for your feedback. Yes, I stumbled across PIP when I was searching for similar implementations. Although, --trusted-hosts in PIP is more like per-domain --insecure, I fully agree it is more explicit. Comma-separated imho is also fine. Let me update this PR

@maciej-lech maciej-lech requested a review from vmaerten December 2, 2025 09:37
Comment on lines 157 to 244
pflag.StringVar(&TrustedHosts, "trusted-hosts", strings.Join(config.Remote.TrustedHosts, ","), "Comma-separated list of trusted hosts for remote Taskfiles.")
pflag.DurationVar(&Timeout, "timeout", getConfig(config, func() *time.Duration { return config.Remote.Timeout }, time.Second*10), "Timeout for downloading remote Taskfiles.")
pflag.BoolVar(&ClearCache, "clear-cache", false, "Clear the remote cache.")
pflag.DurationVar(&CacheExpiryDuration, "expiry", getConfig(config, func() *time.Duration { return config.Remote.CacheExpiry }, 0), "Expiry duration for cached remote Taskfiles.")
}
pflag.Parse()
}

func Validate() error {
if Download && Offline {
return errors.New("task: You can't set both --download and --offline flags")
}

if Download && ClearCache {
return errors.New("task: You can't set both --download and --clear-cache flags")
}

if Global && Dir != "" {
return errors.New("task: You can't set both --global and --dir")
}

if Output.Name != "group" {
if Output.Group.Begin != "" {
return errors.New("task: You can't set --output-group-begin without --output=group")
}
if Output.Group.End != "" {
return errors.New("task: You can't set --output-group-end without --output=group")
}
if Output.Group.ErrorOnly {
return errors.New("task: You can't set --output-group-error-only without --output=group")
}
}

if List && ListAll {
return errors.New("task: cannot use --list and --list-all at the same time")
}

if ListJson && !List && !ListAll {
return errors.New("task: --json only applies to --list or --list-all")
}

if NoStatus && !ListJson {
return errors.New("task: --no-status only applies to --json with --list or --list-all")
}

if Nested && !ListJson {
return errors.New("task: --nested only applies to --json with --list or --list-all")
}

return nil
}

// WithFlags is a special internal functional option that is used to pass flags
// from the CLI into any constructor that accepts functional options.
func WithFlags() task.ExecutorOption {
return &flagsOption{}
}

type flagsOption struct{}

func (o *flagsOption) ApplyToExecutor(e *task.Executor) {
// Set the sorter
var sorter sort.Sorter
switch TaskSort {
case "none":
sorter = sort.NoSort
case "alphanumeric":
sorter = sort.AlphaNumeric
}

// Change the directory to the user's home directory if the global flag is set
dir := Dir
if Global {
home, err := os.UserHomeDir()
if err == nil {
dir = home
}
}

// Parse comma-separated trusted hosts
var trustedHosts []string
if TrustedHosts != "" {
for host := range strings.SplitSeq(TrustedHosts, ",") {
if trimmed := strings.TrimSpace(host); trimmed != "" {
trustedHosts = append(trustedHosts, trimmed)
}
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do not need this, pflag already support it with StringSliceVar cf: https://pkg.go.dev/github.com/spf13/pflag#StringSliceVar

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, we can simplify and use StringSliceVar. This way we support either --trusted-hosts="a.com,b.com" either --trusted-hosts="a.com" --trusted-hosts="b.com"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remote Taskfiles: add a new trust mechanism

4 participants