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