# HG changeset patch # User František Kučera # Date 1661180591 -7200 # Node ID 3d1a196aab73aea3e3ef68079ecf88a21cbb9e95 # Parent d33d6267c9d2eb22f1e487e50607f52b87cea80b a data → some data diff -r d33d6267c9d2 -r 3d1a196aab73 text/ssm.en.xml --- a/text/ssm.en.xml Sat Jul 02 23:19:41 2022 +0200 +++ b/text/ssm.en.xml Mon Aug 22 17:03:11 2022 +0200 @@ -273,7 +273,7 @@ aa0554cf-0cac-47c2-8075-54a84cb20e74 recommendation - Use randomly generated identifiers when full decentralization is desired. These identifiers might be just random (e.g. UUID version 4) or derived from a public key (e.g. an SSH key or a Tor address) or a hash of a (secret) data. + Use randomly generated identifiers when full decentralization is desired. These identifiers might be just random (e.g. UUID version 4) or derived from a public key (e.g. an SSH key or a Tor address) or a hash of some (secret) data. When public key or a hash of secret data is used, then ownership of the name or namespace can be reliably proved. Random identifiers must be picked from a sufficiently large space where we can assume that collisions are effectively eliminated.