Clarify the Operations warning in all seven locales. For the current sealed-data format, workers receive derived keys needed for that private job's data. Legacy SISYENC1 inputs retain compatibility behavior and may require the full private.key to be shared with that worker, so the copy explicitly warns about this exception and advises using trusted workers.
Validation: all seven locale JSON files parse, each warning retains the private.key loss consequence, and git diff --check passes.
CI passed on head 0ebf841, including desktop typecheck/tests/build, Go race tests, statement coverage, daemon build and pool rehearsal. Packaging tests passed on Linux, macOS and Windows.
Refs #117 and follows the review note on #184.
Clarify the Operations warning in all seven locales. For the current sealed-data format, workers receive derived keys needed for that private job's data. Legacy SISYENC1 inputs retain compatibility behavior and may require the full `private.key` to be shared with that worker, so the copy explicitly warns about this exception and advises using trusted workers.
Validation: all seven locale JSON files parse, each warning retains the private.key loss consequence, and `git diff --check` passes.
CI passed on head `0ebf841`, including desktop typecheck/tests/build, Go race tests, statement coverage, daemon build and pool rehearsal. Packaging tests passed on Linux, macOS and Windows.
Checked against the code and it is right: for a blob sealed in the old format the coordinator hands the worker the whole key (keysFor in coordinator/coordinator.go, the whole case), and for everything else only keys derived for that job's data. All seven locales carry the change and nothing else is touched. Merging. Thanks for catching that my note on #184 over-promised.
Checked against the code and it is right: for a blob sealed in the old format the coordinator hands the worker the whole key (`keysFor` in `coordinator/coordinator.go`, the `whole` case), and for everything else only keys derived for that job's data. All seven locales carry the change and nothing else is touched. Merging. Thanks for catching that my note on #184 over-promised.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Refs #117 and follows the review note on #184.
Clarify the Operations warning in all seven locales. For the current sealed-data format, workers receive derived keys needed for that private job's data. Legacy SISYENC1 inputs retain compatibility behavior and may require the full
private.keyto be shared with that worker, so the copy explicitly warns about this exception and advises using trusted workers.Validation: all seven locale JSON files parse, each warning retains the private.key loss consequence, and
git diff --checkpasses.CI passed on head
0ebf841, including desktop typecheck/tests/build, Go race tests, statement coverage, daemon build and pool rehearsal. Packaging tests passed on Linux, macOS and Windows.Checked against the code and it is right: for a blob sealed in the old format the coordinator hands the worker the whole key (
keysForincoordinator/coordinator.go, thewholecase), and for everything else only keys derived for that job's data. All seven locales carry the change and nothing else is touched. Merging. Thanks for catching that my note on #184 over-promised.