Bump zizmorcore/zizmor-action from 0.6.4 to 0.8.0 in the github-actions-dependencies group (#21)
Bumps the github-actions-dependencies group with 1 update: zizmorcore/zizmor-action.
Updates
zizmorcore/zizmor-actionfrom 0.6.4 to 0.8.0Release notes
Sourced from zizmorcore/zizmor-action's releases.
v0.8.0
The action now supports prereleases.
The default has not changed, but you can pass a prerelease version of zizmor or
version: prereleaseto get whatever latest prerelease the action knows about.What's Changed
- Support prereleases by
@woodruffwin zizmorcore/zizmor-action#182- Sync zizmor versions by
@github-actions[bot] in zizmorcore/zizmor-action#184Full Changelog: https://github.com/zizmorcore/zizmor-action/compare/v0.7.1...v0.8.0
v0.7.1
zizmor changes
Bug Fixes 🐛🔗
- Fixed a regression in 1.31.0 where some ignore comments/configurations would no longer apply to the dangerous-triggers audit
action changes
The default version of zizmor is now 1.31.1.
What's Changed
- Sync zizmor versions by
@github-actions[bot] in zizmorcore/zizmor-action#178Full Changelog: https://github.com/zizmorcore/zizmor-action/compare/v0.7.0...v0.7.1
v0.7.0
zizmor notes
Enhancements 🌱🔗
The typosquat-uses audit now supports pre-commit config inputs (#2437)
The self-hosted-runner audit is now significantly more precise (#2350)
Many thanks to
@ubiratansoaresfor proposing and implementing this enhancement!The dangerous-triggers audit now considers the issue_comment trigger fundamentally dangerous (#2396)
zizmor is now aware of the image_version workflow trigger (#2397)
The dangerous-triggers audit now produces more precise finding/diagnostic spans (#2402)
... (truncated)
Commits
53290baSync zizmor versions (#184)76da2eeSupport prereleases (#182)fb1d87bchore(deps): bump the github-actions group with 2 updates (#180)be36601README: bump pins (#179)85b2b9fSync zizmor versions (#178)38c745aREADME: bump pins (#177)f9597c8Sync zizmor versions (#175)2181e51Bump sync-zizmor-versions.py to Python 3.11 for locking (#174)27d989bchore(deps): bump the github-actions group with 2 updates (#173)a91218cBootstrap zizmor without Docker (#169)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency’s major version (unless you unignore this specific dependency’s major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency’s minor version (unless you unignore this specific dependency’s minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSigned-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
sunlight-secretmanager
sunlight-secretmanager is a command-line tool to manage a Sunlight CT Log’s private key material.
All CT logs have a private key which they use to create Signed Certificate Timestamps (SCTs) and Signed Tree Heads (STHs). Sunlight does not take this private key as input directly. Instead, its configuration requires two file paths:
The purpose of sunlight-secretmanager is to authenticate to AWS Secrets Manager, retrieve a stored seed, use that seed to derive the corresponding pubkey, and write both files to disk in a tmpfs. It knows what seed to retrieve and where to write the output files by parsing the same config file which configures the Sunlight log itself.
If it successfully retrieves a secret from AWS Secrets Manager but that secret is empty, it will generate a new seed and save it back to AWS before proceeding. This allows for seamless setup of new log shards simply by adding them to Terraform.
Usage
Sign in the AWS SDK so it populates your environment with the appropriate values, and then: