https://github.com/syncom/x509-certificate-rs-clone

A clone of rust crate x509-certificate, for customization
https://github.com/syncom/x509-certificate-rs-clone

Last synced: 4 days ago
JSON representation

A clone of rust crate x509-certificate, for customization

• Host: GitHub
• URL: https://github.com/syncom/x509-certificate-rs-clone
• Owner: syncom
• License: mpl-2.0
• Created: 2022-11-18T01:16:14.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2024-03-07T06:53:32.000Z (8 months ago)
• Last Synced: 2024-03-07T07:49:24.837Z (8 months ago)
• Language: Rust
• Size: 61.5 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.rst
  • License: LICENSE

Awesome Lists containing this project

README

        
# x509-certificate

`x509-certificate` is a library crate for interfacing with X.509 certificates.

It supports the following:

* Parsing certificates from BER, DER, and PEM.

* Serializing certificates to BER, DER, and PEM.

* Defining common algorithm identifiers.

* Generating new certificates.

* Verifying signatures on certificates.

* And more.

**This crate has not undergone a security audit. It does not

employ many protections for malformed data when parsing certificates.

Use at your own risk. See additional notes in `src/lib.rs`.**

`x509-certificate` is part of the

[PyOxidizer](https://github.com/indygreg/PyOxidizer.git) project and

this crate is developed in that repository.

## Developing

The root of the repository is a Cargo workspace and has a lot of members.

The dependency tree for the entire repo is massive and `cargo build` likely

will fail due to Python dependency weirdness.

For best results, `cd x509-certificate` and run commands there. Or

`cargo build -p x509-certificate`, `cargo test -p x509-certificate`, etc.

This crate is used throughout this repository. If you want to build/run

the workspace, try

`cargo build --workspace --exclude oxidized-importer --exclude pyembed`

to exclude the crates most often causing build troubles. The `pyoxidizer`

and `tugger` crates have an expensive test harness and dependency tree and

can also be excluded.

Generally, the following crates are sensitive to changes in this one:

* `cryptographic-message-syntax`

* `apple-codesign`

* `tugger-code-signing`

* `tugger-windows-codesign`

If build + tests pass on these crates, there's a good chance the entire

workspace is happy.