文件列表:

CODE-OF-CONDUCT.md (4734, 2022-11-30)
CONTRIBUTING.md (5947, 2022-11-30)
Dockerfile (312, 2022-11-30)
LICENSE (11357, 2022-11-30)
Makefile (532, 2022-11-30)
cmd/ (0, 2022-11-30)
cmd/main.go (1506, 2022-11-30)
configs/ (0, 2022-11-30)
configs/cfssl_config.json (877, 2022-11-30)
configs/config.toml (2676, 2022-11-30)
go.mod (15228, 2022-11-30)
go.sum (261242, 2022-11-30)
internal/ (0, 2022-11-30)
internal/api/ (0, 2022-11-30)
internal/api/api.go (117, 2022-11-30)
internal/api/certificate.api.go (740, 2022-11-30)
internal/api/ocsp.api.go (394, 2022-11-30)
internal/api/tls.api.go (1230, 2022-11-30)
internal/app.go (3993, 2022-11-30)
internal/config/ (0, 2022-11-30)
internal/config/config.go (5531, 2022-11-30)
internal/dao/ (0, 2022-11-30)
internal/dao/certificate/ (0, 2022-11-30)
internal/dao/certificate/certificate.entity.go (1117, 2022-11-30)
internal/dao/certificate/certificate.repo.go (1571, 2022-11-30)
internal/dao/dao.go (294, 2022-11-30)
internal/ginx/ (0, 2022-11-30)
internal/ginx/ginx.go (3651, 2022-11-30)
internal/initx/ (0, 2022-11-30)
internal/initx/cache.go (218, 2022-11-30)
internal/initx/cfssl.go (1595, 2022-11-30)
internal/initx/crftkv.go (784, 2022-11-30)
internal/initx/logger.go (1593, 2022-11-30)
internal/initx/storage.go (756, 2022-11-30)
internal/injector.go (236, 2022-11-30)
internal/middleware/ (0, 2022-11-30)
internal/middleware/middleware.go (1745, 2022-11-30)
... ...

# DeCA DeCA is a decentralized PKI framework compatible with X.509 DeCA can perform all the key functions of X.509 PKI standard, namely, registering, confirming, revoking and verifying TLS certificates. DeCA is compatible with the existing PKI standard, namely X.509 It stores, issues and verifies the certificate content in X.509 format instead of creating its custom implementation. # Background The security of PKI largely depends on the reliability of these third-party CAs, which is a single point of failure for PKI. There have been many popular CA violations in the past, among which the centralized operation mode of CA was triggered by the spread of rogue certificates. Our goal is to completely decentralize the CA pool, and at the same time build our decentralized solution and the established PKI standard (i.e. X.509) to achieve effective real-world integration. # System architecture DeCA proposed a decentralized PKI framework named DeCA by using IPFS and FVM technology,This framework provides data synchronization, hidden synchronization strategy and low-latency synchronization of basic data among decentralized CA groups. The certificate is stored in decentralize storage by using the characteristics of IPFS and FVM, and cannot be tampered with, thus effectively preventing the third party from attacking.  # Get Start ``` $ go get github.com/FlowShield/deca $ make $ bin/ca tls -c configs/config.toml ``` ### SDK Installation ``` $ go get github.com/FlowShield/deca ``` The classic usage of CA SDK is that the client and the server use the certificate issued by CA Center for encrypted communication. The following is the usage of sdk between client and server. See：[Demo](https://github.com/FlowShield/casdk/tree/main/examples)

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：