aboutsummaryrefslogtreecommitdiff
path: root/docs/source/locale/nl/LC_MESSAGES/security.po
blob: f46f1305773c843af9682622f7c0db661bb087f0 (plain)
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
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Micah Lee, et al.
# This file is distributed under the same license as the OnionShare package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: OnionShare 2.3\n"
"Report-Msgid-Bugs-To: onionshare-dev@lists.riseup.net\n"
"POT-Creation-Date: 2020-12-13 15:48-0800\n"
"PO-Revision-Date: 2023-01-31 18:46+0000\n"
"Last-Translator: Lucrezia <luctranslator@outlook.com>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: Weblate 4.16-dev\n"
"Generated-By: Babel 2.9.0\n"

#: ../../source/security.rst:2
msgid "Security Design"
msgstr "Beveiligingsontwerp"

#: ../../source/security.rst:4
msgid "Read :ref:`how_it_works` first to get a handle on how OnionShare works."
msgstr ""
"Lees eerst :ref: `how_it_works`om een idee te krijgen hoe OnionShare werkt."

#: ../../source/security.rst:6
msgid "Like all software, OnionShare may contain bugs or vulnerabilities."
msgstr ""
"Net als alle software kan ook OnionShare bugs of kwetsbaarheden bevatten."

#: ../../source/security.rst:9
msgid "What OnionShare protects against"
msgstr "Waar OnionShare tegen beschermd"

#: ../../source/security.rst:11
msgid ""
"**Third parties don't have access to anything that happens in "
"OnionShare.** Using OnionShare means hosting services directly on your "
"computer. When sharing files with OnionShare, they are not uploaded to "
"any server. If you make an OnionShare chat room, your computer acts as a "
"server for that too. This avoids the traditional model of having to trust"
" the computers of others."
msgstr ""
"**Derde partijen hebben geen toegang tot wat er gebeurt in OnionShare.** Het "
"gebruik van OnionShare betekent het hosten van diensten rechtstreeks op jouw "
"computer. Wanneer je bestanden deelt met OnionShare, dan worden naar geen "
"enkele server geüpload. Wanneer je een chatruimte maakt met OnionShare, dan "
"is je computer de server. Dit voorkomt het traditionele model dat je andere "
"computers moet vertrouwen."

#: ../../source/security.rst:13
msgid ""
"**Network eavesdroppers can't spy on anything that happens in OnionShare "
"in transit.** The connection between the Tor onion service and Tor "
"Browser is end-to-end encrypted. This means network attackers can't "
"eavesdrop on anything except encrypted Tor traffic. Even if an "
"eavesdropper is a malicious rendezvous node used to connect the Tor "
"Browser with OnionShare's onion service, the traffic is encrypted using "
"the onion service's private key."
msgstr ""
"**Netwerk-afluisteraars kunnen niets bespioneren van wat er onderweg in "
"OnionShare gebeurt.** De verbinding tussen de Tor onion service en Tor "
"Browser is end-to-end versleuteld. Dit betekent dat netwerkaanvallers niets "
"kunnen afluisteren behalve versleuteld Tor-verkeer. Zelfs als een "
"afluisteraar een kwaadwillig rendezvous-knooppunt is dat wordt gebruikt om "
"de Tor Browser met de onion service van OnionShare te verbinden, wordt het "
"verkeer versleuteld met de privésleutel van de onion service."

#: ../../source/security.rst:15
msgid ""
"**Anonymity of OnionShare users are protected by Tor.** OnionShare and "
"Tor Browser protect the anonymity of the users. As long as the OnionShare"
" user anonymously communicates the OnionShare address with the Tor "
"Browser users, the Tor Browser users and eavesdroppers can't learn the "
"identity of the OnionShare user."
msgstr ""
"**Anonimiteit van de OnionShare gebruikers wordt beschermd door Tor.** "
"OnionShare en de Tor Browser beschermen de anonimiteit van de gebruikers. "
"Zolang de OnionShare gebruiker anoniem het OnionShare adres communiceert met "
"de Tor Browser gebruikers, kunnen de Tor Browser gebruikers en afluisteraars "
"de identiteit van de OnionShare gebruiker niet achterhalen."

#: ../../source/security.rst:17
msgid ""
"**If an attacker learns about the onion service, it still can't access "
"anything.** Prior attacks against the Tor network to enumerate onion "
"services allowed the attacker to discover private .onion addresses. If an"
" attack discovers a private OnionShare address, a password will be "
"prevent them from accessing it (unless the OnionShare user chooses to "
"turn it off and make it public). The password is generated by choosing "
"two random words from a list of 6800 words, making 6800², or about 46 "
"million possible passwords. Only 20 wrong guesses can be made before "
"OnionShare stops the server, preventing brute force attacks against the "
"password."
msgstr ""
"**Als een aanvaller de onion-service achterhaald, heeft hij nog steeds "
"nergens toegang toe.** Bij eerdere aanvallen op het Tor-netwerk om onion-"
"services te verzamelen, kon de aanvaller privé .onion-adressen ontdekken. "
"Als een aanvaller een privé OnionShare-adres ontdekt, zal een wachtwoord hen "
"verhinderen er toegang toe te krijgen (tenzij de OnionShare-gebruiker ervoor "
"kiest het uit te schakelen en het openbaar te maken). Het wachtwoord wordt "
"gegenereerd door twee willekeurige woorden te kiezen uit een lijst van 6800 "
"woorden, wat neerkomt op 6800², of ongeveer 46 miljoen mogelijke "
"wachtwoorden. Er kunnen slechts 20 foutieve pogingen worden gedaan voordat "
"OnionShare de server stopt, waardoor brute force aanvallen op het wachtwoord "
"worden voorkomen."

#: ../../source/security.rst:20
msgid "What OnionShare doesn't protect against"
msgstr "Waar OnionShare geen bescherming tegen biedt"

#: ../../source/security.rst:22
msgid ""
"**Communicating the OnionShare address might not be secure.** "
"Communicating the OnionShare address to people is the responsibility of "
"the OnionShare user. If sent insecurely (such as through an email message"
" monitored by an attacker), an eavesdropper can tell that OnionShare is "
"being used. If the eavesdropper loads the address in Tor Browser while "
"the service is still up, they can access it. To avoid this, the address "
"must be communicateed securely, via encrypted text message (probably with"
" disappearing messages enabled), encrypted email, or in person. This "
"isn't necessary when using OnionShare for something that isn't secret."
msgstr ""
"**Het communiceren van het OnionShare-adres is mogelijk niet veilig.** Het "
"communiceren van het OnionShare-adres aan mensen is de verantwoordelijkheid "
"van de OnionShare-gebruiker. Als het onveilig wordt verzonden (bijvoorbeeld "
"via een e-mailbericht dat wordt bewaakt door een aanvaller), kan een "
"afluisteraar zien dat OnionShare wordt gebruikt. Als de afluisteraar het "
"adres in de Tor-browser laadt terwijl de service nog steeds bestaat, hebben "
"ze er toegang toe. Om dit te voorkomen, moet het adres veilig worden "
"gecommuniceerd, via een versleuteld sms-bericht (waarschijnlijk met "
"verdwijnende berichten ingeschakeld), versleutelde e-mail of persoonlijk. "
"Dit is niet nodig bij het gebruik van OnionShare voor iets dat niet geheim "
"is."

#: ../../source/security.rst:24
msgid ""
"**Communicating the OnionShare address might not be anonymous.** Extra "
"precautions must be taken to ensure the OnionShare address is "
"communicated anonymously. A new email or chat account, only accessed over"
" Tor, can be used to share the address. This isn't necessary unless "
"anonymity is a goal."
msgstr ""
"**Het communiceren van het OnionShare adres is mogelijk niet anoniem.** Er "
"moeten extra voorzorgsmaatregelen worden genomen om ervoor te zorgen dat het "
"OnionShare adres anoniem wordt gecommuniceerd. Een nieuw e-mail of chat "
"account, alleen toegankelijk via Tor, kan worden gebruikt om het adres te "
"delen. Dit is niet nodig tenzij anonimiteit het doel is."

#~ msgid "Security design"
#~ msgstr ""

#~ msgid ""
#~ "First read :ref:`how_it_works` to understand"
#~ " the basics of how OnionShare works."
#~ msgstr ""

#~ msgid ""
#~ "**Third parties don't have access to "
#~ "anything that happens in OnionShare.** "
#~ "When you use OnionShare, you host "
#~ "services directly on your computer. For"
#~ " example, when you share files with"
#~ " OnionShare, you don't upload these "
#~ "files to any server, and when you"
#~ " start an OnionShare chat room, your"
#~ " computer is the chat room server "
#~ "itself. Traditional ways of sharing "
#~ "files or setting up websites and "
#~ "chat rooms require trusting a service"
#~ " with access to your data."
#~ msgstr ""

#~ msgid ""
#~ "**Network eavesdroppers can't spy on "
#~ "anything that happens in OnionShare in"
#~ " transit.** Because connections between Tor"
#~ " onion services and Tor Browser are"
#~ " end-to-end encrypted, no network "
#~ "attackers can eavesdrop on what happens"
#~ " in an OnionShare service. If the "
#~ "eavesdropper is positioned on the "
#~ "OnionShare user's end, the Tor Browser"
#~ " user's end, or is a malicious "
#~ "Tor node, they will only see Tor"
#~ " traffic. If the eavesdropper is a"
#~ " malicious rendezvous node used to "
#~ "connect Tor Browser with OnionShare's "
#~ "onion service, the traffic will be "
#~ "encrypted using the onion service key."
#~ msgstr ""

#~ msgid ""
#~ "**If an attacker learns about the "
#~ "onion service, they still can't access"
#~ " anything.** There have been attacks "
#~ "against the Tor network that can "
#~ "enumerate onion services. Even if "
#~ "someone discovers the .onion address of"
#~ " an OnionShare onion service, they "
#~ "can't access it without also knowing "
#~ "the service's random password (unless, "
#~ "of course, the OnionShare users chooses"
#~ " to disable the password and make "
#~ "it public). The password is generated"
#~ " by choosing two random words from"
#~ " a list of 6800 words, meaning "
#~ "there are 6800^2, or about 46 "
#~ "million possible password. But they can"
#~ " only make 20 wrong guesses before"
#~ " OnionShare stops the server, preventing"
#~ " brute force attacks against the "
#~ "password."
#~ msgstr ""

#~ msgid ""
#~ "**Communicating the OnionShare address might"
#~ " not be secure.** The OnionShare user"
#~ " is responsible for securely communicating"
#~ " the OnionShare address with people. "
#~ "If they send it insecurely (such "
#~ "as through an email message, and "
#~ "their email is being monitored by "
#~ "an attacker), the eavesdropper will "
#~ "learn that they're using OnionShare. If"
#~ " the attacker loads the address in"
#~ " Tor Browser before the legitimate "
#~ "recipient gets to it, they can "
#~ "access the service. If this risk "
#~ "fits the user's threat model, they "
#~ "must find a more secure way to "
#~ "communicate the address, such as in "
#~ "an encrypted email, chat, or voice "
#~ "call. This isn't necessary in cases "
#~ "where OnionShare is being used for "
#~ "something that isn't secret."
#~ msgstr ""

#~ msgid ""
#~ "**Communicating the OnionShare address might"
#~ " not be anonymous.** While OnionShare "
#~ "and Tor Browser allow for anonymity, "
#~ "if the user wishes to remain "
#~ "anonymous they must take extra steps "
#~ "to ensure this while communicating the"
#~ " OnionShare address. For example, they "
#~ "might need to use Tor to create"
#~ " a new anonymous email or chat "
#~ "account, and only access it over "
#~ "Tor, to use for sharing the "
#~ "address. This isn't necessary in cases"
#~ " where there's no need to protect "
#~ "anonymity, such as co-workers who "
#~ "know each other sharing work documents."
#~ msgstr ""

#~ msgid ""
#~ "**If an attacker learns about the "
#~ "onion service, it still can't access "
#~ "anything.** Prior attacks against the "
#~ "Tor network to enumerate onion services"
#~ " allowed the attacker to discover "
#~ "private .onion addresses. If an attack"
#~ " discovers a private OnionShare address,"
#~ " a password will be prevent them "
#~ "from accessing it (unless the OnionShare"
#~ " user chooses to turn it off "
#~ "and make it public).. The password "
#~ "is generated by choosing two random "
#~ "words from a list of 6800 words,"
#~ " making 6800^2, or about 46 million"
#~ " possible passwords. Only 20 wrong "
#~ "guesses can be made before OnionShare"
#~ " stops the server, preventing brute "
#~ "force attacks against the password."
#~ msgstr ""

#~ msgid ""
#~ "**Communicating the OnionShare address might"
#~ " not be anonymous.** Extra steps must"
#~ " be taken to ensure the OnionShare"
#~ " address is communicated anonymously. A "
#~ "new email or chat account, only "
#~ "accessed over Tor, can be used to"
#~ " share the address. This isn't "
#~ "necessary unless anonymity is a goal."
#~ msgstr ""