Mithril v2304.0-prerelease
Pre-release
Pre-release
github-actions
released this
25 Jan 08:28
·
6101 commits
to main
since this release
What's Changed
- Mithril Network Update ADR by @ghubertpalo in #676
- Update PR template by @jpraynaud in #680
- Upgrade
devnet
to Cardano1.35.4
by @jpraynaud in #667 - Fix make build portable by @jpraynaud in #685
- Update build documentation by @jpraynaud in #682
- Update docs
current
version by @jpraynaud in #686 - Update dependencies by @jpraynaud in #683
- Fix
make
errors from root by @jpraynaud in #684 - Accelerate end to end test execution by @jpraynaud in #692
- 689 Signer Register Message by @ghubertpalo in #691
- Fix
make
errors from root v2 by @jpraynaud in #687 - [693] register signature message by @ghubertpalo in #694
- [695] add epoch settings message & adapter by @ghubertpalo in #700
- Add snapshot message and adapter by @jpraynaud in #702
- Add certificate message and adapter by @jpraynaud in #701
- [705] Api version enforcement update by @Alenar in #706
- Greg/696/certificate pending message by @ghubertpalo in #704
- Add snapshot list message and adapter by @jpraynaud in #703
Full Changelog: 2302.0...2304.0-prerelease
Crates Versions
Crate | Version |
---|---|
mithril-aggregator | 0.2.8 |
mithril-client | 0.2.5 |
mithril-common | 0.2.8 |
mithril-signer | 0.2.6 |
mithril-stm | 0.2.1 |
Verify the authenticity of a downloaded asset
Detailed procedure to verify an asset
- Step 1: Identify the downloaded asset on your computer YOUR_ASSET_FILE
- Step 2: Download the signed checksum file from this link CHECKSUM.asc and save it in the same folder as the asset
- Step 3: In your terminal, go to the asset folder by running:
cd ***YOUR_ASSET_FOLDER***
- Step 4: Then verify the checksum of the asset by running:
sha256sum -c ./CHECKSUM.asc 2>/dev/null | grep ***YOUR_ASSET_FILE***
You must see:
./***YOUR_ASSET_FILE***: OK
- Step 5: Download the public key file from this link gpg-public.key and save it in the same folder as the asset
- Step 6: Then import the GPG public key:
gpg --import ./gpg-public.key
You must see something like:
gpg: key : public key "Input Output / Mithril <mithril@iohk.io>" imported
gpg: Total number processed: 1
gpg: imported: 1
- Step 7: Then verify the GPG signature of the checksum file:
gpg --verify ./gpg-public.key ./CHECKSUM.asc
You must see something like:
gpg: Signature made Mon 05 Dec 2022 04:53:54 PM CET
gpg: using RSA key 35EDE9D47BBA62A2F388E655899ACD26B8BCA0D2
gpg: Good signature from "Input Output / Mithril <mithril@iohk.io>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 35ED E9D4 7BBA 62A2 F388 E655 899A CD26 B8BC A0D2
The signature is valid if and only if:
- there is a line with
gpg: Good signature from "Input Output / Mithril <mithril@iohk.io>"
- there is a line with
Primary key fingerprint: 2AC0 7B11 8B23 1443 F544 2D0C 6E2C 1160 3E79 0021
- Step 8:
If you successfully validated all the steps of this process, then you have successfully verified the authenticity of the asset ✔️
If not, contact us at [mithril@iohk.io] and let us know of the outcome of your run of this process⚠️