forked from I2P_Developers/i2p.www
149 lines
11 KiB
HTML
149 lines
11 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}Pages/meeting144.html{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, August 23, 2005</h2>
|
|
<div class="irclog">
|
|
<p>12:01 < jrandom> 0) hi</p>
|
|
<p>12:01 < jrandom> 1) 0.6.0.3 status</p>
|
|
<p>12:01 < jrandom> 2) IRC status</p>
|
|
<p>12:01 < jrandom> 3) susibt</p>
|
|
<p>12:01 < jrandom> 4) Syndie</p>
|
|
<p>12:01 < jrandom> 5) ???</p>
|
|
<p>12:01 < jrandom> 0) hi</p>
|
|
<p>12:01 * jrandom waves</p>
|
|
<p>12:01 < lucky> hi</p>
|
|
<p>12:02 < jrandom> weekly status notes up @ http://dev.i2p.net/pipermail/i2p/2005-August/000857.html</p>
|
|
<p>12:02 < lucky> hihihihi</p>
|
|
<p>12:02 < jrandom> hi lucky </p>
|
|
<p>12:02 < jrandom> ok, jumping into 1) 0.6.0.3 status</p>
|
|
<p>12:02 < jrandom> i think the biggest things worth mentioning wrt 0.6.0.3 are in the status notes, but beyond that, anyone have anything to bring up?</p>
|
|
<p>12:04 < gott> What's the deal with 'Unknown' ?</p>
|
|
<p>12:04 < jrandom> i'm not sure whether the ssu cwin improvements will come in 0.6.0.4 or will wait until 0.6.1 when we have better peer / configuration</p>
|
|
<p>12:04 < jrandom> gott: there are two paragraphs in the email related to that - do you have any specific questions beyond those?</p>
|
|
<p>12:05 < jrandom> or is there some point i could clarify?</p>
|
|
<p>12:05 < gott> No, I just haven't read the bloody email.</p>
|
|
<p>12:05 < jrandom> heh</p>
|
|
<p>12:05 < jrandom> well, scroll up five lines and read the bloody email ;)</p>
|
|
<p>12:06 < jrandom> ok, anyone else have any questions on 0.6.0.3?</p>
|
|
<p>12:07 < jrandom> if not, moving on to 2) IRC status</p>
|
|
<p>12:07 < modulus> sorry guys, but need to leave. later all.</p>
|
|
<p>12:08 < jrandom> beyond whats in the mail, postman/cervantes/arcturus: y'all have anything you want to bring up?</p>
|
|
<p>12:08 < jrandom> l8r modulus</p>
|
|
<p>12:08 <+arcturus> on 1)?</p>
|
|
<p>12:08 <+arcturus> oh sorry</p>
|
|
<p>12:08 < gott> Hmm.</p>
|
|
<p>12:08 <+arcturus> 2) it is now</p>
|
|
<p>12:09 < gott> How much upstream bandwidth does IRC over i2p usually take at the moment ?</p>
|
|
<p>12:09 <+arcturus> netsplits are history</p>
|
|
<p>12:09 <+arcturus> gott: i coudln't say that without compromising my router's anonymity</p>
|
|
<p>12:09 < gott> No, no, no.</p>
|
|
<p>12:10 < jrandom> not sure, my router with squid.i2p/dev.i2p/cvs.i2p/www.cvs/syndiemedia.i2p plus my irc and eepproxy uses on average 10-20KBps</p>
|
|
<p>12:10 < gott> Does it require a commercial line ?</p>
|
|
<p>12:10 < jrandom> nice1 arcturus</p>
|
|
<p>12:10 < gott> jrandom: I mean to say, to host.</p>
|
|
<p>12:10 < jrandom> gott: to operate a server or a client?</p>
|
|
<p>12:10 < jrandom> ah</p>
|
|
<p>12:10 <+arcturus> gott: i couldn't say that without compromising my router's anonymity</p>
|
|
<p>12:10 < gott> server.</p>
|
|
<p>12:10 * jrandom knows not. probably less when you have just one ircd</p>
|
|
<p>12:10 < gott> So are you running a modified unrealircd ?</p>
|
|
<p>12:11 < jrandom> say, add a factor of 1.3 to the client usage for a single server</p>
|
|
<p>12:11 <+arcturus> i'd like to also add that inter-server lag is steady and very very low</p>
|
|
<p>12:11 < gott> I assume you are, since there doesn't seem to be a VERSION command</p>
|
|
<p>12:11 <+arcturus> i disabled version</p>
|
|
<p>12:12 < gott> Are your modifications open-source ?</p>
|
|
<p>12:12 <+arcturus> maybe we're running unreal, maybe we aren't :)</p>
|
|
<p>12:12 < gott> You should put them up so others can start their own private networks.</p>
|
|
<p>12:12 <+arcturus> i can't tell you without compromising security</p>
|
|
<p>12:12 < gott> security through obscurity, sweet.</p>
|
|
<p>12:12 < jrandom> word arcturus. i'm seeing something like 0-2s lag on average (at the moment, less than irssi's lag detector)</p>
|
|
<p>12:12 <+arcturus> no, it's only one layer of security</p>
|
|
<p>12:13 <+arcturus> and it only serves as a deterrent, no substitute for technical security measures</p>
|
|
<p>12:15 < jrandom> arcturus: how goes with vanguard?</p>
|
|
<p>12:15 <+arcturus> i haven't coded on it lately, other projects have been occupying me, but there's a constant, steady pressure i feel to get around to finishing it :)</p>
|
|
<p>12:16 < jrandom> heh coo'</p>
|
|
<p>12:16 <+arcturus> vanguard will be most effective against bots, the hashcash measure is a separate deal</p>
|
|
<p>12:16 <+arcturus> i'm concerned about hashcash now though</p>
|
|
<p>12:17 <+arcturus> with the latest attacks against sha-1</p>
|
|
<p>12:17 <+arcturus> it won't be long before there are tools available to the masses</p>
|
|
<p>12:17 <+arcturus> unfortunately the standard hashcash implementation is based entirely on sha-1</p>
|
|
<p>12:17 < susi23_> Unable to find a javac compiler; // com.sun.tools.javac.Main is not on the classpath. // Perhaps JAVA_HOME does not point to the JDK</p>
|
|
<p>12:18 <@cervantes> ah made it</p>
|
|
<p>12:18 < susi23_> any ideas about this? JAVA_HOME points definitely to the right dir, javac is in PATH and callable</p>
|
|
<p>12:18 <+arcturus> susi23_: we're in a meeting atm :)</p>
|
|
<p>12:18 < jrandom> susi23_: OOM?</p>
|
|
<p>12:18 < susi23_> meeting? though its 8pm?</p>
|
|
<p>12:18 < jrandom> (precompile your jsps rather than letting jetty/tomcat do it, its faster ;)</p>
|
|
<p>12:19 < jrandom> yeah we moved it susi23_ :)</p>
|
|
<p>12:19 < susi23_> didn't know, sorry</p>
|
|
<p>12:19 < jrandom> hehe np, glad you made it for the meeting, your agenda item is up next ;)</p>
|
|
<p>12:20 * susi23_ sits down and listens</p>
|
|
<p>12:20 <+arcturus> so while i don't expect immediate problems with hashcash, i think it's feasible sha-1 could be seriously compromised soon</p>
|
|
<p>12:21 < jrandom> arcturus: hashcash with md5 would probably be fine</p>
|
|
<p>12:21 < jrandom> its just a PoW</p>
|
|
<p>12:21 <+arcturus> if anyone knows of any hashcash implementations based on sha256 or higher please met me know</p>
|
|
<p>12:21 <+arcturus> well PoW is pointless if there's little P in it :)</p>
|
|
<p>12:21 < jrandom> the size of the hash only matters when your hashcash reaches the size of the hash</p>
|
|
<p>12:23 < jrandom> (but, yeah, running against a truncated sha256 or 512 or whirlpool or whatever would be neat)</p>
|
|
<p>12:23 <+arcturus> i guess we could go ahead with the current implementation, perhaps we can design it so that we can swap it out easily later when we need to</p>
|
|
<p>12:24 < jrandom> (DTSTTCPW)</p>
|
|
<p>12:25 <+arcturus> because we will eventually need to drop sha-1, i'm sure of it :) and if we can't be reasonably certain a token was generated properly there's no reason to even be using hashcash</p>
|
|
<p>12:25 < jrandom> (its only for a PoW to get a nym on irc, not to get access to fort knox ;)</p>
|
|
<p>12:26 <@cervantes> there's some talk on the hashcash mailing list about implementing sha256</p>
|
|
<p>12:26 <+arcturus> it's not for a nym, it's for entry to the server</p>
|
|
<p>12:26 <+arcturus> cervantes: cool i'll check that</p>
|
|
<p>12:27 <+arcturus> jrandom: and it's not just PoW, the hashcash is what gives us a method to uniquely identify clients on the network, akin to being able to identify by IP, so that we can ban with precision</p>
|
|
<p>12:28 < jrandom> certainly those are renewed over time though, right?</p>
|
|
<p>12:28 < jrandom> e.g. a new PoW cert every 6 months (or 6h, or whatever)</p>
|
|
<p>12:28 <+arcturus> if a user doen't have to do any work to get their ID, that nullifies our ability to ban them</p>
|
|
<p>12:29 <+arcturus> i don't know of any reason to expire them automatically, only expire them manually if they violate terms of service</p>
|
|
<p>12:29 <+arcturus> no need to make people do unnecessary work for new IDs</p>
|
|
<p>12:29 < jrandom> eh, its just a passive PoW, they can run one cycle every 6 hours to regenerate a new one</p>
|
|
<p>12:29 < jrandom> but perhaps DTSTTCPW</p>
|
|
<p>12:30 <+arcturus> any hashcash genereated must be used within 24 hours or it is invalid</p>
|
|
<p>12:32 <@cervantes> just to reiterate the new server irc.freshcoffee.i2p needs to be added into your i2ptunnel console</p>
|
|
<p>12:32 < jrandom> coo'. ok, anything else for 2) irc2p?</p>
|
|
<p>12:33 <@cervantes> (http://forum.i2p/viewtopic.php?t=911</p>
|
|
<p>12:33 <@cervantes> )</p>
|
|
<p>12:33 <@cervantes> <-- done</p>
|
|
<p>12:34 <+arcturus> i don't have anything else to bore you all with :)</p>
|
|
<p>12:34 < jrandom> hehe</p>
|
|
<p>12:34 < jrandom> ok, 3) susibt</p>
|
|
<p>12:34 < ardvark> um, when I add the new server to my tunnel, do I have to restart i2p?</p>
|
|
<p>12:34 < jrandom> susi23_: p1ng</p>
|
|
<p>12:35 <@cervantes> ardvark: just the tunnel</p>
|
|
<p>12:35 <@cervantes> (ircproxy tunnel)</p>
|
|
<p>12:35 < ardvark> oh ok, I just added and saved, so that is not enuff then</p>
|
|
<p>12:36 < jrandom> right, unfortunately you need to stop and start that proxy</p>
|
|
<p>12:36 < susi23_> well</p>
|
|
<p>12:36 < ardvark> but i'll miss the meeting then ;)</p>
|
|
<p>12:37 < susi23_> susibt is a webapp (like susimail) to drop into your routers VM</p>
|
|
<p>12:37 < susi23_> it acts as a web frontend for i2p-bt</p>
|
|
<p>12:38 < susi23_> so you can manage your seeds, up- and download files etc.</p>
|
|
<p>12:38 < jrandom> w00t</p>
|
|
<p>12:39 < susi23_> the prob is, you need to start a btdownloadheadless.py for each seed... so you get lot of python processes to your many java threads :)</p>
|
|
<p>12:39 <+arcturus> that will be addressed in ducktorrent *cough*</p>
|
|
<p>12:39 < jrandom> heh</p>
|
|
<p>12:39 * jrandom holds breath</p>
|
|
<p>12:40 < susi23_> it even supports restart of seeds after router restart</p>
|
|
<p>12:40 <@cervantes> nice</p>
|
|
<p>12:40 < jrandom> wikked</p>
|
|
<p>12:40 < susi23_> future plans are automatic build of torrents and ui improvement</p>
|
|
<p>12:41 < susi23_> if you want to try it out, I recommend a separate jetty instance</p>
|
|
<p>12:41 < susi23_> so you don't have to fiddle with your router :)</p>
|
|
<p>12:41 < susi23_> download and installation instructions on http://susi.i2p</p>
|
|
<p>12:42 < susi23_> thats all *ping back to jr*</p>
|
|
<p>12:42 < jrandom> w3wt, gracias susi</p>
|
|
<p>12:42 < jrandom> ok, anyone have any questions & comments on that, or shall we jump on over to 4) syndie?</p>
|
|
<p>12:44 < jrandom> ok regarding syndi, i've posted a bunch to the list about it over the last day or two, and there'll be lots more activity</p>
|
|
<p>12:45 < jrandom> the main demo site for syndie is http://syndiemedia.i2p / http://66.111.51.110:8000/, but of course people are encouraged to download it and install it locally</p>
|
|
<p>12:45 < jrandom> i dont have too much to add at the moment on that frnt. unless anyone has any questions?</p>
|
|
<p>12:46 < gott> Why is it called syndie ?</p>
|
|
<p>12:46 < gott> is it a reference to 'syndicate' ?</p>
|
|
<p>12:47 < jrandom> yeah, its a generic syndication frontend (+ security, authentication, and anonymity awareness)</p>
|
|
<p>12:48 < jrandom> ok, if there's nothing else on 4), lets jump on over to 5) ???</p>
|
|
<p>12:48 < jrandom> anyone have anythin i2p related to bring up for the meeting?</p>
|
|
<p>12:51 < jrandom> ok, if there's nothing else</p>
|
|
<p>12:51 * jrandom winds up</p>
|
|
<p>12:52 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |