Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.16: ci: add cargo deny check advisories (backport of #216) #217

Merged
merged 1 commit into from
Oct 23, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,11 @@ jobs:
- name: cargo fmt
run: cargo fmt --all -- --check

- name: cargo deny check advisories
uses: EmbarkStudios/cargo-deny-action@v1
with:
command: check advisories

- name: cargo clippy
run: cargo clippy --workspace --all-targets --tests #-- --deny=warnings

Expand Down
32 changes: 32 additions & 0 deletions deny.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
all-features = true

[advisories]
ignore = [
# borsh 0.9.3
# Advisory: https://rustsec.org/advisories/RUSTSEC-2023-0033
# Affected versions of borsh cause undefined behavior when zero-sized-types (ZST)
# are parsed and the Copy/Clone traits are not implemented/derived.
# For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy
# (this can be achieved through a singleton), then accessing/writing to deserialized
# data will cause a segmentation fault.
# borsh 0.10.3
# Advisory: https://rustsec.org/advisories/RUSTSEC-2023-0033
# Affected versions of borsh cause undefined behavior when zero-sized-types (ZST)
# are parsed and the Copy/Clone traits are not implemented/derived.
# For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy
# (this can be achieved through a singleton), then accessing/writing to deserialized
# data will cause a segmentation fault.
"RUSTSEC-2023-0033",

# ed25519-dalek 1.0.1
# Advisory: https://rustsec.org/advisories/RUSTSEC-2022-0093
# Versions of `ed25519-dalek` prior to v2.0 model private and public keys as
# separate types which can be assembled into a `Keypair`, and also provide APIs
# for serializing and deserializing 64-byte private/public keypairs.
"RUSTSEC-2022-0093",

# atty 0.2.14
# Advisory: https://rustsec.org/advisories/RUSTSEC-2021-0145
# On windows, `atty` dereferences a potentially unaligned pointer.
"RUSTSEC-2021-0145",
]