forked from I2P_Developers/i2p.www
misc. small changes
This commit is contained in:
@@ -1,31 +0,0 @@
|
||||
WARNING - if you can read this you will trust anybody!
|
||||
The revision containing this file was signed by
|
||||
untrusted-test@mail.i2p as a test.
|
||||
|
||||
Monotone databases may contain untrusted content. Trust in monotone
|
||||
is enforced ONLY on checkout and update, NOT when syncing with remote databases.
|
||||
|
||||
If you are reading this, you will trust anybody -
|
||||
you should fix this by putting the following
|
||||
trust hook in your ~/.monotonoe/monotonerc file:
|
||||
|
||||
function get_revision_cert_trust(signers, id, name, val)
|
||||
local trusted_signers = { "complication@mail.i2p", "zzz@mail.i2p" }
|
||||
local t = intersection(signers, trusted_signers)
|
||||
if t == nil then return false end
|
||||
if table.getn(t) >= 1 then return true end
|
||||
return false
|
||||
end
|
||||
|
||||
Edit as you wish to include only the signers YOU trust.
|
||||
|
||||
Now, since you can't trust anything in this directory
|
||||
that you checked out (the directory containing this file),
|
||||
you should delete the whole thing and check it out again.
|
||||
|
||||
You should get a message like:
|
||||
|
||||
mtn: warning: trust function disliked 1 signers of branch cert on revision c84b3ecdcf7b2cf7d6091f230bced401613bd5b0
|
||||
|
||||
... and you will not see this file.
|
||||
Now you know your trust hook is working.
|
@@ -12,7 +12,7 @@
|
||||
<a href="http://mirror.i2p2.de/i2pheadless-0.6.1.31.tar.bz2">i2pheadless-0.6.1.31.tar.bz2</a>
|
||||
(SHA1 201cacbf5fadf8d3f29cfb422241cffab49732ee
|
||||
<a href="http://mirror.i2p2.de/i2pheadless-0.6.1.31.tar.bz2.sig">sig</a>)<br />
|
||||
Run <code>(tar xjvf i2p-0.6.1.31.tar.bz2 ; cd i2p ; vi install-headless.txt)</code></li>
|
||||
Run <code>(tar xjvf i2pheadless-0.6.1.31.tar.bz2 ; cd i2p ; vi install-headless.txt)</code></li>
|
||||
<li>Source install:<br />
|
||||
<a href="http://mirror.i2p2.de/i2psource-0.6.1.31.tar.bz2">i2psource-0.6.1.31.tar.bz2</a>
|
||||
(SHA1 1341a4f500c0c0644b05dd39f8ea39699af15920
|
||||
|
@@ -72,6 +72,14 @@ See the
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2068">I2P Bittorrent FAQ</a>
|
||||
<a href="http://forum.i2p.net/viewtopic.php?t=2068">(outside I2P)</a>
|
||||
|
||||
<h3 id="irc">How do I connect to IRC within I2P?
|
||||
<span class="permalink">(<a href="#irc">link</a>)</span></h3>
|
||||
<p>
|
||||
On the
|
||||
<a href="http://localhost:7657/i2ptunnel/index.jsp">I2PTunnel configuration page</a>,
|
||||
start the ircProxy.
|
||||
Then tell your IRC client to connect to localhost port 6668.
|
||||
|
||||
<h3 id="remote_webconsole">How can I access the web console from my other machines or password protect it?
|
||||
<span class="permalink">(<a href="#remote_webconsole">link</a>)</span></h3>
|
||||
<p>
|
||||
|
@@ -16,7 +16,7 @@ included in your OS / distribution or installed already, it can be received from
|
||||
<a href="http://www.swox.com/gmp/">http://www.swox.com/gmp/</a>. Even if you
|
||||
have already installed it as binary, it might still be worth a try to compile
|
||||
GMP yourself, since then it will be able to use the specific instructions of
|
||||
your processor. From I2P source of 0.6.1.31-6 on latest GMP 4.2.2 is also
|
||||
your processor. The latest GMP 4.2.2 is also
|
||||
possible to be used instead of GMP 4.1.4. But latest GMP 4.2.2 needs more
|
||||
testing before setting the default requirement for building jbigi.jar.</p>
|
||||
|
||||
@@ -47,7 +47,7 @@ report.</li>
|
||||
<li>Copy <code>libjbigi.so</code> to your i2p directory</li>
|
||||
<li>Restart your I2P programs.</li>
|
||||
<li>On
|
||||
<a href="http://localhost:7655/routerStats.html">http://localhost:7655/routerStats.html</a>
|
||||
<a href="http://localhost:7657/oldstats.jsp">http://localhost:7657/oldstats.jsp</a>
|
||||
the <code>crypto.elGamal.decrypt</code> and <code>crypto.elGamal.encrypt</code>
|
||||
should be a lot faster.</li>
|
||||
</ol>
|
||||
|
@@ -252,12 +252,12 @@ must be trusted by the release managers (currently Complication and zzz).
|
||||
In addition, they must explicitly agree with the above terms to be trusted.
|
||||
That means that they must send one of the release managers a signed message affirming that:</p>
|
||||
<ul>
|
||||
<li>Unless marked otherwise, all code they commit is implicitly licensed under
|
||||
<li>Unless marked otherwise, all code I commit is implicitly licensed under
|
||||
the component's primary license</li>
|
||||
<li>If specified in the source, the code may be explicitly licensed under one
|
||||
of the component's alternate licenses</li>
|
||||
<li>They have the right to release the code they commit under the terms they
|
||||
are committing it</li>
|
||||
<li>I have the right to release the code they commit under the terms I
|
||||
am committing it</li>
|
||||
</ul>
|
||||
|
||||
<p>If anyone is aware of any instances where the above conditions are not met,
|
||||
|
@@ -2,7 +2,7 @@
|
||||
{% block title %}Old Tunnel Implementation{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<b>Note: Obsolete - NOT used! see <a href="tunnel-alt.html">tunnel-alt.html</a> for the new implementation</b>
|
||||
<b>Note: Obsolete - NOT used! Replaced in 0.6.1.10 - see <a href="tunnel-alt.html">tunnel-alt.html</a> for the new implementation</b>
|
||||
<br>
|
||||
<code>$Id: tunnel.html,v 1.10 2005/01/16 01:07:07 jrandom Exp $</code>
|
||||
<pre>
|
||||
|
Reference in New Issue
Block a user