-
Notifications
You must be signed in to change notification settings - Fork 81
Fix Pkcs11::new bug preventing PKCS#11 library loading and bump rust-version and update deps #289
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
base: main
Are you sure you want to change the base?
Changes from all commits
bc4f0b5
2aa4505
fa1e79b
7db90c9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,17 +13,16 @@ documentation = "https://docs.rs/crate/cryptoki" | |
rust-version = "1.77" | ||
|
||
[dependencies] | ||
bitflags = "1.3" | ||
libloading = "0.8.6" | ||
log = "0.4.14" | ||
bitflags = "2.9.1" | ||
libloading = "0.8.8" | ||
log = "0.4.27" | ||
cryptoki-sys = { path = "../cryptoki-sys", version = "0.4.0" } | ||
paste = "1.0.6" | ||
paste = "1.0.15" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. for paste we have separate issue #279 where it is considered unmaintained (or feature complete -- depending on the point of view) and @hug-dev had a proposal to remove the dependency . Given that it is used only in one place and audit will show the issues with that, I would rather go with removing it than updating. @hug-dev can you open a PR with the proposed change in there to remove it? |
||
secrecy = "0.10.3" | ||
|
||
[dev-dependencies] | ||
num-traits = "0.2.14" | ||
hex = "0.4.3" | ||
serial_test = "0.5.1" | ||
serial_test = "3.2.0" | ||
testresult = "0.4.1" | ||
|
||
[features] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not related with your PR and you don't need to change anything here but this made me thinking that we could add a dependabot check in some nightly CI which could check that we use the latest dependencies, and update if not!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. It took me quite a while to locate the actual change, even though I've seen it earlier 😅
Maybe it's best to split this into several smaller PRs and keep this one only about the fix? 🤔
(Sorry for putting you for even more work 🙇 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mematthias made a good job of splitting between different commit and there seems to be one just to address the bug, would that be enough 🕵️?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That first commit is still kind-of packed: 860d945 and it includes stuff such as raising MRSV to 1.77 that has been done in another PR...
I just itches me to restructure these commits differently but... maybe it's just my OCD 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be just rebased (instead of doing the merge commits on the way.