kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make usage of 2-word Address Book consistent across website, except preserve old blog posts as is

Browse Source
This commit is contained in:
idk
2021-01-23 21:06:01 -05:00
parent 8c3bfb60ec
commit 8891b5e8c0
12 changed files with 63 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
i2p2www/pages/site/docs/api/bob.html
View File

@@ -213,7 +213,7 @@ C A OK Bye!
<p>{% trans -%}
Now all we need to do is telnet into 127.0.0.1, port 37337,
send the destination key or host address from addressbook we want to contact.
send the destination key or host address from address book we want to contact.
In this case, we want to contact "mouth", all we do is paste in the
key and it goes.
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/api/socks.html
View File

@@ -47,7 +47,7 @@ work that simply using the existing I2P APIs.
<p>{% trans -%}
The SOCKS proxy
supports standard addressbook names, but not Base64 destinations.
supports standard address book names, but not Base64 destinations.
Base32 hashes should work as of release 0.7.
It supports outgoing connections only, i.e. an I2PTunnel Client.
UDP support is stubbed out but not working yet.

16
i2p2www/pages/site/docs/discussions/naming.html
View File

@@ -104,7 +104,7 @@ Others have suggested asking for specific keys only (similar to what jump servic
in a more automated fashion), possibly at a further cost in anonymity.
{%- endtrans %}</p>
<p>{% trans i2host=i2pconv('i2host.i2p') -%}
Possible improvements would be a replacement or supplement to addressbook (see <a href="http://{{ i2host }}/">{{ i2host }}p</a>),
Possible improvements would be a replacement or supplement to address book (see <a href="http://{{ i2host }}/">{{ i2host }}p</a>),
or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.
If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,
that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag.
@@ -116,7 +116,7 @@ This script returns an Etag with a timestamp.
When a request comes in with the If-None-Match etag,
the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.
In this way, the script efficiently returns only the hosts the subscriber
does not know about, in an addressbook-compatible manner.
does not know about, in an address book-compatible manner.
{%- endtrans %}</p>
<p>{% trans -%}
So the inefficiency is not a big issue and there are several ways to improve things without
@@ -138,7 +138,7 @@ a key, you need to have the whole set of keys stored locally, at a cost of about
<li>
<p>{% trans -%}
<b>Requires configuration and "trust":</b>
Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,
Out-of-the-box address book is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,
leading to poor new-user experience.
{%- endtrans %}</p>
<p>{% trans -%}
@@ -177,7 +177,7 @@ Sure, we could make it work, but why? It's a bad fit.
<li>
<p>{% trans -%}
<b>Not reliable:</b>
It depends on specific servers for addressbook subscriptions.
It depends on specific servers for address book subscriptions.
{%- endtrans %}</p>
<p>{% trans -%}
Yes it depends on a few servers that you have configured.
@@ -185,7 +185,7 @@ Within i2p, servers and services come and go.
Any other centralized system (for example DNS root servers) would
have the same problem. A completely decentralized system (everybody is authoritative)
is possible by implementing an "everybody is a root DNS server" solution, or by
something even simpler, like a script that adds everybody in your hosts.txt to your addressbook.
something even simpler, like a script that adds everybody in your hosts.txt to your address book.
{%- endtrans %}</p>
<p>{% trans -%}
People advocating all-authoritative solutions generally haven't thought through
@@ -257,7 +257,7 @@ See core/java/src/net/i2p/client/naming for details.
{%- endtrans %}</p>
<p>{% trans -%}
Any new system should be stacked with HostsTxt, or should
implement local storage and/or the addressbook subscription functions, since addressbook
implement local storage and/or the address book subscription functions, since address book
only knows about the hosts.txt files and format.
{%- endtrans %}</p>
@@ -266,7 +266,7 @@ only knows about the hosts.txt files and format.
I2P destinations contain a certificate, however at the moment that certificate
is always null.
With a null certificate, base64 destinations are always 516 bytes ending in "AAAA",
and this is checked in the addressbook merge mechanism, and possibly other places.
and this is checked in the address book merge mechanism, and possibly other places.
Also, there is no method available to generate a certificate or add it to a
destination. So these will have to be updated to implement certificates.
{%- endtrans %}</p>
@@ -280,7 +280,7 @@ i2p uses a flat naming system) to be signed by the 2nd level domain's keys.
<p>{% trans -%}
With any certificate implementation must come the method for verifying the
certificates.
Presumably this would happen in the addressbook merge code.
Presumably this would happen in the address book merge code.
Is there a method for multiple types of certificates, or multiple certificates?
{%- endtrans %}</p>
<p>{% trans -%}

14
i2p2www/pages/site/docs/how/tech-intro.html
View File

@@ -832,9 +832,9 @@ abstraction of TCP, with its sliding windows, congestion control algorithms
SYN, FIN, RST, etc).
{%- endtrans %}</p>
<h2 id="app.naming">{% trans %}Naming library and addressbook{% endtrans %}</h2>
<h2 id="app.naming">{% trans %}Naming library and address book{% endtrans %}</h2>
<p><i>{% trans naming=site_url('docs/naming') -%}
For more information see the <a href="{{ naming }}">Naming and Addressbook</a> page.
For more information see the <a href="{{ naming }}">Naming and Address Book</a> page.
{%- endtrans %}</i></p>
<p><i>{% trans dev='mihi, Ragnarok' -%}Developed by: {{ dev }}{%- endtrans %}</i></p>
@@ -846,16 +846,16 @@ inherent demand for secure communication and decentralized operation, the
traditional DNS-style naming system is clearly out, as are "majority rules"
voting systems. Instead, I2P ships with a generic naming library and a base
implementation designed to work off a local name to destination mapping, as
well as an optional add-on application called the "addressbook". The addressbook
well as an optional add-on application called the "Address Book". The address book
is a web-of-trust-driven secure, distributed, and human readable naming system,
sacrificing only the call for all human readable names to be globally unique
by mandating only local uniqueness. While all messages in I2P are cryptographically
addressed by their destination, different people can have local addressbook
addressed by their destination, different people can have local address book
entries for "Alice" which refer to different destinations. People can still
discover new names by importing published addressbooks of peers specified
discover new names by importing published address books of peers specified
in their web of trust, by adding in the entries provided through a third party,
or (if some people organize a series of published addressbooks using a first
come first serve registration system) people can choose to treat these addressbooks
or (if some people organize a series of published address books using a first
come first serve registration system) people can choose to treat these address books
as name servers, emulating traditional DNS.
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/how/threat-model.html
View File

@@ -860,7 +860,7 @@ Routers rely on a single news host, but there is a hardcoded backup URL pointing
A malicious news host could feed a huge file, need to limit the size.
{%- endtrans %}</li>
<li>{% trans naming=site_url('docs/naming') -%}
<a href="{{ naming }}">Naming system services</a>, including addressbook subscription providers, add-host services,
<a href="{{ naming }}">Naming system services</a>, including address book subscription providers, add-host services,
and jump services, could be malicious. Substantial protections for subscriptions were implemented
in release 0.6.1.31, with additional enhancements in subsequent releases.
However, all naming services require some measure of trust, see

4
i2p2www/pages/site/docs/index.html
View File

@@ -39,8 +39,8 @@ If you find any inaccuracies in the documents linked below, please
<h3>{% trans %}Application-Layer Topics{% endtrans %}</h3>
<ul>
<li><a href="{{ site_url('get-involved/develop/applications') }}">Application Development Overview and Guide</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Addressbook') }}</a></li>
<li><a href="{{ spec_url('subscription') }}">{{ _('Addressbook Subscription Feed Commands') }}</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Address Book') }}</a></li>
<li><a href="{{ spec_url('subscription') }}">{{ _('Address Book Subscription Feed Commands') }}</a></li>
<li><a href="{{ site_url('docs/plugins') }}">{{ _('Plugins Overview') }}</a></li>
<li><a href="{{ spec_url('plugin') }}">{{ _('Plugin Specification') }}</a></li>
<li><a href="{{ site_url('docs/applications/managed-clients') }}">{{ _('Managed Clients') }}</a></li>

52
i2p2www/pages/site/docs/naming.html
View File

@@ -1,5 +1,5 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Naming and Addressbook{% endtrans %}{% endblock %}
{% block title %}{% trans %}Naming and Address Book{% endtrans %}{% endblock %}
{% block lastupdated %}2020-07{% endblock %}
{% block accuratefor %}0.9.46{% endblock %}
{% block content %}
@@ -8,21 +8,21 @@
<p>{% trans -%}
I2P ships with a generic naming library and a base implementation
designed to work off a local name to destination mapping, as well as an
add-on application called the <a href="#addressbook">addressbook</a>.
add-on application called the <a href="#addressbook">address book</a>.
I2P also supports <a href="#base32">Base32 hostnames</a> similar to Tor's .onion addresses.
{%- endtrans %}</p>
<p>{% trans -%}
The addressbook is a web-of-trust
The address book is a web-of-trust
driven secure, distributed, and human readable naming system, sacrificing only
the call for all human readable names to be globally unique by mandating only
local uniqueness. While all messages in I2P are cryptographically addressed
by their destination, different people can have local addressbook entries for
by their destination, different people can have local address book entries for
"Alice" which refer to different destinations. People can still discover new
names by importing published addressbooks of peers specified in their web of trust,
names by importing published address books of peers specified in their web of trust,
by adding in the entries provided through a third party, or (if some people organize
a series of published addressbooks using a first come first serve registration
system) people can choose to treat these addressbooks as name servers, emulating
a series of published address books using a first come first serve registration
system) people can choose to treat these address books as name servers, emulating
traditional DNS.
{%- endtrans %}</p>
@@ -63,12 +63,12 @@ HTTP <a href="#add-services">host-add forms</a> which allow users to add hosts t
HTTP <a href="#jump-services">jump services</a> which provide their own lookups and redirection.
{%- endtrans %}</li>
<li>{% trans -%}
The <a href="#addressbook">addressbook</a> application which merges external
The <a href="#addressbook">address book</a> application which merges external
host lists, retrieved via HTTP, with the local list.
{%- endtrans %}</li>
<li>{% trans -%}
The <a href="#susidns">SusiDNS</a> application which is a simple web front-end
for addressbook configuration and viewing of the local host lists.
for address book configuration and viewing of the local host lists.
{%- endtrans %}</li>
</ol>
@@ -114,7 +114,7 @@ The files are:
<h3>{{ _('Blockfile Naming Service') }}</h3>
<p>{% trans -%}
The Blockfile Naming Service stores multiple "addressbooks" in a single
The Blockfile Naming Service stores multiple "address books" in a single
database file named hostsdb.blockfile.
This Naming Service is the default since release 0.8.8.
{%- endtrans %}</p>
@@ -126,7 +126,7 @@ The blockfile format is specified on the <a href="{{ blockfile }}">Blockfile pag
It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,
the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.
In addition, the blockfile provides the capability of arbitrary metadata storage
(such as added date, source, and comments) for each entry to implement advanced addressbook features.
(such as added date, source, and comments) for each entry to implement advanced address book features.
The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides
approximately 10x reduction in lookup times.
{%- endtrans %}</p>
@@ -180,11 +180,11 @@ an error page to the user with links to several "jump" services.
See below for details.
{%- endtrans %}</p>
<h2 id="addressbook">{% trans %}Addressbook{% endtrans %}</h2>
<h2 id="addressbook">{% trans %}Address Book{% endtrans %}</h2>
<h3>{% trans %}Incoming Subscriptions and Merging{% endtrans %}</h3>
<p>{% trans -%}
The addressbook application periodically
The address book application periodically
retrieves other users' hosts.txt files and merges
them with the local hosts.txt, after several checks.
Naming conflicts are resolved on a first-come first-served
@@ -205,11 +205,11 @@ default is <code>http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5
which contains a copy of the hosts.txt included
in the I2P release.
Users must configure additional subscriptions in their
local addressbook application (via subscriptions.txt or <a href="#susidns">SusiDNS</a>).
local address book application (via subscriptions.txt or <a href="#susidns">SusiDNS</a>).
{%- endtrans %}</p>
<p>{% trans -%}
Some other public addressbook subscription links:
Some other public address book subscription links:
{%- endtrans %}</p>
<ul>
<li><a href="http://{{ i2pconv('i2host.i2p') }}/cgi-bin/i2hostetag">http://{{ i2pconv('i2host.i2p') }}/cgi-bin/i2hostetag</a>
@@ -223,7 +223,7 @@ Presence on this list does not imply endorsement.
<h3>{% trans %}Naming Rules{% endtrans %}</h3>
<p>{% trans -%}
While there are hopefully not any technical limitations within I2P on host names,
the addressbook enforces several restrictions on host names
the address book enforces several restrictions on host names
imported from subscriptions.
It does this for basic typographical sanity and compatibility with browsers,
and for security.
@@ -308,7 +308,7 @@ Note that the '.' symbols in a host name are of no significance,
and do not denote any actual naming or trust hierarchy.
If the name 'host.i2p' already exists, there is nothing
to prevent anybody from adding a name 'a.host.i2p' to their hosts.txt,
and this name can be imported by others' addressbook.
and this name can be imported by others' address book.
Methods to deny subdomains to non-domain 'owners' (certificates?),
and the desirability and feasibility of these methods,
are topics for future discussion.
@@ -321,7 +321,7 @@ add 'network.IDN.whitelist.i2p (boolean) = true' in about:config.
{%- endtrans %}</p>
<p>{% trans -%}
As the addressbook application does not use privatehosts.txt at all, in practice
As the address book application does not use privatehosts.txt at all, in practice
this file is the only place where it is appropriate to place private aliases or
"pet names" for sites already in hosts.txt.
{%- endtrans %}</p>
@@ -336,7 +336,7 @@ See <a href="/spec/subscription">the specification</a> for details.
<h3>{% trans %}Outgoing Subscriptions{% endtrans %}</h3>
<p>{% trans -%}
Addressbook will publish the merged hosts.txt to a location
Address Book will publish the merged hosts.txt to a location
(traditionally hosts.txt in the local I2P Site's home directory) to be accessed by others
for their subscriptions.
This step is optional and is disabled by default.
@@ -344,7 +344,7 @@ This step is optional and is disabled by default.
<h3>Hosting and HTTP Transport Issues</h3>
<p>{% trans -%}
The addressbook application, together with eepget, saves the Etag and/or Last-Modified
The address book application, together with eepget, saves the Etag and/or Last-Modified
information returned by the web server of the subscription.
This greatly reduces the bandwidth required, as the web server will
return a '304 Not Modified' on the next fetch if nothing has changed.
@@ -373,7 +373,7 @@ will be propagated through the network.
{%- endtrans %}</p>
<p>{% trans -%}
It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.
It is recommended that host add services impose, at a minimum, the restrictions imposed by the address book application listed above.
Host add services may impose additional restrictions on hostnames and keys, for example:
{%- endtrans %}</p>
<ul>
@@ -446,15 +446,15 @@ several hosts.txt providers so that its local host list is current.
<h2 id="susidns">SusiDNS</h2>
<p>{% trans -%}
SusiDNS is simply a web interface front-end to configuring addressbook subscriptions
and accessing the four addressbook files.
All the real work is done by the 'addressbook' application.
SusiDNS is simply a web interface front-end to configuring address book subscriptions
and accessing the four address book files.
All the real work is done by the 'address book' application.
{%- endtrans %}</p>
<p>{% trans -%}
Currently, there is little enforcement of addressbook naming rules within SusiDNS,
Currently, there is little enforcement of address book naming rules within SusiDNS,
so a user may enter hostnames locally that would be rejected by
the addressbook subscription rules.
the address book subscription rules.
{%- endtrans %}</p>
<h2 id="base32">{% trans %}Base32 Names{% endtrans %}</h2>