From 13531ae8246634aa00f258c54ae42c6e20661ec5 Mon Sep 17 00:00:00 2001
From: ovari123 <ovari123@zoho.com>
Date: Sun, 26 Jan 2025 05:28:45 -0400
Subject: [PATCH] extension/jami-extension-certificate.md: cleanup
Change-Id: Iab3a54941daf230e85daa06f4150ce343d3785a7
---
extension/jami-extension-certificate.md | 34 +++++++++++++------------
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/extension/jami-extension-certificate.md b/extension/jami-extension-certificate.md
index 1224065f..9f896b4e 100644
--- a/extension/jami-extension-certificate.md
+++ b/extension/jami-extension-certificate.md
@@ -1,9 +1,11 @@
# Jami extension certificates
-**NOTE: This page describes the architecture of certificates on the Jami Extension Store.**
+```{note}
+This page describes the architecture of certificates on the Jami Extension Store.
+```
The Jami team introduced extensions as a call/chat feature for GNU/Linux, Windows, macOS, and Android, providing users the ability to personalize the call/chat experience.
-To learn more about Jami extensions, visit the [Extension manual](./extension.md).
+To learn more about Jami extensions, visit the [Extension manual](index).
The Jami team implemented a Jami Extension Store to be able to distribute extensions from the Jami team and from third parties.
A certificate mechanism is required to ensure trust in the Jami team and third-party extensions.
Certificates play a crucial role in verifying the authenticity of extensions available on the Jami Extension Store.
@@ -84,19 +86,19 @@ The certificate chain is the following: Store Root CA `→` Organization Certifi
The root certificate structure is:
```bash
- Certificate:
- tbsCertificate:
- version: 2
- serialNumber: <generate-by-design>
- signature: AlgorithmIdentifier { algorithm: sha512WithRSAEncryption }
- issuer: Name { commonName: "Store Root CA" }
- validity:
- notBefore: Time { utcTime: "20220101000000Z" }
- notAfter: Time { utcTime: "20520101000000Z" }
- subject: Name { commonName: "Store Root CA" }
- subjectPublicKeyInfo:
- algorithm: AlgorithmIdentifier { algorithm: id-ecdsa-with-shake256 }
- subjectPublicKey: BIT STRING (ECDSA-256 public key)
+Certificate:
+ tbsCertificate:
+ version: 2
+ serialNumber: <generate-by-design>
+ signature: AlgorithmIdentifier { algorithm: sha512WithRSAEncryption }
+ issuer: Name { commonName: "Store Root CA" }
+ validity:
+ notBefore: Time { utcTime: "20220101000000Z" }
+ notAfter: Time { utcTime: "20520101000000Z" }
+ subject: Name { commonName: "Store Root CA" }
+ subjectPublicKeyInfo:
+ algorithm: AlgorithmIdentifier { algorithm: id-ecdsa-with-shake256 }
+ subjectPublicKey: BIT STRING (ECDSA-256 public key)
```
This structure is based on [RFC standard certificate v3](https://www.ietf.org/rfc/rfc2459.txt).
@@ -251,4 +253,4 @@ python3 ./certKey.py revoke --crl /tmp/bar --subject /tmp/foo --issuer /tmp/bar
```bash
python3 ./certKey.py --plugin verify --path /tmp/foo
-```
+```
\ No newline at end of file
--
GitLab