forked from I2P_Developers/i2p.www
Updated translation strings
This commit is contained in:
str4d
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: I2P website\n"
|
||||
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
|
||||
"POT-Creation-Date: 2014-03-04 21:03+0000\n"
|
||||
"POT-Creation-Date: 2014-03-24 03:17+0000\n"
|
||||
"PO-Revision-Date: 2014-02-09 19:53+0000\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: he <LL@li.org>\n"
|
||||
@@ -526,7 +526,6 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/naming.html:3
|
||||
#: i2p2www/pages/site/docs/api/streaming.html:3
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:3
|
||||
#: i2p2www/pages/site/docs/spec/geoip.html:3
|
||||
#: i2p2www/pages/site/docs/transport/index.html:3
|
||||
msgid "December 2013"
|
||||
@@ -1448,7 +1447,6 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/api/bob.html:3
|
||||
#: i2p2www/pages/site/docs/api/datagrams.html:3
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:3
|
||||
#: i2p2www/pages/site/docs/protocol/index.html:3
|
||||
msgid "August 2010"
|
||||
msgstr ""
|
||||
@@ -3427,8 +3425,8 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/api/streaming.html:499
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:242
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:344
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:254
|
||||
#: i2p2www/pages/site/docs/how/network-database.html:848
|
||||
#: i2p2www/pages/site/docs/how/peer-selection.html:265
|
||||
#: i2p2www/pages/site/docs/how/tunnel-routing.html:255
|
||||
@@ -5123,6 +5121,12 @@ msgstr ""
|
||||
msgid "Low-level Cryptography Details"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:3
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:3
|
||||
msgid "March 2014"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:6
|
||||
msgid "This page specifies the low-level details of the cryptography in I2P."
|
||||
msgstr ""
|
||||
@@ -5297,7 +5301,7 @@ msgstr ""
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:176
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:273
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:352
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:391
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:406
|
||||
msgid "Obsolescence"
|
||||
msgstr ""
|
||||
|
||||
@@ -5354,10 +5358,10 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:279
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:371
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:397
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:465
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:281
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:367
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:412
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:480
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:293
|
||||
#: i2p2www/pages/site/docs/how/peer-selection.html:296
|
||||
msgid "References"
|
||||
msgstr ""
|
||||
@@ -5407,42 +5411,51 @@ msgid ""
|
||||
"prime, and we will document the construction process."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:366
|
||||
msgid ""
|
||||
"The vulnerability of the network to a DSA attack and the impact of "
|
||||
"transitioning to longer keys is to be studied.\n"
|
||||
"It may be quite difficult to make any change backward-compatible."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:374
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:376
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:370
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:372
|
||||
#, python-format
|
||||
msgid "Meeting %(num)s"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:378
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:374
|
||||
msgid "Choosing the constants"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:386
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:381
|
||||
msgid "New Signature Algorithms"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:382
|
||||
msgid ""
|
||||
"As of release 0.9.12, the router supports additional signature algorithms"
|
||||
" that are more secure than 1024-bit DSA.\n"
|
||||
"The first usage is for Destinations; support for Router Identities will "
|
||||
"be added in a future release.\n"
|
||||
"Support for migrating existing Destinations from old to new signatures "
|
||||
"will be added in a future release.\n"
|
||||
"The supported signature types are as follows. Additional signature types "
|
||||
"will be added in future releases."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:401
|
||||
#, python-format
|
||||
msgid ""
|
||||
"Hashes within I2P are plain old SHA256, as implemented in\n"
|
||||
"<a href=\"%(code)s\">[SHA256Generator]</a>"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:392
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:407
|
||||
msgid ""
|
||||
"The vulnerability of the network to a SHA-256 attack and the impact of "
|
||||
"transitioning to a longer hash is to be studied.\n"
|
||||
"It may be quite difficult to make any change backward-compatible."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:403
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:418
|
||||
msgid "Transports"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:404
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:419
|
||||
msgid ""
|
||||
"At the lowest protocol layer,\n"
|
||||
"point-to-point inter-router communication is protected by the transport "
|
||||
@@ -5458,11 +5471,11 @@ msgid ""
|
||||
"on the transport links."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:416
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:431
|
||||
msgid "NTCP connections"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:418
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:433
|
||||
#, python-format
|
||||
msgid ""
|
||||
"NTCP connections are negotiated with a 2048 Diffie-Hellman "
|
||||
@@ -5479,35 +5492,35 @@ msgid ""
|
||||
"href=\"%(elgamalaes)s\">ElGamalAES+SessionTag</a> does not."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:426
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:441
|
||||
msgid ""
|
||||
"In order to migrate to a more standardized implementation (TLS/SSL or "
|
||||
"even SSH), the following issues must be addressed:"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:430
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:445
|
||||
msgid ""
|
||||
"Can we somehow reestablish sessions securely (ala session tags) or do we "
|
||||
"need to do full negotiation each time?"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:433
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:448
|
||||
msgid ""
|
||||
"Can we simplify/avoid the x509 or other certificate formats and use our "
|
||||
"own RouterInfo structure (which \n"
|
||||
"contains the ElGamal and DSA keys)?"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:438
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:453
|
||||
#, python-format
|
||||
msgid "See <a href=\"%(ntcp)s\">the NTCP specification</a> for details."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:442
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:457
|
||||
msgid "UDP connections"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:443
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:458
|
||||
msgid ""
|
||||
"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
|
||||
" explicit IV and MAC \n"
|
||||
@@ -5520,12 +5533,12 @@ msgid ""
|
||||
"checking."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:451
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:466
|
||||
#, python-format
|
||||
msgid "See <a href=\"%(ssu)s#keys\">the SSU specification</a> for details."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:455
|
||||
#: i2p2www/pages/site/docs/how/cryptography.html:470
|
||||
#, python-format
|
||||
msgid ""
|
||||
"WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
|
||||
@@ -5542,10 +5555,6 @@ msgstr ""
|
||||
msgid "ElGamal/AES + SessionTag Encryption"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
|
||||
msgid "February 2011"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:7
|
||||
msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
|
||||
msgstr ""
|
||||
@@ -5861,7 +5870,26 @@ msgid ""
|
||||
"href=\"#new\">New Session Message</a>."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
|
||||
msgid "Session Tag Configuration Options"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
|
||||
#, python-format
|
||||
msgid ""
|
||||
"As of release 0.9.2, the client may configure the default number of "
|
||||
"Session Tags to send\n"
|
||||
"and the low tag threshold for the current session.\n"
|
||||
"For brief streaming connections or datagrams, these options may be used "
|
||||
"to significantly reduce bandwidth.\n"
|
||||
"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
|
||||
"details.\n"
|
||||
"The session settings may also be overridden on a per-message basis.\n"
|
||||
"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
|
||||
" Expires specification</a> for details."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
|
||||
msgid ""
|
||||
"There are many possible areas to tune the Session Key Manager's "
|
||||
"algorithms;\n"
|
||||
@@ -5870,68 +5898,47 @@ msgid ""
|
||||
"impact on overall performance."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:338
|
||||
msgid ""
|
||||
"Delivery of too many tags at one time may impose substantial overhead for"
|
||||
" brief streaming connections\n"
|
||||
"or datagrams, and increase the chance of message loss.\n"
|
||||
"We currently deliver 40 tags at a time (1280 bytes).\n"
|
||||
"32 (1024 bytes) may be better for tunnel fragmentation."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
|
||||
msgid ""
|
||||
"A few tags could be delivered in each of several messages, or lots of "
|
||||
"tags all at once."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:349
|
||||
msgid ""
|
||||
"It is also important to study and tune\n"
|
||||
"the low-tag thresholds at which more tags are sent."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:354
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:352
|
||||
msgid ""
|
||||
"The number of tags delivered could depend on message size, keeping in "
|
||||
"mind\n"
|
||||
"the eventual padding to 1KB at the tunnel message layer."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:359
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:357
|
||||
msgid ""
|
||||
"Clients could send an estimate of session lifetime to the router, as an "
|
||||
"advisory\n"
|
||||
"on the number of tags required."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:364
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:362
|
||||
msgid ""
|
||||
"Delivery of too few tags causes the router to fall back to an expensive "
|
||||
"ElGamal encryption."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:368
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:366
|
||||
msgid ""
|
||||
"The router may assume delivery of Session Tags, or await acknowledgement "
|
||||
"before using them;\n"
|
||||
"there are tradeoffs for each strategy."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:373
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:371
|
||||
msgid ""
|
||||
"For very brief messages, almost the full 222 bytes of the pre-IV and "
|
||||
"padding fields in the ElGamal block\n"
|
||||
"could be used for the entire message, instead of establishing a session."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:378
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:376
|
||||
msgid ""
|
||||
"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
|
||||
"Would be better to add a few tags to small messages than pad."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:383
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:381
|
||||
msgid ""
|
||||
"Perhaps things could be more efficient if the Session Tag system was "
|
||||
"bidirectional,\n"
|
||||
@@ -5942,14 +5949,14 @@ msgid ""
|
||||
"tunnel test messages to itself."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:391
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:389
|
||||
#, python-format
|
||||
msgid ""
|
||||
"Change from Session Tags to\n"
|
||||
"<a href=\"%(futureperf)s#prng\">a synchronized PRNG</a>."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:396
|
||||
#: i2p2www/pages/site/docs/how/elgamal-aes.html:394
|
||||
#, python-format
|
||||
msgid ""
|
||||
"Several of these ideas may require a new I2NP message type, or\n"
|
||||
@@ -6260,26 +6267,41 @@ msgstr ""
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:213
|
||||
#, python-format
|
||||
msgid ""
|
||||
"In the current implementation, the Delivery Status and Database Store "
|
||||
"Messages\n"
|
||||
"By default, the Delivery Status and Database Store Messages\n"
|
||||
"are bundled when the local LeaseSet changes, when additional\n"
|
||||
"<a href=\"%(commonstructures)s#type_SessionTag\">Session Tags</a>\n"
|
||||
"are delivered, or if the messages have not been bundled in the previous "
|
||||
"minute."
|
||||
"minute.\n"
|
||||
"As of release 0.9.2, the client may configure the default number of "
|
||||
"Session Tags to send\n"
|
||||
"and the low tag threshold for the current session.\n"
|
||||
"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
|
||||
"details.\n"
|
||||
"The session settings may also be overridden on a per-message basis.\n"
|
||||
"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
|
||||
" Expires specification</a> for details."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:220
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:227
|
||||
msgid ""
|
||||
"Obviously, the additional messages are currently bundled for specific "
|
||||
"purposes,\n"
|
||||
"and not part of a general-purpose routing scheme."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:226
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:232
|
||||
msgid ""
|
||||
"As of release 0.9.12, the Delivery Status Message is wrapped in another "
|
||||
"Garlic Message\n"
|
||||
"by the originator so that the contents are encrypted and not visible to "
|
||||
"routers on the return path."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:238
|
||||
msgid "Storage to the Floodfill Network Database"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:227
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:239
|
||||
#, python-format
|
||||
msgid ""
|
||||
"As explained on the\n"
|
||||
@@ -6293,7 +6315,7 @@ msgid ""
|
||||
"so it is not visible to the tunnel's outbound gateway."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:243
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:255
|
||||
#, python-format
|
||||
msgid ""
|
||||
"The Garlic Message mechanism is very flexible and provides a structure "
|
||||
@@ -6306,7 +6328,7 @@ msgid ""
|
||||
"possible."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:251
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:263
|
||||
msgid ""
|
||||
"In particular, there is potential for much more flexibility at the "
|
||||
"outbound tunnel endpoint.\n"
|
||||
@@ -6316,7 +6338,7 @@ msgid ""
|
||||
"for redundancy, or streaming audio and video."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:258
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:270
|
||||
msgid ""
|
||||
"Such experiments may conflict with the need to ensure security and "
|
||||
"anonymity, such\n"
|
||||
@@ -6326,7 +6348,7 @@ msgid ""
|
||||
"expiration times."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:264
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:276
|
||||
#, python-format
|
||||
msgid ""
|
||||
"As a part of\n"
|
||||
@@ -6339,14 +6361,14 @@ msgid ""
|
||||
"of 16 bytes."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:273
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:285
|
||||
#, python-format
|
||||
msgid ""
|
||||
"Encryption of additional messages to and from the\n"
|
||||
"<a href=\"%(netdb)s#delivery\">floodfill routers</a>."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:283
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:295
|
||||
msgid ""
|
||||
"The term garlic routing was first coined in Roger Dingledine's Free Haven"
|
||||
" \n"
|
||||
@@ -6356,30 +6378,30 @@ msgid ""
|
||||
"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:290
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:302
|
||||
msgid "Onion router publications"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:292
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:304
|
||||
msgid "Onion Routing on Wikipedia"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:294
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:306
|
||||
msgid "Garlic Routing on Wikipedia"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:296
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:308
|
||||
#, python-format
|
||||
msgid ""
|
||||
"<a href=\"%(meeting58)s\">I2P Meeting 58</a> (2003) discussing the "
|
||||
"implementation of garlic routing"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:302
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:314
|
||||
msgid "Free Haven publications"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:304
|
||||
#: i2p2www/pages/site/docs/how/garlic-routing.html:316
|
||||
msgid ""
|
||||
"Onion routing was first described in <a href=\"http://www.onion-"
|
||||
"router.net/Publications/IH-1996.pdf\">Hiding Routing Information</a>\n"
|
||||
@@ -16947,3 +16969,4 @@ msgid ""
|
||||
"conclusion is not supported by the paper."
|
||||
msgstr ""
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user