Dmitry Baryshkov

I took a glance a the GOST certificate which is used in the signature on my Ham license. It has: ``` Key Usage (critical): Digital signature. Non repudiation. Key encipherment....

Some justification. GOST is one of 'national' PK schemes. The corresponding X.509 parts are described in [RFC 4491](https://www.rfc-editor.org/rfc/rfc4491.html) and [RFC 9215](https://www.rfc-editor.org/rfc/rfc9215.html). Certificates can be used for both digital signatures, key...

That note talks about the nonRepudiation bit. However I'm more concerned about mixing of other usage bits. For example RFC 3279 section 2.3.5 (also see errata [6672](https://www.rfc-editor.org/errata/eid6672)). It explicitly allows...

Forr the reference, [RFC 4055](https://datatracker.ietf.org/doc/html/rfc4055) allows keyEncipherment and dataEncipherment, but explicitly tellls that those two bits SHOULD NOT be used together.

@dayday2019 a very limited implementation. Hope it can be helpful. License: Apache-2 + MIT Note: it doesn't perform path validation, etc. Just signature checks. ```Rust pub fn verify_signature( cert: &Certificate,...

@tarcieri the major issue with the `StrSlice` that I faced while trying to implement `TeletexString` in a more correct way (handling `byte >= 0x80` as if it was the win-1252),...

Being a minor party here, I'm fine with either approach as long as StrSlice doesn't become the public API.

Can it be replaced with the trait to provide the calling interface?

As a second thought, let's maybe rename `StrSlice` to `AbstractString` and use `Deref` as you suggested? In the end, it might be possible to extend it later to suppor custom...

`AsRef` would stay as is. It's the `AsRef::as_ref(&self)`, who would require it to be changed.