Bugzilla

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #6)
> OK, this is up to the point of
> ```
> 2019/10/25 00:29:28 UTC Invalid config: Config setting "ed25519SigningKeyLocation" has not been defined
> ```
> I'm not sure how ot fix that without providing a signing key?

See the config from comment 7. For win2012r2 the key is generated [here](https://github.com/taskcluster/generic-worker/blob/278fbc5a853010611d7fd186abb1229fde8b1fd9/worker_types/win2012r2/bootstrap.ps1#L156-L157).

Note, we don't currently publish the ed25519 public key anywhere, but if we did, it would enable people to verify the authenticity of task artifacts. As far as I am aware, only gecko level 3 build tasks currently sign their artifacts, but the feature is available to all workers, so that any task can potentially sign its artifacts so that their authenticity can be verified downstream.

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #6)
> OK, this is up to the point of
> ```
> 2019/10/25 00:29:28 UTC Invalid config: Config setting "ed25519SigningKeyLocation" has not been defined
> ```
> I'm not sure how ot fix that without providing a signing key?

See the [config from comment 7](https://github.com/taskcluster/community-history/blob/1fd642871fdc30612d78792c4b653c55188f7edb/WorkerPools/proj-taskcluster%E2%81%84win2012r2#L38). For win2012r2 the key is generated [here](https://github.com/taskcluster/generic-worker/blob/278fbc5a853010611d7fd186abb1229fde8b1fd9/worker_types/win2012r2/bootstrap.ps1#L156-L157).

Note, we don't currently publish the ed25519 public key anywhere, but if we did, it would enable people to verify the authenticity of task artifacts. As far as I am aware, only gecko level 3 build tasks currently sign their artifacts, but the feature is available to all workers, so that any task can potentially sign its artifacts so that their authenticity can be verified downstream.