diff --git a/www.i2p2/pages/jbigi.html b/www.i2p2/pages/jbigi.html index 77591836..84d50781 100644 --- a/www.i2p2/pages/jbigi.html +++ b/www.i2p2/pages/jbigi.html @@ -22,10 +22,10 @@ testing before setting the default requirement for building jbigi.jar.

Step-by-step instructions

    -
  1. Look on http://localhost:7655/routerStats.html +
  2. Look on http://localhost:7657/oldstats.jsp to see what the values for crypto.elGamal.decrypt and -crypto.elGamal.encrypt are. Copy this somewhere so you can compare -it later on.
  3. +crypto.elGamal.encrypt are. The numbers are times in milliseconds. Copy these somewhere so you can compare +them later on.
  4. Get the latest sourcecode of I2P out of the monotone database mtn.i2p2.de
  5. Inside the source tree change directory to: core/c
  6. Take a look at build.sh, if your JAVA_HOME diff --git a/www.i2p2/pages/license-agreements.html b/www.i2p2/pages/license-agreements.html new file mode 100644 index 00000000..746cf6b8 --- /dev/null +++ b/www.i2p2/pages/license-agreements.html @@ -0,0 +1,57 @@ +{% extends "_layout.html" %} +{% block title %}License Agreements{% endblock %} +{% block content %} + +

    For more information see licenses.html. +

    +
    +Complication:
    +
    +-----BEGIN PGP SIGNED MESSAGE-----
    +Hash: SHA1
    +
    +Applicable to the code I contribute to the I2P project,
    +I hereby state that:
    +
    +* Unless marked otherwise, all code I commit
    +is implicitly licensed under the component's primary license
    +
    +* If specified in the source, the code may be explicitly licensed
    +under one of the component's alternate licenses
    +
    +* I have the right to release the code I commit
    +under the terms I am committing it
    +-----BEGIN PGP SIGNATURE-----
    +Version: GnuPG v1.4.6 (GNU/Linux)
    +
    +iD8DBQFHyXwu+h38a3n8zjMRAjeSAJ9MFx/ENbUu8+3/U7KTj+FGL/NkHQCdE38G
    +IWV1Gaqcis9sFEW7Nh0hY+c=
    +=WPeP
    +-----END PGP SIGNATURE-----
    +
    +
    +zzz:
    +
    +-----BEGIN PGP SIGNED MESSAGE-----
    +Hash: SHA1
    +
    +I affirm that:
    +
    +     * Unless marked otherwise, all code I commit is implicitly licensed under the component's primary license
    +     * If specified in the source, the code may be explicitly licensed under one of the component's alternate licenses
    +     * I have the right to release the code I commit under the terms I am committing it
    +
    +-----BEGIN PGP SIGNATURE-----
    +Version: GnuPG v1.4.6 (GNU/Linux)
    +
    +iD8DBQFHyaYXQVV2uqduC+0RAhn4AJ40JO/ep1JhmghjPU/IeISIa2fY8ACgiuV0
    +vOCHNLZ8kiXKc8cTzYHGnU0=
    +=ZzDd
    +-----END PGP SIGNATURE-----
    +
    +welterde:
    +Received by zzz 2008-02-16, need to put clearsigned version here.
    +
    +
    +
    +{% endblock %} diff --git a/www.i2p2/pages/licenses.html b/www.i2p2/pages/licenses.html index f8a851c0..ae600c5d 100644 --- a/www.i2p2/pages/licenses.html +++ b/www.i2p2/pages/licenses.html @@ -262,5 +262,7 @@ That means that they must send one of the release managers a signed message affi

    If anyone is aware of any instances where the above conditions are not met, please contact the component lead and/or an I2P release manager with further -information.

    +information. +See developers' license agreements. +

    {% endblock %} diff --git a/www.i2p2/pages/ntcp.html b/www.i2p2/pages/ntcp.html index d6fc111b..1e707eca 100644 --- a/www.i2p2/pages/ntcp.html +++ b/www.i2p2/pages/ntcp.html @@ -647,7 +647,8 @@ Priority sending for SSU was implemented by zzz but was never checked in The advanced transport bid control i2np.udp.preferred was implemented in 0.6.1.29.
  7. -Pushback for NTCP was implemented in 0.6.1.30 +Pushback for NTCP was implemented in 0.6.1.30, disabled in 0.6.1.31 due to anonymity concerns, +and reenabled with improvements to address those concerns in 0.6.1.32.
  8. None of zzz's proposals 1-5 have been implemented. diff --git a/www.i2p2/pages/todo.html b/www.i2p2/pages/todo.html index b09a9904..5d21d6dd 100644 --- a/www.i2p2/pages/todo.html +++ b/www.i2p2/pages/todo.html @@ -217,7 +217,8 @@ samples when dealing with longer tunnels.

  9. Strict ordering of participants within tunnels

    As Connelly proposed -to deal with the predecessor attack, +to deal with the predecessor attack +(2008 update), keeping the order of peers within our tunnels consistent (aka whenever Alice creates a tunnel with both Bob and Charlie in it, Bob's next hop is always Charlie), we address the issue as Bob doesn't get to substantially sample Alice's peer selection group. We may even want