Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sanketshevkar/gsoc-submission
https://github.com/sanketshevkar/gsoc-submission
Last synced: 28 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/sanketshevkar/gsoc-submission
- Owner: sanketshevkar
- Created: 2021-08-23T08:27:55.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-08-23T09:56:33.000Z (over 3 years ago)
- Last Synced: 2024-11-07T08:51:00.277Z (3 months ago)
- Size: 10.7 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Signing Templates and Signing Contracts GSoC 2021
- Student: [Sanket Shevkar](https://github.com/sanketshevkar)
- Mentor: [Martin Halford](https://github.com/martinhalford)
- Organisation: [Accord Project](https://github.com/accordproject)
# Template Signing
### Purpose:
The developer/author should be able to digitally sign the template that the developer has developed. Dicussion about this can be found [here](https://github.com/accordproject/cicero/issues/262).
- Pull Request [#688](https://github.com/accordproject/cicero/pull/688)
- Status: Merged
- Closes [#671](https://github.com/accordproject/cicero/issues/671)
### Prerequisites
Create a PEM file containing the the private key and the certificate of the developer,
following should be the format of the PEM file:
```
-----BEGIN RSA PRIVATE KEY-----
(Private Key: domain_name.key contents)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(Primary SSL certificate: domain_name.crt contents)
-----END CERTIFICATE-----
```
Create a pkcs#12 file:
`openssl pkcs12 -export -in server.pem -out keystore.pkcs12`
### Usage
```
cicero archive --template [template path] --output [output archive path] --keystore [pkcs#12 keystore path] --passphrase [password of the keystore]
cicero verify --template [template path]
```
# Contract Signing
### Purpose:
The parties involved in execution of a certain contract should be able to digitally sign the contract to validate it model, logic, data/text. Dicussion about this can be found [here](https://github.com/accordproject/cicero/issues/558).
- Pull Request [#689](https://github.com/accordproject/cicero/pull/689)
- Status: Open
- This a part of a much larger new feature that is being built i.e. Contract Instances.
More information can be found [here](https://github.com/accordproject/lab-contract-design).
### Prerequisites
Create a PEM file containing the the private key and the certificate of the party,
following should be the format of the PEM file:
```
-----BEGIN RSA PRIVATE KEY-----
(Private Key: domain_name.key contents)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(Primary SSL certificate: domain_name.crt contents)
-----END CERTIFICATE-----
```
Create a pkcs#12 file:
`openssl pkcs12 -export -in server.pem -out keystore.pkcs12`
### Usage
```
cicero sign --contract [contract path] --output [output archive path] --keystore [pkcs#12 keystore path] --passphrase [password of the keystore] --signatory [name of the signatory]
cicero verify --contract [contract path]
```