Skip to content

Commit 6d4fc81

Browse files
committed
update README to reflect pubkey change done on 2025-12-10
The applicable public key has changed from key ID 1 to key ID 2 on 2025-12-10, so the filenames of the GSC products change. The Merkle tree root is the same, but the Merkle tree XML from GSC is different because it also contains the current public key and intermediate tree nodes.
1 parent 0a03e4f commit 6d4fc81

1 file changed

Lines changed: 10 additions & 9 deletions

File tree

README.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -96,26 +96,27 @@ signal-in-space for a public key renewal or revocation. If only the Merkle tree
9696
root is given, it will be necessary to wait until the current ECDSA public key
9797
is broadcast in the signal-in-space.
9898

99-
The public key and the Merkle tree root can be
100-
downloaded from the [European GNSS Service Centre](https://www.gsc-europa.eu/),
101-
under [GSC Products > OSNMA_PUBLICKEY](https://www.gsc-europa.eu/gsc-products/OSNMA/PKI).
102-
It is necessary to register an account to obtain these files.
99+
The public key and the Merkle tree root can be downloaded from the [European
100+
GNSS Service Centre](https://www.gsc-europa.eu/), under [GSC Products >
101+
OSNMA_MERKLETREE](https://www.gsc-europa.eu/gsc-products/OSNMA/MT) and [GSC
102+
Products > OSNMA_PUBLICKEY](https://www.gsc-europa.eu/gsc-products/OSNMA/PKI)
103+
respectively. It is necessary to register an account to obtain these files.
103104

104105
The public key is downloaded as an x509 certificate. The Public Key ID is included
105106
in the filename, and it is also listed elsewhere in the GSC Products website.
106-
The current certificate file is `OSNMA_PublicKey_20240115100000_newPKID_1.crt`,
107-
and the corresponding Public Key ID is `1`. The key in PEM format, as required by
107+
The current certificate file is `OSNMA_PublicKey_20251210100000_newPKID_2.crt`,
108+
and the corresponding Public Key ID is `2`. The key in PEM format, as required by
108109
`galmon-osnma` can be extracted with
109110
```
110-
openssl x509 -in OSNMA_PublicKey_20240115100000_newPKID_1.crt -noout -pubkey > osnma-pubkey.pem
111+
openssl x509 -in OSNMA_PublicKey_20251210100000_newPKID_2.crt -noout -pubkey > osnma-pubkey.pem
111112
```
112113

113114
The Merkle tree information is downloaded in an XML file. The current file is
114-
`OSNMA_MerkleTree_20240115100000_newPKID_1.xml`. The tree root,
115+
`OSNMA_MerkleTree_20251210100000_newPKID_2.xml`. The tree root,
115116
expressed as a 256-bit hexadecimal number can be extracted from the XML file
116117
with
117118
```
118-
./utils/extract_merkle_tree_root.py OSNMA_MerkleTree_20240115100000_newPKID_1.xml
119+
./utils/extract_merkle_tree_root.py OSNMA_MerkleTree_20251210100000_newPKID_2.xml
119120
```
120121
This 256-bit hexadecimal format is the one that is directly used by the `galmon-osnma`
121122
`--merkle-root` argument. The tree root is also listed in other parts of the GSC Products

0 commit comments

Comments
 (0)