martin/databag
1
0
Fork 0
mirror of https://github.com/balzack/databag.git synced 2025-03-13 00:50:03 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update design_overview.md

Browse Source
This commit is contained in:
Pierre Balzack 2024-03-22 14:36:50 -07:00 committed by GitHub
parent 4ea24efd21
commit 96629ff26c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/design_overview.md
View File

@ -49,7 +49,7 @@ The revision mechanism allows for the efficient synchronization for both new and
While the profile describes the account holder, the identity is determined by a public/private key. Regardless of what may be stored in the profile, a fingerprint of the public key uniquely identifies the account. At account creation time a key pair is generated which becomes the identity of the account for its lifetime. The private key never leaves the server and all signing of data happens within the server.
<div align="center">
<a href="#"><img src="/doc/overview_fig4.png" width="50%" style="border-radius:50%"></a>
<a href="#"><img src="/doc/overview_fig4.png" width="40%" style="border-radius:50%"></a>
</div>
The discovery of other contacts in the system is achieved through a signed profile message. When enabled the profile message can be accessed through a public endpoint on the node. One of the fields in the profile is the public key fingerprint so the receiving client and server can verify the integrity of the profile. When a new profile message is received at the node, a new card object is created with the profile contents for future reference.