headers
jrandom | 10 Oct 2006 16:09

weekly status notes [oct 10]


Hi y'all, brief status notes this week

* Index
1) 0.6.1.26 and network status
2) Syndie development status
3) Distributed version control revisited
4) ???

* 1) 0.6.1.26 and network status

The other day we pushed out a new 0.6.1.26 release, including lots
of i2psnark improvements from zzz and some new NTP safety checks
from Complication, and reports have been positive.  The network
seems to be growing slightly with no new odd effects, though some
people still have trouble building their tunnels (as has always
been the case).

* 2) Syndie development status

More and more improvements have been coming down the line, with
the current alpha version sitting at 0.910a.  The feature list
for 1.0 is pretty much met, so right now its largely bugfixing
and documentation.  Swing on by #i2p if you want to help test :)

Also, there have been some discussions on the channel for designs
of the Syndie GUI - meerboop has come up with some cool ideas, and
is working on docing them up.  The Syndie GUI is the main component
of the Syndie 2.0 release, so the sooner we get that rolling, the
sooner we take over the worl^W^W^W^W can push Syndie out on the
(Continue reading)

Permalink | Reply | 0 comments |
headers
jrandom | 9 Oct 2006 02:08

0.6.1.26 is available


hi y'all, we've got a new 0.6.1.26 release ready for your enjoyment!
In it are Complication's new NTP clock skew protection code plus a
ton of zzz's i2psnark fixes and improvements.  The release is backwards
compatible, so swing on by and update at your earliest convenience -
the full list of changes is up at
http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD

Upgrading and installation is the same as always, or you can see
http://www.i2p.net/download for details

Thanks zzz and Complication for your work, and all y'all for your help!

=jr
Permalink | Reply | 0 comments |
headers
jrandom | 4 Oct 2006 16:29

weekly status notes [oct 3]


Hi y'all, a belated status notes this week

* Index
1) Net status
2) Router dev status
3) Syndie rationale continued
4) Syndie dev status
5) Distributed version control
6) ???

* 1) Net status

The past week or two have been fairly stable on irc and other
services, though dev.i2p/squid.i2p/www.i2p/cvs.i2p had a few bumps
(due to temporary OS-related issues).  Things seem to be at a
steady state at the moment.

* 2) Router dev status

The flip side to the Syndie discussion is "so, what does that mean
for the router?", and to answer that, let me explain a bit where the
router development stands right now.

On the whole, the thing holding the router back from 1.0 is in my
view its performance, not its anonymity properties.  Certainly, there
are anonymity issues to improve, but while we do get pretty good
performance for an anonymous network, our performance is not
sufficient for wider use.  In addition, improvements to the anonymity
of the network will not improve its performance (in most instances I
(Continue reading)

Permalink | Reply | 2 comments |
headers
jrandom | 14 Sep 2006 19:27

syndie comment reply


Hi y'all, I got some private email regarding the Syndie stuff, but I
think it'd be helpful to document the answers out in the open.  Lines
quoted with "> >" are me, and lines quoted with "> " are the author who
sent me the email.

> > though some posts can be trivialy decrypted by the public at large,
>
> I wondered which method you were envisioning for supplying the key.
> Publish it somewhere in plaintext post metadata (is there such a thing)?

Exactly

> Or encrypt "public secrets" with a key obtained from a blank/default
> passphrase? From what I gathered, I thought you were meaning the former
> (supply key with post) but I wasn't totally sure.
> I wonder if a scenario would exist for which different approaches
> to this question would have different implications?

Well, there'll be support for password-based encryption, and using ""
as a passphrase will of course be supported.  So, I guess this means
that the Syndie file format/spec will handle either, though the
implementation I'm hacking on will use the former when someone picks the
option to make something readable by anyone.

> > while others can be only be read by authorized readers,
>
> Would this approach amount to the poster specifying
> "encrypt post for decryption by Foo, Bar and Moo"?
> Since it wasn't quite explicitly said so, I wondered
(Continue reading)

Permalink | Reply | 0 comments |
headers
jrandom | 12 Sep 2006 13:18

weekly status notes [sep 12]


Hi y'all, here's our *cough* weekly status notes

* Index:
1) 0.6.1.25 and net status
2) I2PSnark
3) Syndie (what/why/when)
4) Syndie crypto questions
5) ???

* 1) 0.6.1.25 and net status

The other day we pushed out the 0.6.1.25 release, including the swarm of
bugfixes accumulated over the past month, as well as zzz's work on
I2PSnark and Complication's work trying to make our time synchronization
code a bit more robust.  Right now the network seems to be fairly stable,
though IRC has been a bit rough in the last few days (due to reasons
unrelated to I2P).  With perhaps half of the network upgraded to the
latest release, tunnel build success rates have not changed much, though
overall throughput seems to have increased (likely due to an increase in
the number of people using I2PSnark).

* 2) I2PSnark

zzz's updates to I2PSnark included protocol optimizations as well as web
interfaces changes, as described in the history log [1].  There have been
a few small updates for I2PSnark since the 0.6.1.25 release as well, and
perhaps zzz can give us an overview of whats up on during the meeting
tonight.
(Continue reading)

Permalink | Reply | 8 comments |
headers
jrandom | 9 Sep 2006 18:09

0.6.1.25 is available


Hi y'all, we've got a new 0.6.1.25 release ready for your
enjoyment, stuffed with zzz's great work improving i2psnark,
Complication's SusiDNS and NTP fixes, and a spattering of
bug fixes and configuration adjustments.  The release is
backwards compatible, and upgrading is highly recommended.
As always, the full list of changes is up at
http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD

Two of the configuration adjustments are worth brief mention
here - I've disabled the dynamic router keys code (which would
change your router identity every time you restart the router),
as the benefits visible are negligible and the drawbacks
aparent.  In the future it may be revisited, but for now it
doesn't help.

Another change is to disable the tunnel load testing, which
basically floods tunnels at self-tuning rates with the intent
of getting more precise local speed profiles.  At the moment,
we're relying more substantially on the published peer tiers,
so for the moment, this artificial load isn't helping.  Down
the line it may be reenabled, but we'll cross that bridge when
we reach it.

Installation and update instructions for this release are up  <at> 
http://www.i2p.net/download

As an aside, we'll be having our dev meeting this coming tuesday
as well, with updates on whats going on.
(Continue reading)

Permalink | Reply | 0 comments |
headers
paul wang | 24 Aug 2006 19:26
Picon
Favicon

postinstall.sh do nothign

hi

I'm just trying i2p.
after installing jikes-1.22 and kaffe-1.1.7,
I try "bash postinstall.sh", but noting happens.
I've checked "ps -ax" and nothing was running.
there is no message of any kind except
"Starting I2P service..."
but I'm sure nothing is running.

I thought java code was good at throwing exceptions, when something didn't start right...



Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. 
_______________________________________________
i2p mailing list
i2p@...
http://dev.i2p.net/mailman/listinfo/i2p
Permalink | Reply | 0 comments |
headers
jrandom | 1 Aug 2006 21:41

weekly status notes [aug 1]

Hi y'all, time for a brief set of notes before tonight's meeting.
I realize that you may have a variety of questions or issues to
bring up, so we'll go in a more fluid format than usual.  There
are just a few things I want to mention first.

* Network status

It seems the network is doing pretty well, with swarms of fairly
large I2PSnark transfers completing, and with quite sustantial
transfer rates achieved on individual routers - I've seen
650KBytes/sec and 17,000 participating tunnels without any
fireworks.  Routers on the low end of the spectrum seem to be
doing fine too, browsing eepsites and irc with 2 hop tunnels
using under 1KByte/sec average.

It isn't all roses for everyone though, but we're working through
updating the router's behavior so as to allow more consistent and
usable performance.

* NTCP

The new NTCP transport ("new" tcp) is doing quite well after
clearing up the initial bumps and bruises.  To answer a frequent
question, in the long run, both NTCP and SSU will be in operation -
we are not reverting to TCP-only.

* Eepsite reachability

Remember folks that eepsites are reachable only when the person
who is running it has it up - if they're down, there's nothing
you can do to reach it ;)  Unfortunately, for the past few days,
orion.i2p hasn't been reachable, but the net is definitely still
working - perhaps swing by inproxy.tino.i2p or eepsites.i2p for
your network survey needs.

Anyway, there's lots more going on, but it'd be a bit premature
to mention it here.  Of course, if you have any questions or
concerns, swing on by #i2p in a few minutes for our *cough* weekly
development meeting.

Thanks for your help moving us forward!
=jr
Permalink | Reply | 0 comments |
headers
jrandom | 29 Jul 2006 18:27

0.6.1.24 is available


Hi y'all, back again with a new 0.6.1.24 release fixing a hefty
bug some have been experiencing with 0.6.1.23 - thanks cervantes,
frosk, postman, Complication, et al!  The release is backwards
compatible, and upgrading is highly recommended.  As always, the
full list of changes is up at
http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD

Installation and update instructions can be found on
http://www.i2p.net/download

Thanks!
=jr
Permalink | Reply | 0 comments |
headers
jrandom | 28 Jul 2006 04:04

0.6.1.23 is available


Hi y'all, now that I've finally got net access again, we'll
hopefully be putting public releases out a bit more frequently
again.  Today's 0.6.1.23 release fixes a bunch of bugs found
in the new NTCP transport, cleans up the shitlist and netDb
behavior even further, and adds some infrastructure to
help track the router identity proliferation.  The release is
backwards compatible and should be fairly safe, so please upgrade
at your earliest convenience.  As always, the list of changes is up
at http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD

For update or installation instructions, see
http://www.i2p.net/download

Thanks for your help moving us forward!
=jr
Permalink | Reply | 1 comment |
headers
jrandom | 18 Jul 2006 18:00

0.6.1.22 is available


Hi y'all, after a month of hacking, we've got a new 0.6.1.22
release ready for your enjoyment.  In it are new TCP transports,
a slew of bugfixes (including that reseed-inspiring bug), the
use of peers with 16-32KBps limits in the default configuration,
among other things.  Reports on the net have been generally
positive as these changes have been rolled out, so we hope to
continue that trend along.

The new TCP transport ("NTCP") is enabled for outbound connections
by default, falling back on the UDP transport ("SSU") if the other
side cannot receive connections for some reason.  You can however
enable inbound NTCP connections by poking a hole in your NAT and/or
firewall and configuring the router according to
http://localhost:7657/config.jsp - though *only* do that if you
really know what you're doing.  You don't have to enable inbound
NTCP connections, and it doesn't hurt not enabling it, so don't do
it until you've read all of the text there and know what it means :)

Anyway, as always, the full list of changes is up at
http://dev.i2p.net/cgi-bin/cvsweb.cgi/history.txt?rev=HEAD
and the upgrade/installation instructions can be found at
http://www.i2p.net/download

Thanks for your patience, and lets see how this goes
=jr
Permalink | Reply | 0 comments |

Gmane