Konge

Obviously, It's hotlink protectction, AMD check if user download from AMD website directly, preventing bad website refer to the download link without download permission. I think it better to add...

no response

I think the issue is still valuable because of the kerberos protocol [requirement](https://datatracker.ietf.org/doc/html/rfc4120#appendix-A). The remarkable thing is that it needs the `APPLICATION` as toplevel attribute, not field level.

yes

it's because edition 2018 will not do it automatically, but 2021 include TryInto in the std prelude. and it is the spiffe crate problem, not my code :( as the...

spire has already use its own `Model` type. The auto migrate in gorm v1 doesn't modify the field type, so I think maybe changing the field type `uint` -> `uint64`...

See https://github.com/parallaxsecond/rust-cryptoki/pull/226 This is trickier than expected. With the added mutability, the entire `Mechanism` structure becomes *non-copyable/cloneable*. We might need to either redesign the `Mechanism` abstraction or add a `try_clone`...

Actually in the commit https://github.com/parallaxsecond/rust-cryptoki/commit/43c8863750065224f56b29a3ab2a16b51272bdbe, I make all methods accept the "owned" `Mechanism`, instead of mutable `Mechanism` ref. In that case, users must create new `Mechanism` each time, and move...

Although the trait constraint for `Mechanism` is enough for the alias rule: ``` Mechanism: !Clone+!Send ``` I open another branch https://github.com/parallaxsecond/rust-cryptoki/commit/43c8863750065224f56b29a3ab2a16b51272bdbe that make all operations use the owned `Mechanism`. It's...