Closed chris-wood closed 1 year ago
Thanks @chris-wood !
For your convenience:
Running [/home/runner/golangci-lint-1.51.2-linux-amd64/golangci-lint run --out-format=github-actions --config=./.etc/golangci.yml ./...] in [] ...
Error: File is not `gofmt`-ed with `-s` (gofmt)
Error: File is not `gofmt`-ed with `-s` (gofmt)
Error: File is not `gofmt`-ed with `-s` (gofmt)
Error: File is not `gofumpt`-ed (gofumpt)
Error: File is not `gofumpt`-ed (gofumpt)
Error: `(kemBase).labeledExtract` - `salt` always receives `nil` (unparam)
For your convenience:
Running [/home/runner/golangci-lint-1.51.2-linux-amd64/golangci-lint run --out-format=github-actions --config=./.etc/golangci.yml ./...] in [] ... Error: File is not `gofmt`-ed with `-s` (gofmt) Error: File is not `gofmt`-ed with `-s` (gofmt) Error: File is not `gofmt`-ed with `-s` (gofmt) Error: File is not `gofumpt`-ed (gofumpt) Error: File is not `gofumpt`-ed (gofumpt) Error: `(kemBase).labeledExtract` - `salt` always receives `nil` (unparam)
What incantation do I need to invoke to make these changes locally? Can we get that set up in a make
target?
What incantation do I need to invoke to make these changes locally? Can we get that set up in a
make
target?
make lint
What incantation do I need to invoke to make these changes locally? Can we get that set up in a
make
target?
make lint
This is sort of unhelpful in that it just runs the linter without actually applying changes. I'll send a PR to update the Makefile so that there's a target for actually doing the formatting.
@bwesterb I pushed some preliminary test vector generation code.
Marking as ready for review now. I updated when keys are validated (only when we receive them over the wire through deserialization functions). Fail early and fail often!
If these secrets were true positive and are still valid, we highly recommend you to revoke them. Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately. Find here more information about risks.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
@armfazh @cjpatton Please check whether this makes sense to you.
@armfazh can you please re-review? I'd like to merge this and address KEM-specific validation steps in a separate PR, if possible.
@armfazh squashed and ready to go!
Cool 😎
See the draft. Some tasks still left to do: