Skip to Content

Changes for page Definitions

Last modified by Zenna Elfen on 2025/11/27 12:13
From version 6.1
edited by Zenna Elfen
on 2025/11/27 12:13
Change comment: There is no comment for this version
To version 1.1
edited by Zenna Elfen
on 2025/11/23 23:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -P4P.WebHome
1 +P4P.Projects.WebHome
Content
... ... @@ -1,33 +1,21 @@
1 1  == Definitions for Authentication and Access ==
2 2  
3 -(% border="1" dir="ltr" id="auth_def" style="margin-right:auto" summary="Definitions for Authentication and Access" %)
3 +(% dir="ltr" id="auth_def" style="margin-right:auto" summary="Definitions for Authentication and Access" %)
4 4  |=Function|=What it means in P2P context
5 -|Permissions|//Define what actions a peer is allowed to perform (read, write, broadcast, modify state, etc.)//
6 -|Delegation|//Allow a peer to grant some portion of its authority to another peer (e.g., "you can write to this dataset for 1 day")//
7 -|Capabilities|//Tokens/objects that embody permissions and can be passed around securely//
8 -|Revocation|//Ability to withdraw access (essential yet tricky, since there's no central admin)//
9 -|Identity-agnostic control|//Often operations are authorized not by who you are but what capabilities you possess//
5 +|**Permissions**|Define what actions a peer is allowed to perform (read, write, broadcast, modify state, etc.)
6 +|**Delegation**|Allow a peer to grant some portion of its authority to another peer (e.g., "you can write to this dataset for 1 day")
7 +|**Capabilities**|Tokens/objects that //embody// permissions and can be passed around securely
8 +|**Revocation**|Ability to withdraw access (essential yet tricky, since there's no central admin)
9 +|**Identity-agnostic control**|Often operations are authorized not by //who// you are but //what capabilities you possess//
10 10  
11 11  
12 12  
13 -== ==
14 -
15 -== ==
16 -
17 -== ==
18 -
19 -== ==
20 -
21 -== ==
22 -
23 23  == Definitions for Security and Encryption ==
24 24  
25 -(% border="1" dir="ltr" id="sec_def" style="margin-right:auto" summary="Definitions for Security and Encryption" %)
15 +(% dir="ltr" id="sec_def" style="margin-right:auto" summary="Definitions for Security and Encryption" %)
26 26  |=Security Function|=Purpose|=Examples
27 27  |Transport Encryption|//P2P channel confidentiality//|//TLS, Noise//
28 -|[[Private Interest Overlap>>https://willowprotocol.org/specs/pio/index.html#private_interest_overlap]]|//allows peers to securely determine if they have capabilities in common without revealing what those capabilities are//|//Willow//
29 -|[[Prefix Pruning>>https://willowprotocol.org/specs/data-model/index.html#prefix_pruning]]|Enables removal of data by replacing data with a new timestamped file that is empty, encouraging replication of the deletion.  "you have a path hierarchy which lets you prune off a whole bunch of leaves by cutting at the root. Like if you replaced your Documents directory with a text file of the same name."|//Willow//
30 -|Message" Encryption|//End-to-end secrecy, async//|//MLS, Olm/Megolm, DR//
18 +|Message Encryption|//End-to-end secrecy, async//|//MLS, Olm/Megolm, DR//
31 31  |Identity & Trust|//Who’s who, key bootstrapping//|//DIDs, TOFU, Web-of-trust//
32 32  |Integrity|//Detect tampering//|//AEAD, Merkle DAGs//
33 33  |Key Lifecycle|//Rotation, revocation, recovery//|//X3DH, key transparency//