aboutsummaryrefslogtreecommitdiff
path: root/template/glossary.html.j2
diff options
context:
space:
mode:
Diffstat (limited to 'template/glossary.html.j2')
-rw-r--r--template/glossary.html.j283
1 files changed, 70 insertions, 13 deletions
diff --git a/template/glossary.html.j2 b/template/glossary.html.j2
index f0429e84..d8f6c0e5 100644
--- a/template/glossary.html.j2
+++ b/template/glossary.html.j2
@@ -1,42 +1,99 @@
1{% extends "common/base.j2" %} 1{% extends "common/base.j2" %}
2{% block body_content %} 2{% block body_content %}
3<div class="container"> 3<div class="container">
4
5<dl> 4<dl>
6<!-- 5<dt>{{ _("Ego") }}</dt>
7<dt>{{ _("term") }}</dt>
8 <dd> 6 <dd>
9 {% trans %} 7 {% trans %}
10 explanation 8 We use the term "Ego" to refer to the fact that users in GNUnet
9 can have multiple unlinkable identities, in the sense of alter egos.
10 The ability to have more than one identity is crucial, as we may
11 want to keep our egos for business separate from those we use
12 for political activities or romance.<br>
13 Egos in GNUnet are technically
14 equivalent to identities (and the code does not distinguish
15 between them). We simply sometimes use the term "ego" to stress
16 that you can have more than one.
11 {% endtrans %} 17 {% endtrans %}
12 </dd> 18 </dd>
13</dt> 19</dt>
14--> 20<dt>{{ _("Identity") }}</dt>
15<dt>{{ _("Ego") }}</dt>
16 <dd> 21 <dd>
17 {% trans %} 22 {% trans %}
18 explanation 23 In GNUnet users are identified via a public key, and that public
24 key is then often referred to as the "Identity" of the user.
25 However, the concept is not as draconian as it often is in real
26 life where many are forced to have one name, one passport and
27 one unique identification number.
28 <br>
29 As long as identities in GNUnet are simply
30 public keys, users are free to create any number of identities,
31 and we call those egos to emphasize the difference. Even though
32 users can create such egos freely, it is possible to have
33 an ego certified by some certification authority, resulting
34 in something that more closely resembles the traditional concept
35 of an identity.<br>
36 For example, a university may certify the identities of its students
37 such that they can prove that they are studying. Students may
38 keep their (certified) student identity separate from other egos
39 that they use for other activities in life.
19 {% endtrans %} 40 {% endtrans %}
20 </dd> 41 </dd>
21</dt> 42</dt>
22<dt>{{ _("Identity") }}</dt> 43<dt>{{ _("Pseudonym") }}</dt>
23 <dd> 44 <dd>
24 {% trans %} 45 {% trans %}
25 explanation 46 A pseudonym is an ego that is specifically intended
47 to not be linked to one's real name. GNUnet users can create
48 many egos, and thus also many pseudonyms.
49 <br>
50 Repeated uses of
51 the same pseudonym are linkable by definition, as they involve
52 the same public key. Anonymity requires the use of either the
53 special "anonymous" pseudonym (for GNUnet, this is the neutral
54 element on the elliptic curve) or a throw-away pseudonym that
55 is only used once.
26 {% endtrans %} 56 {% endtrans %}
27 </dd> 57 </dd>
28</dt> 58</dt>
29<dt>{{ _("Pseudonym") }}</dt> 59<dt>{{ _("Namespaces") }}</dt>
30 <dd> 60 <dd>
31 {% trans %} 61 {% trans %}
32 explanation 62 The GNU Name System allows every ego (or identity) to
63 securely and privately associate any number of label-value pairs
64 with an ego. The values are called record sets following the
65 terminology of the Domain Name System (DNS). The mapping of
66 labels to record sets for a given ego is called a namespace.
67 <br>
68 If records are made public and thus published, it is possible
69 for other users to lookup the record given the ego's public key
70 and the label. Here, not only the label can thus act as a
71 passphrase but also the public key -- which despite its name
72 may not be public knowledge and is never disclosed by the GNS
73 protocol itself.
33 {% endtrans %} 74 {% endtrans %}
34 </dd> 75 </dd>
35</dt> 76</dt>
36<dt>{{ _("Namespaces") }}</dt> 77<dt>{{ _("Peer") }}</dt>
37 <dd> 78 <dd>
38 {% trans %} 79 {% trans %}
39 explanation 80 A "peer" is an instance of GNUnet with its own per-instance
81 public key and network addresses. Technically, it is possible
82 to run multiple peers on the same host, but this only makes
83 sense for testing.
84 <br>
85 By design GNUnet supports multiple
86 users to share the same peer, just as UNIX is a multi-user
87 system. A "peer" typically consists of a set of foundational GNUnet
88 services running as the "gnunet" user and allowing all users
89 in the "gnunet" group to utilize the API. On multi-user
90 systems, additional "personalized" services may be required
91 per user.
92 <br>
93 While peers are also identified by public keys, these
94 public keys are completely unrelated to egos or
95 identities. Namespaces cannot be associated with a
96 peer, only with egos.
40 {% endtrans %} 97 {% endtrans %}
41 </dd> 98 </dd>
42</dt> 99</dt>