<p>13:06 < jrandom> weekly status notes up @ http://dev.i2p.net/pipermail/i2p/2005-February/000564.html</p>
<p>13:07 < cervantes> sorry I'm late...I was busy reading the status notes that were posted at the last minute...</p>
<p>13:07 < jrandom> hey, this week they were /before/ the meeting at least (by 30s or so ;)</p>
<p>13:08 < jrandom> anyway, while you dig through that oh so exciting email, lets jump on into 1) 0.4.2.6-*</p>
<p>13:09 < jrandom> with the latest patches from anon et al, i'm torn between pushing out a new 0.4.2.7 so close to the 0.5 rev. </p>
<p>13:10 < jrandom> for the moment though, if you're feeling brave, feel free to give cvs a whirl - its stable (i'm breaking things off on another branch), and has some good stuff</p>
<p>13:11 < jrandom> the deciding factor for not pushing a rev out was when i did a checklist for 0.5 and found that the only things left were really web interface updates</p>
<p>13:11 <+Ragnarok> about the patches from sugadude, they do represent a policy change, as we discussed filtering out non .i2p addresses before, and you decided against it</p>
<p>13:11 < jrandom> oh, hrm? i disagree with my old self then - eepproxy doesn't accept non-.i2p address in any case, even if they were in hosts.txt</p>
<p>13:12 < jrandom> did i have a convincing argument before?</p>
<p>13:13 <+Ragnarok> ok, then can we revert the patch, and I can implement it the way it originally worked, which is a 0 line change?</p>
<p>13:13 <+Ragnarok> not really, I just didn't care either way :)</p>
<p>13:13 < jrandom> oh, cool you're the boss</p>
<p>13:13 < cervantes> well you convinced me to drop all my work on a multi-tld management system and fire all my employees</p>
<p>13:13 <+Ragnarok> filtering is already happening, so it's just adding a condition to an if statement</p>
<p>13:14 < jrandom> cervantes: there's also this beautiful bridge i've got for sale...</p>
<p>13:14 < cervantes> :)</p>
<p>13:14 < jrandom> ok word Ragnarok, if you want to send me a .java/.tar/.diff/.whatever, that'd be great</p>
<p>13:15 <+Ragnarok> I can do cvs now :)</p>
<p>13:16 <+Ragnarok> ... just kidding :)</p>
<p>13:17 < jrandom> ok, other than that, anyone have anything else to bring up wrt 0.4.*?</p>
<p>13:17 < ant><dm>gt; 0.4.* sucks, give us 0.5</p>
<p>13:17 < ant><dm>gt; It's like a gazillion years old!!</p>
<p>13:18 < ant><fvw>gt; 0.4.* doesn't suck, give us 0.5 anyway.</p>
<p>13:18 < jrandom> 2) 0.5 it is then :)</p>
<p>13:19 < ant><dm>gt; you guys owe me big time, I brought 0.5</p>
<p>13:19 < jrandom> we couldn't'a done it without ya dm </p>
<p>13:19 < ant><dm>gt; amen</p>
<p>13:20 < jrandom> as mentioned in the notes, pretty much all the heavy lifting for 0.5 is done and tested, but there are still the odds and ends left to fix up</p>
<p>13:21 < jrandom> (e.g. the next task on my list is a tunnel config page to manage the pools and settings)</p>
<p>13:22 <@duck> I hope we will have a test-0.5 network before releasing?</p>
<p>13:22 < jrandom> there have been updates to lots of different components though, so 0.5 might be a bit bumpy</p>
<p>13:22 < ant><dm>gt; jrandom HAS a test network already.. duh</p>
<p>13:23 < jrandom> aye, i've been doing one locally here with a dozen routers, but in the next day or two i'll try to snag some people to help with some wide area tests</p>
<p>13:24 < jrandom> wikked. perhaps we can try something out tomorrow, try to break some things. </p>
<p>13:26 < cervantes> as can I</p>
<p>13:27 < jrandom> word</p>
<p>13:27 < jrandom> thats about all i have to say about the upcoming 0.5 at the moment - the cvs commit logs have been pretty verbose, so if you want the nitty gritty, hit 'em up</p>
<p>13:28 < jrandom> anyone else have any comments/questions/concerns/frisbees wrt 0.5?</p>
<p>13:43 < smeghead> i move we schedule the licensing issue for the next meeting of the I2P Public Domain Security Council</p>
<p>13:43 < modulus> ah, that one</p>
<p>13:43 < modulus> misheard.</p>
<p>13:45 <@duck> 3.9.0 looks hot</p>
<p>13:45 <@duck> it is still beta though</p>
<p>13:47 <@duck> ok, those willing to help, please let me know</p>
<p>13:47 <@duck> so we can look into using 3.9.x</p>
<p>13:47 <@duck> .</p>
<p>13:47 < jrandom> w3rd</p>
<p>13:47 < smeghead> i'm willing to help out</p>
<p>13:47 < jrandom> i'm willing to help test</p>
<p>13:48 <+Ragnarok> I'm willing, but there are likely to be time constraints, as I am currently having the semester from hell.</p>
<p>13:48 < jrandom> d'oh</p>
<p>13:48 <@duck> drop out</p>
<p>13:48 < jrandom> damn, duck beat me</p>
<p>13:48 < smeghead> yes, everyone does it</p>
<p>13:49 <+Ragnarok> boo</p>
<p>13:49 < ant><jnymo>gt; just join the military ;)</p>
<p>13:50 < jrandom> yeah, as that'll give you lots of time to code, 'eh? ;)</p>
<p>13:50 <+Ragnarok> I've already given up on being a math major, that's as much as you're getting from me :)</p>
<p>13:50 < jrandom> heh</p>
<p>13:50 < jrandom> ok, anyone else have anything on 3) i2p-bt? </p>
<p>13:51 < ant><jnymo>gt; just don't sign up for six years</p>
<p>13:51 <@duck> quite a bit of forum posts on it</p>
<p>13:51 <@duck> thanks to those who aid the newbies</p>
<p>13:51 <@duck> s/thanks/my thanks/</p>
<p>13:51 <@duck> if you have stuff for a FAQ, lemme kno</p>
<p>13:52 < jrandom> (if we still had drupal, we could just add a new node...)</p>
<p>13:53 < jrandom> ok, anyway, moving on to 4) fortuna</p>
<p>13:54 < jrandom> smeghead: wanna give us an update on things?</p>
<p>13:54 < smeghead> yes, i'm working on pants and fortuna in tandem</p>
<p>13:55 < smeghead> since i needed to modify fortuna's build to turn it into a pbuild</p>
<p>13:55 < smeghead> eta on a patch that will let you test fortuna is a day or two, maybe tonight depending on what drugs are involved</p>
<p>13:56 < jrandom> heh</p>
<p>13:56 <@duck> so you'll get your pants down?</p>
<p>13:56 < jrandom> ok, cool, whenever is fine - if we get it in for 0.5 in the next week or so, thats great, if not, thats great too</p>
<p>13:56 < smeghead> well even if i finish it tonight, i would take a conservative stance on deployment</p>
<p>13:57 < jrandom> reasonable enough</p>
<p>13:57 < smeghead> until we get some decent testing in</p>
<p>13:57 < smeghead> since this will be at the heart of most of i2p's crypto</p>
<p>13:57 < jrandom> aye</p>
<p>13:57 < ant><jnymo>gt; will jbigi stay?</p>
<p>13:57 < smeghead> your new entropy class is cool</p>
<p>13:58 < jrandom> yeah jnymo, this is just a random # generator</p>
<p>13:58 < ant><jnymo>gt; ah</p>
<p>13:59 < jrandom> we'll still need to do some research into the quality of various entropy sources in the router, but I think we'll be able to feed it some data.</p>
<p>14:00 < smeghead> btw if anyone wants to read what this pants thing is about: http://smeghead.i2p/README_pants</p>
<p>14:00 < jrandom> oh wikked</p>
<p>14:01 < smeghead> pants is almost done too</p>
<p>14:01 < brachtus> i know jbigi is kinda hard to get working with OS X/Darwin... will this have the same build problems?</p>
<p>14:01 < smeghead> what is the issue on osx?</p>
<p>14:01 < modulus> it's just you have to build the lib</p>
<p>14:02 < modulus> not a big deal imo, but somewhat troublesome.</p>
<p>14:02 < jrandom> brachtus: fortuna is in pure java, doesnt use anything native</p>
<p>14:02 < smeghead> i can put jbigi into pants and that should make building a cinch if we ship pants with i2p</p>
<p>14:02 < brachtus> nothign terribly difficult, it's like building a shared lib on linux, but harder than just double-click-install</p>
<p>14:02 < smeghead> you'd need ant of course</p>
<p>14:02 < brachtus> ok jrandom, that's great :)</p>
<p>14:03 < jrandom> smeghead: thats actually a good point - jbigi has a pants dependency upon GMP</p>
<p>14:03 < ant><jnymo>gt; what is pants?</p>
<p>14:03 < smeghead> no manual mucking would be necessary</p>
<p>14:03 < ant> * jnymo doesn't have a router up</p>
<p>14:03 < smeghead> jnymo: read that link i just posted</p>
<p>14:04 < smeghead> pants can build gmp too</p>
<p>14:04 < jrandom> (public inproxy)</p>
<p>14:04 < smeghead> ah nice</p>
<p>14:04 < jrandom> yuck, that totally b0rked the text</p>
<p>14:04 < ant><jnymo>gt; thanks jr</p>
<p>14:04 < ant><fvw>gt; aren't you afraid of legal trouble?</p>
<p>14:04 < smeghead> jrandom doesn't run the inproxy</p>
<p>14:04 < jrandom> oh, the inproy is run by someone else, its been posted to the forum</p>
<p>14:05 < jrandom> (see http://bolas.mine.nu:8080/)</p>
<p>14:05 < cervantes> jrandom: it shouldn't be viewed as an html file...check the source</p>
<p>14:05 < ant><fvw>gt; still, I'm amazed anyone would. But as long as it's being run by someone not vital to the project, fine :)</p>
<p>14:05 < jrandom> hehe</p>
<p>14:05 < jrandom> we're /all/ vital to the project :)</p>
<p>14:06 < smeghead> fvw: i don't see inproxies as legally precarious as outrpoxies</p>
<p>14:06 < smeghead> outproxies even</p>
<p>14:06 < ant><fvw>gt; Perhaps not, but they can still serve up child porn and such</p>
<p>14:06 < jrandom> only if there were such things on i2p, which, to my knowledge, there isnt </p>
<p>14:06 < legion> outproxies could route through tor, just to be a little safer, since they would just be used for webrowsing I don't see it as a problem.</p>
<p>14:07 < jrandom> (but yeah)</p>
<p>14:07 < modulus> yet</p>
<p>14:07 < ant><fvw>gt; yeah, but anyone can put it on at any point.</p>
<p>14:07 < ant><fvw>gt; yeah, I wouldn't run a tor outproxy either. Anyway, sorry for drifting offtopic like that</p>
<p>14:07 < jrandom> legion: yeah, though i tossed up squid.i2p before tor was out</p>
<p>14:07 < ant><duck_>gt; to get back on topic; looking forward to pants</p>
<p>14:08 < jrandom> aye, pants++</p>
<p>14:08 < smeghead> i'll let you know before i drop pants on CVS</p>
<p>14:08 < smeghead> it's kinda big</p>
<p>14:08 < ant><duck_>gt; folks outside of i2p might be interested in it too</p>
<p>14:09 < cervantes> yes let us all know before you drop your pants</p>
<p>14:09 < smeghead> yes, i intend to publicise it outside of i2p also</p>
<p>14:09 < jrandom> agreed, perhaps we should put it in another module (or on the new fast/large server)?</p>
<p>14:09 <+Ragnarok> especially if you're a big pants kind of guy</p>
<p>14:10 < smeghead> yes the pants module really should be kept separate from the pants repo in the source tree, currently i have them located in the same apps/pants root</p>
<p>14:10 < smeghead> :/</p>
<p>14:10 < smeghead> which i don't have to tell you is total pants</p>
<p>14:11 < smeghead> so what were we talking about originally?</p>
<p>14:11 < jrandom> hmm, we can discuss deployment options offline</p>
<p>14:11 < jrandom> fortuna ;)</p>
<p>14:11 < smeghead> right</p>
<p>14:12 < jrandom> smeghead: have you looked at the AES/SHA256 needs of the impl?</p>
<p>14:12 < jrandom> (as i2p's SHA256 doesn't do partial digests)</p>
<p>14:17 < cervantes> for generally being a helpful sod to all those i2p n00bs</p>
<p>14:17 <@duck> nice avatar too</p>
<p>14:17 < cervantes> avatar(s)</p>
<p>14:18 < legion> avatars? didn't know that we could have avatars on the i2p forums?</p>
<p>14:18 < smeghead> only users who are really really bad get them</p>
<p>14:18 < cervantes> you can't...unless you're a forum person of the week ;-)</p>
<p>14:18 <@duck> only for the elite</p>
<p>14:18 < legion> oh, i see...</p>
<p>14:19 < ant><jnymo>gt; i know someone was interested in secure financial systems over i2p</p>
<p>14:19 < legion> makes sense :)</p>
<p>14:19 < ant><jnymo>gt; don't know if they're here, but...</p>
<p>14:19 <@duck> I am a smelly anarcho capitalist</p>
<p>14:19 <@duck> so try me</p>
<p>14:20 < ant><jnymo>gt; i was reading more on threashold cryptography and theres talk about using it for that</p>
<p>14:20 < ant><jnymo>gt; as well as securing other functions</p>
<p>14:21 < ant><jnymo>gt; everyone familiar with threshold cryptography?</p>
<p>14:21 < legion> IMO that cryptography and network security should be variable, how much should depend on the feature/task.</p>
<p>14:21 < ant><duck_>gt; jnymo: a bit</p>
<p>14:22 < ant><jnymo>gt; well, for trustable financial transactions in i2p, we want strong decentralized trust</p>
<p>14:22 < modulus> is that about the shared keys and shit like that?</p>
<p>14:23 < ant><jnymo>gt; yea, keys are shared in pieces</p>
<p>14:23 < ant><duck_>gt; but in an anonymous environment, how do you know that the entities doing the sharing arent controlled by the same one?</p>
<p>14:23 < ant><jnymo>gt; and you need to circumvent more than half of all the servers in the system to obtain the priv key</p>
<p>14:24 < modulus> afaik it's kind of complicated the issue of distributed key generations though.</p>
<p>14:24 < legion> yeah but in a system of millions that would be hard (yeah i2p is small at the moment, but hopefully it will grow much larger soon).</p>
<p>14:25 < ant><jnymo>gt; atomic communications, or something.. but yea, theres issues with taking on new nodes on the system, which i thing are being worked out</p>
<p>14:25 < ant><jnymo>gt; think</p>
<p>14:25 < ant><jnymo>gt; so maybe its not developed enough, but i'd bet some usage of threshold crypto will end up over i2p at some point</p>
<p>14:26 < jrandom> neat</p>
<p>14:26 < legion> dunno, maybe</p>
<p>14:26 < ant><jnymo>gt; someone has already built a DNSSEC addon with threshold crypto</p>
<p>14:27 < ant><jnymo>gt; and a wrapper around bind</p>
<p>14:27 < jrandom> thresholds work fine when identity is scarce</p>
<p>14:27 < jrandom> in anonymous networks, however, identity is free</p>
<p>14:27 < legion> I'd figure at the moment the highest priority is to get it more user friendly and debugged.</p>
<p>14:27 < jrandom> (want a new destination? want 100,000?)</p>
<p>14:28 < legion> granted it's cool whenever a new service/feature is developed.</p>
<p>14:28 < jrandom> aye, commerce and finance on top of i2p will be nice</p>
<p>14:28 < ant><jnymo>gt; yea, and i wouldn't know if atomic commo would work over a 10000 node threshold crypto sys</p>
<p>14:29 < ant><jnymo>gt; well, that's all i had to say :)</p>
<p>14:30 < jrandom> heh cool, definitely feel free to post up neat stuff to the forum or whatnot whenever</p>
<p>14:30 < jrandom> ok, anyone else have anything for the meeting?</p>
<p>14:32 <+ugha2p> I suck.</p>
<p>14:33 < jrandom> whats up ugha2p?</p>
<p>14:33 < ant><jnymo>gt; glad you got that off your' chest, ugha ;)</p>
<p>14:33 <+ugha2p> I never remember the meetings. :)</p>
<p>14:33 < jrandom> heh</p>
<p>14:33 < jrandom> well, the logs will be posted soon, 90 minutes of action packed fun</p>
