Is this the devl mailing list for Hyphanet/Freenet_Classic?

[Juiceman]

-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

Re: Important Announcement: Freenet naming change

[Juiceman]

On Wed, Jan 18, 2023, 1:54 PM Ian Clarke  wrote:

> On Wed, Jan 18, 2023 at 11:11 AM Juiceman  wrote:
>
>> On Wed, Jan 18, 2023, 12:08 PM David Dernoncourt 
>> wrote:
>>
>>> As "just a regular user" and node runner who just poked around a few
>>> PRs, the main issues I have with this are 1) "what the Hell is Locutus" and
>>> 2) wow that's confusing.
>>>
>>> Sure, 1) is just (mostly) a rhetorical question. But it seems quite an
>>> unusual thing to "steal" the name of a software (even more so when said
>>> software is still actively maintained) to stamp it on another software that
>>> doesn't have any relationship with the other one beside being supported by
>>> the same foundation and sharing the same (or a similar enough) mission
>>> statement.
>>>
>>
>> Speaking of steal:
>>
> https://trademarks.justia.com/874/39/freenet-87439977.html
>>
>
> Given that our use of the name predates their trademark by 18 years and
> has been in active use that entire time, I don't think this trademark is a
> concern.
>

My only concern was someone was trading on Freenet's name with a similar
area of technology.


> --
> Ian Clarke
> Founder, The Freenet Project
> Email: i...@freenetproject.org
>

Re: Important Announcement: Freenet naming change

[Juiceman]

On Wed, Jan 18, 2023, 12:08 PM David Dernoncourt 
wrote:

> As "just a regular user" and node runner who just poked around a few PRs,
> the main issues I have with this are 1) "what the Hell is Locutus" and 2)
> wow that's confusing.
>
> Sure, 1) is just (mostly) a rhetorical question. But it seems quite an
> unusual thing to "steal" the name of a software (even more so when said
> software is still actively maintained) to stamp it on another software that
> doesn't have any relationship with the other one beside being supported by
> the same foundation and sharing the same (or a similar enough) mission
> statement.
>

Speaking of steal:
https://trademarks.justia.com/874/39/freenet-87439977.html

While I do understand the reasoning of "I can't come up with a better name
> to describe what we're doing", boy, how confusing is that. 20-something
> year old software suddenly becomes totally different. Imagine Mozilla
> rebranding "Thunderbird" as "Firefox" and "Firefox" as "Firefox Classic"
> (and on top of that you've never head of Thunderbird), what a mess this
> would be.
>
> As far as suggestions go, even though (if it's not obvious) I don't
> support this change either (I would rather prefer, for instance, "Freenet
> Locutus" vs "Freenet Classic", dropping "Freenet [period]" instead of
> hijacking it), my suggestion would be to find a way to make it crystal
> clear that names were swapped and to point out clearly and concisely the
> key differences between the "old" Freenet and the "new" one.
>
> On Tue, Jan 17, 2023, at 15:04, Ian Clarke wrote:
> > Dear Freenet users and developers,
> >
> > I hope this email finds you well. I am writing to inform you of an
> > important change that the Freenet Project board voted on unanimously on
> > Friday. After much discussion over the past 18 months, we have decided
> > to rename the codebase and software known internally as "Fred," to
> > "Freenet Classic."
> >
> > In addition, we are announcing that the new codebase, known internally
> > as "Locutus," will be renamed to "Freenet." We understand that this is
> > a big change and it carries risk, but the board believes that this risk
> > is necessary in order to further the project's mission.
> >
> > It is important to note that this change does *not* mean that Locutus
> > is replacing Fred, which solves related but different problems. We will
> > ensure that where Fred is the appropriate tool for people they will be
> > directed to it.  Freenetproject.org will remain focused on Fred while
> > linking to Locutus - as it has been for over two decades - while
> > freenet.org will place more emphasis on Locutus, while still linking to
> > Fred.
> >
> > We will be implementing these changes over the coming days and weeks
> > and would be grateful for your ideas and suggestions on how best to do
> > this.
> >
> > Thank you,
> >
> > Ian
> >
> > --
> > Ian Clarke
> > Founder, The Freenet Project
> > Email: i...@freenetproject.org
>

[freenet-dev] paddDataPackets defaults to false??

[Juiceman]

I recently installed a new node and noticed this config setting defaults to
false? The description field recommended that it could improve local node
performance but would be detrimental if a large number of the network did
this.

This was on a linux machine and I chose low security settings if that
matters for troubleshooting.

P.S. The variable has the typo in it.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Fwd: Promiscuous opennet

[Juiceman]

I originally sent this email 3 and a half years ago.
Would it help to limit seednodes acceptance of announcement attempts to
once per hour? Would slow harvesting down and encourage uptime from users...
-- Forwarded message --
From: "Juiceman" <juicema...@gmail.com>
Date: Apr 10, 2012 2:32 PM
Subject: Promiscuous opennet
To: "Discussion of development issues" <devl@freenetproject.org>
Cc:

Should we do something about the amount of announcements/refs handed
out?  Seems a good way to harvest opennet (known problem, but perhaps
we could slow it down...) or perhaps monopolize/monitor the key-space
somehow?

opennetSizeEstimateSession: 18985 nodes
opennetSizeEstimate24h:12435 nodes
opennetSizeEstimate48h:14855 nodes
nodeUptimeSession:   4d23h


Seed stats
IPConnected  Announced  Accepted  Completed  Sent
refsVersion
24.126.77.671766352352352
  5201406
202.134.203.35 1785279279279
 1812  1377
213.134.163.3   1792275275275
  1819  1388
68.227.101.68   1793293293293
  1747  1389
62.107.42.7   1803257257257
1774  1389
67.61.122.2461840267267267
   1809 1397
82.66.7.51 1843247247247
 1400  1397
78.105.55.2061846290290290
   2053  1388
68.144.7.7 1853438438438
 1481406
80.217.175.104  1868314314314
  2053  1388
67.169.243.331919317317317
   4161406
208.76.88.92  1939327327327
1980  1376
98.21.244.1131951317317317
   2238  1376
50.4.40.1461979308308308
 2106  1385
71.204.143.231   2041292292292
   1629  1385
81.56.65.622043278278278
 2209  1384
88.174.162.112   2071297297297
   2104  1378
88.90.64.247  2110278278278
1658  1397
88.172.49.91  2120305305305
1730  1372
69.228.173.126   2146318318318
   2247  1364


--
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Thoughts on website

[Juiceman]

On Nov 8, 2015 2:48 PM, "Ian" <i...@locut.us> wrote:
>
> On Sun, Nov 8, 2015 at 12:06 PM, Juiceman <juicema...@gmail.com> wrote:
> >
> > Bikeshed discussions is where most people don't feel qualified to weigh
in
> > on designing a nuclear reactor but everyone feels like they are
entitled to
> > design the bikeshed for the employee's of said nuclear power plant. The
> > reactor will be done way before everyone and their brother agree on the
> > color of the shed.
> >
>
> Except the color of a bikeshed isn't central to the function of the
> bikeshed.  A website is there to be read, so if the color of the site
> impedes readability then it is very much central to the function of the
> site.
>
>
> > I like the new site and I think you should stop pissing on volunteer's
> > efforts.
> >
>
> Of course, nobody should ever provide constructive criticism of anything
> because that would be "pissing on volunteer's
> efforts".  Buggy code?  Poor documentation?  Doesn't matter, you're not
> allowed to criticize.
>
> That's ridiculous.  Multiple independent people have told us that the
color
> scheme is a problem.  You can stick your fingers in your ears and sing
> "la-la-la" if you want, but don't expect me to.

As you said yourself you should have weighed in earlier. Now it feels like
nitpicking.

>
> Ian.
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Thoughts on website

[Juiceman]

On Nov 8, 2015 12:27 PM, "Ian"  wrote:
>
> On Sun, Nov 8, 2015 at 11:12 AM, Arne Babenhauserheide 
> wrote:
>
> > Am Sonntag, 8. November 2015, 08:55:50 schrieb Ian:
> >
> Light on dark or dark on light is a minor point.
>
>
> I disagree, it is the single most obvious aspect of the design, the very
> first thing people notice when they visit the site.  We can't just ignore
> the feedback we're getting because it is inconvenient.
>
> On that subject though, from what Steve is saying the new site should be
> much easier to modify than the old site, so I'm not sure that this is such
> a catastrophic change after all.  The site already uses bootstrap, all I'm
> suggesting is that we go back to the default Bootstrap color scheme, or
> something closer to it.
>
>
> > So please let us stop the bikeshedding discussion. We’re working on
> > realizing the important points of the feedback — for example “your
> > download page does not ask me to download the software” and “I don’t
> > understand how your tool helps me in the first 10 seconds”.
> >
>
> I don't know what you mean by "bikeshedding discussion", but having a well
> designed website is critical to the project's success.  I don't understand
> why you want to ignore feedback from multiple sources, combined with
> scientific data, telling us that there are serious issues with the color
> scheme.
>

Bikeshed discussions is where most people don't feel qualified to weigh in
on designing a nuclear reactor but everyone feels like they are entitled to
design the bikeshed for the employee's of said nuclear power plant. The
reactor will be done way before everyone and their brother agree on the
color of the shed.

I like the new site and I think you should stop pissing on volunteer's
efforts.

> Ian.
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet website & optimization

[Juiceman]

On Nov 4, 2015 9:54 AM,  wrote:
>
> First of all, very good how the donation money bar on the website
currently is - https://freenetproject.org/index.html
> Clear improvement to the vague donation time bar, which wasn't really
motivating to donate as such and by it's boring small design.
>
> Suggestion:
> 1. Place the donation money bar below the first download button on the
main page. It's weird to hold up the hand even before offering the product.
> I could imagine that after said re-organization, the fact that the
horizontal section containing prize and 'motivation section' is asymmetric
will have a
> slightly less bad effect. One way or the other, the asymmetry is not
that tragic. No need to worry.
> 2. Let the 'motivation section' giving reasons why to use Freenet rotate,
so that every 12 seconds the displayed reason switches automatically.
>
>
> Greetings,
> Torben Lechner
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

I like the new website.

The donation bar is crowded on my phone. It could be wider and/or round the
donated amount to nearest whole dollar.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Behind the times

[Juiceman]

On Oct 22, 2015 11:09 PM, "Steve Dougherty"  wrote:
>
> On 10/22/2015 10:58 PM, Ian Clarke wrote:
> > On Thu, Oct 22, 2015 at 9:43 PM, Steve Dougherty 
> > wrote:
> ...
> >> I don't understand what you mean by this exactly. Reduce padding
between
> >> sections and put the download button where? Up in the menu?
> >>
> >
> > Probably below the menu, but in the top-right of the page.  That way
it's
> > very prominent, but not the immediate thing that attracts attention.
>
> Why?
>
> > I think right now the first thing people are encouraged to look at is
the
> > Download button, but to figure out why they might want to consider
> > downloading, they have to scroll down to the "What is Freenet?" section.
>
> Currently the Browse and Forums panes link to the same page, so I'd want
> to fix that before making the section even more prominent. Somewhat less
> scrolling would be good here, yes.
>
> > I think we need a very concise explanation of why they would want to
> > download Freenet as the focal point for the front page.
> >
> > Thoughts?
>
> That's the intent of the slides, which are above the button: it starts
> on "Avoid Censorship" "Freenet is a platform for censorship-resistant
> communication and publishing. ..."
>

The left and right arrows are too close to the edge of my phone screen. My
screen protector almost covers them. Can I get a few more pixels please?

> Is that more verbose than you were thinking?
>
>
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Thoughts on removing native acceleration? [cross-post FMS]

[Juiceman]

On Sep 19, 2015 3:26 PM, "Steve Dougherty"  wrote:
>
> Does anyone have benchmarks that demonstrate native acceleration having
> significant performance improvements? Keeping it around makes for
> maintenance, and anecdotes suggest native Java performance is
> sufficient. If it's no longer a clear benefit to have native
> acceleration I'd like to look into removing it to lower maintenance
> load. Thoughts?
>
>

No idea on benchmarks.
From what I have been reading just now it looks like Java's BigInteger
performance should be much improved with Java 8. See Java bug 4837946

The next build + 1 will require Java 7. I think people will naturally be
migrating to Java 8 and you have enough to maintain already.

> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Multiple SourceForge issues

[Juiceman]

On Sep 11, 2015 6:14 PM, "Arne Babenhauserheide"  wrote:
>
> Am Donnerstag, 10. September 2015, 18:30:54 schrieb Matthew Toseland:
> > I did that once. Ian got really angry. Granted it's not really his
> > decision any more. But he's right, isn't he? Versions are for marketing,
> > not for change tracking?
>
> He might have reasons I do not see, so I don’t feel I can judge that.
>
> This here is a communication issue: If there is an old version
> somewhere and people don’t see that this old version is actually old
> (0.7.5 vs. 0.7.5), then that’s a problem.
>
> If there is no place which shows that old version as the most recent
> one, I don’t see incrementing the version as necessary.
>
> And I should be clearer: I only mean “no longer able to update over
> mandatory”. Also I don’t think we need to make this a rule. I think
> that it’s time to increment the version regardless of this issue (for
> marketing reasons: we have lots of new features).
>
> Best wishes,
> Arne
> --
> Unpolitisch sein
> heißt politisch sein,
> ohne es zu merken.
> - Arne (http://draketo.de)
>
>
>
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

*build* number should never be reset. Windows doesn't. AFAIK is supposed to
represent builds (not releases).

Essentially Freenet version is 0.7.5.1472 or whatever.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] [RFC] Update channels

[Juiceman]

On Aug 18, 2015 11:17 AM, xor x...@freenetproject.org wrote:

 On Friday, September 19, 2014 10:03:29 PM Steve Dougherty wrote:
   Also, is this usable for plugins, too?
 
  It seems desirable to have it generic enough to do so, but I'm not sure
  it's in the initial scope.

 We've had 2 continuous WOT builds fail to be released due to issues which
were
 not detected during testing but only when you tried to deploy them.
 This sounds like the manual JAR ZIPs I publish don't get enough testers :|
 (and like I should setup a compilation environment similar to the release
 environment you use :| Sorry for not having done that yet.)

 Also, I'm increasingly feeling like having to deal with plugin deployment
is
 too much of a burden for you, and I don't want to stress you with it.
 Especially now that the release cycle of WOT will be much shorter since
 everyone was so unhappy about the huge delays.

 So it would be really nice if update channels included plugins.

iirc using an USK for plugin address allows updates for plugins separate
from fred builds. Heck, I seem to recall it being fixed to work on even
Windows by just clicking the 'reload plugin' button. Windows had been
bugged because of files not be closed on plugin unload but that was fixed
6? 12? months ago. I know I tested it with Sone and was impressed.

For now XOR can gather volunteers to run his private USK for testing.

Ideally fred should include update channels. Define official plugin USKs,
wire in notifications with 'ignore' and 'reload plugin now'.
Official maintainer pushes new insert to the defined plugin USK. Done. 


 Fred should then offer some configuration like this:

  Get updates from:
  ( ) The main official stable Freenet repository
  (*) Testing releases from developer xor

 This would allow me to publish pre-releases to a wider audience, and
cause you
 to have less hassle.

 It should include the opportunity for me to:

 - update not only WOT but also everything else: I sometimes do file fred
pull
 request. Also, once the WOT-performance mess has been resolved, I should
not
 just consider my job as WOT maintainer but client-application
maintainer,
 and thus deal with other plugins as well. We should really get all
WOT-based
 plugins official ASAP then! :)

 - if I don't have the setup to compile every fred release and every
plugin, it
 should be possible to ask me to have it fall-back to the official update
 channel for stuff which I don't compile myself. This is crucial as the
 development environments are very different among all the plugins and it
can
 cost a lot of time to be able to figure out each one's dependencies.


 Anyway, overall you applying the word burnout to yourself recently,
even if
 it was joined with something like before I burn out, sounds very
alarming;
 so if you do someday again feel like writing code, you might write the
update
 channels stuff first to give yourself the chance to get rid of the boring
 plugin hassle :)
 Meanwhile, please relax first! :)


 Greetings and thanks for your tremendous efforts,
 xor
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre4

[Juiceman]

It is fixed now but the update-new.cmd file still has wrong line endings
On Jul 18, 2015 1:51 PM, Florent Daigniere nextg...@freenetproject.org
wrote:

 Weird. I re-ran the script for testing-build-1469-pre2; let me know if
 it's still a problem.

 Florent

 On Fri, 2015-07-17 at 11:47 -0400, Juiceman wrote:
  I don't know the answer to that. I do know that
  https://downloads.freenetproject.org/alpha/update/
  has the wrong line endings.
  I'm confused how it could have broken again. Is a .gitattribute file
  with
  eol=clrf not sufficient?
 
  On Fri, Jul 17, 2015, 11:35 AM Juiceman juicema...@gmail.com wrote:
 
   .cmd file line endings are still broken on website. Needs to have
   CR-LF
   endings.
   On Jun 27, 2015 8:47 PM, Steve Dougherty st...@asksteved.com
   wrote:
  
On 06/27/2015 04:35 PM, Steve Dougherty wrote:
 Freenet unstable testing prerelease 1468-pre4 is now available.
  Inserts
 are pending and I will reply with keys once they are available.
   
CHK@4idgkGIa6hOZcAKELAnrz
   
  
  ~N7e0qPTRuUrMlshB8Ezds,JmRtt4Txm6gXB
  -Xxzd9ydzopgi0pE3ZFBwdXSVpmPII,AAMC--8/freenet-testing-build-1468
  -pre4-snapshot.jar
CHK@m31Yy2OaI
   
  
  ~efNlNhBgzeQ47zn0IQfCtRuG4peMaN63o,g
  -Bpfc1qMO2bgrr0yDYWxpZ5zprphCS4ZYaJFGdaCnI,AAMC--8/freenet-testing
  -build-1468-pre4-snapshot.jar.sig
CHK@WV4QQbQFMAeGI7alvpe1o
   
  
  ~e2vUAW43-TEk0Jy1jXhS0,vNtw1SDmo4I-nw1eQTzp6w36URz
  -K1kPBRBawxmd3UQ,AAMC--8/freenet-testing-build-1468-pre4
  -source.tar.bz2
CHK@f2xr1
   
  
  ~I~l2jj4ZBVzJpx20oN0qTHYc6DSkmUh2Ys~Fw,8rmsSQCjrtmXpcPQneWfxUrqzcJagm
  t6nZpzBrl8414,AAMC--8/freenet-testing-build-1468-pre4
  -source.tar.bz2.sig
   
   
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
   
   ___
   Devl mailing list
   Devl@freenetproject.org
   https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre4

[Juiceman]

.cmd file line endings are still broken on website. Needs to have CR-LF
endings.
On Jun 27, 2015 8:47 PM, Steve Dougherty st...@asksteved.com wrote:

 On 06/27/2015 04:35 PM, Steve Dougherty wrote:
  Freenet unstable testing prerelease 1468-pre4 is now available. Inserts
  are pending and I will reply with keys once they are available.

 CHK@4idgkGIa6hOZcAKELAnrz
 ~N7e0qPTRuUrMlshB8Ezds,JmRtt4Txm6gXB-Xxzd9ydzopgi0pE3ZFBwdXSVpmPII,AAMC--8/freenet-testing-build-1468-pre4-snapshot.jar
 CHK@m31Yy2OaI
 ~efNlNhBgzeQ47zn0IQfCtRuG4peMaN63o,g-Bpfc1qMO2bgrr0yDYWxpZ5zprphCS4ZYaJFGdaCnI,AAMC--8/freenet-testing-build-1468-pre4-snapshot.jar.sig
 CHK@WV4QQbQFMAeGI7alvpe1o
 ~e2vUAW43-TEk0Jy1jXhS0,vNtw1SDmo4I-nw1eQTzp6w36URz-K1kPBRBawxmd3UQ,AAMC--8/freenet-testing-build-1468-pre4-source.tar.bz2
 CHK@f2xr1
 ~I~l2jj4ZBVzJpx20oN0qTHYc6DSkmUh2Ys~Fw,8rmsSQCjrtmXpcPQneWfxUrqzcJagmt6nZpzBrl8414,AAMC--8/freenet-testing-build-1468-pre4-source.tar.bz2.sig


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre4

[Juiceman]

I don't know the answer to that. I do know that
https://downloads.freenetproject.org/alpha/update/
has the wrong line endings.
I'm confused how it could have broken again. Is a .gitattribute file with
eol=clrf not sufficient?

On Fri, Jul 17, 2015, 11:35 AM Juiceman juicema...@gmail.com wrote:

 .cmd file line endings are still broken on website. Needs to have CR-LF
 endings.
 On Jun 27, 2015 8:47 PM, Steve Dougherty st...@asksteved.com wrote:

  On 06/27/2015 04:35 PM, Steve Dougherty wrote:
   Freenet unstable testing prerelease 1468-pre4 is now available.
Inserts
   are pending and I will reply with keys once they are available.
 
  CHK@4idgkGIa6hOZcAKELAnrz
 

~N7e0qPTRuUrMlshB8Ezds,JmRtt4Txm6gXB-Xxzd9ydzopgi0pE3ZFBwdXSVpmPII,AAMC--8/freenet-testing-build-1468-pre4-snapshot.jar
  CHK@m31Yy2OaI
 

~efNlNhBgzeQ47zn0IQfCtRuG4peMaN63o,g-Bpfc1qMO2bgrr0yDYWxpZ5zprphCS4ZYaJFGdaCnI,AAMC--8/freenet-testing-build-1468-pre4-snapshot.jar.sig
  CHK@WV4QQbQFMAeGI7alvpe1o
 

~e2vUAW43-TEk0Jy1jXhS0,vNtw1SDmo4I-nw1eQTzp6w36URz-K1kPBRBawxmd3UQ,AAMC--8/freenet-testing-build-1468-pre4-source.tar.bz2
  CHK@f2xr1
 

~I~l2jj4ZBVzJpx20oN0qTHYc6DSkmUh2Ys~Fw,8rmsSQCjrtmXpcPQneWfxUrqzcJagmt6nZpzBrl8414,AAMC--8/freenet-testing-build-1468-pre4-source.tar.bz2.sig
 
 
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
 
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre4

[Juiceman]

It works now. Thanks! No further issues upgrading from -pre3

On Sat, Jun 27, 2015 at 8:13 PM, Steve Dougherty st...@asksteved.com wrote:
 On 06/27/2015 07:36 PM, Juiceman wrote:
 The windows update script on the website still has Unix style line endings
 that break the batch script. My install detects a new script on the
 website, downloads and launches it then fails with the system cannot find
 the batch label specified - extjardownloadend. I tracked this down to the
 line endings issue about a month ago. The directory on the website 
 https://downloads.freenetproject.org/alpha/update; needs to have the .cmd
 files saved with CRLF style line endings.

 Let me know when this is done and I will retest.

 Whoops, sorry about that - I forgot. Thank you for bringing it up again.

 I've added a .gitattribute file with eol=clrf [0] for update.cmd and
 uploaded them again. It now has clrf line endings. Does it work now?

 [0]
 https://github.com/freenet/wininstaller-innosetup/commit/9c926411874a04190221ec4456eb0713b7bcbe78


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre4

[Juiceman]

The windows update script on the website still has Unix style line endings
that break the batch script. My install detects a new script on the
website, downloads and launches it then fails with the system cannot find
the batch label specified - extjardownloadend. I tracked this down to the
line endings issue about a month ago. The directory on the website 
https://downloads.freenetproject.org/alpha/update; needs to have the .cmd
files saved with CRLF style line endings.

Let me know when this is done and I will retest.
On Jun 27, 2015 4:35 PM, Steve Dougherty st...@asksteved.com wrote:

 Freenet unstable testing prerelease 1468-pre4 is now available. Inserts
 are pending and I will reply with keys once they are available.

 In the absence of critical bugs this is the last prerelease before the
 stable release on 2015-07-11. If you've been waiting to try a testing
 release until it settled down or until all the official plugins worked,
 all official plugins work, so now is the time to do so! Note that
 automatic downgrading is not supported, so if you want to go back to
 1467 without losing the upload and download queue back up master.keys,
 persistent-temp-*/ and node.db4o* before upgrading (see
 https://wiki.freenetproject.org/Program_files ).

 If a plugin which is not compatible with 1468 hangs while loading and
 cannot be unloaded, shut down Freenet, remove its entry from
 pluginmanager.loadplugin in freenet.ini, and start Freenet again.

 If you'd like to help test upgrading over auto-update, set the
 auto-update key of a 1467 node to:

 USK@7oujRHSeR4m
 ~99Dv~trRUj11s7sYGuiEDS-KPjvHYW4,j~OOXsiNXTId25H-NQeeEzbTSPAOLkdJD39WXcYq5BQ,AQACAAE/testing-jar/1467

 (At the time of this writing the insert is not yet complete.)

 This keypair was used only to insert this testing update and has since
 been discarded, so you'll need to restore the previous key to continue
 getting updates.

 * There is a new tray app with some useful features that is included
   with new installations [0]. If you are using the existing Windows tray
   app you can download the new one here [1]. No need to put it in a
   specific directory - it will try the default installation location and
   prompt if it can't find it.

 * The list of download keys has moved from downloads/listFetchKeys.txt
   to downloads/listKeys.txt.

 * A list of upload keys is now available at uploads/listKeys.txt.

 * Gantros' index is now in the default bookmarks. It uses the same
   software as Enzo's index, which is no longer updated.

 * The obsolete and deprecated XMLLibrary and XMLSpider plugins are no
   longer officially supported. They will still load for those who have
   them added, but are no longer shown on the plugin page.

 * In the interest of releasing this build more quickly, this version of
   FlogHelper does not support exporting and importing backups from the
   web UI. The old backup code did not work with the new Freenet version
   after removing db4o. People can instead back up
   plugins.floghelper.FlogHelper files in the plugin-data directory.
   These can be dropped into the directory after unloading FlogHelper to
   restore a backup.

 * ThawIndexBrowser works again. Thanks saces!

 * Add two seed nodes, one sponsored by meshnet.pl - the Polish
   radio/meshnet darknet users group, and another run by ArneBab. Thanks!


 FlogHelper changes since v32:
 ---

 Steve Dougherty (4):
   Update translation
   Update version to 33
   Disable blog export and import
   Version 34

 TheSeeker (1):
   Update API usage for purge-db4o


 ThawIndexBrower changes since v5:
 ---

 Matthew Toseland (1):
   Fix build.

 saces (3):
   remove obsolete classpath entry
   build fixes for 1468-pre3
   bump version number


 Fred changes since 1468-pre3:
 ---

 David ‘Bombe’ Roden (3):
   Try to reload seednodes if they are missing
   Add request client builder
   Replace anonymous classes by request client builder

 Matthew Toseland (5):
   Tell the TempBucket when the RAF is freed, and clarify.
   Better to just set the flag.
   Free outside the lock unless it's stored in RAM
   Check for double free here too (will happen for temp-buffer).
   Resume ClientPutDir.manifestElements on startup, fixes NPE

 Steve Dougherty (5):
   Document purpose of seed node retry
   RequestClientBuilder: remove superfluous documentation
   Update ThawIndexBrowser to v6
   Add contributing guidelines
   Update FlogHelper to v34

 drak@kaverne (4):
   default bookmarks: add Gantros index
   default bookmarks: change order: nerd, gantros, link, enzo
   Split default bookmark software and docs; add docs sites
   Add bookmark localization

 saces (1):
   fix the 'open with ThawIndexBrowser' link

 xor-freenet (11):
   freenet.support.TransferThread: Deprecate
   TransferThread: Clarify reasons for deprecation
   ClientRequester: Keep track of latest 

Re: [freenet-dev] Donation page on website

[Juiceman]

On Jun 3, 2015 6:29 AM, hyazin...@emailn.de wrote:

 I agree, that aims are good.
 But I think that displaying donation status in a way, so that you can see
it when you've donated 10$, is just as important. People need this
verification quality,
 and with the current display of donation status they have it. I'm not
saying by this, that all should stay like it is right now. I'm hinting on
what shouldn't be lost in the process of change.

I thought the balance is currently only updated twice a day? How is it
different?
Of course we wouldn't show just a plain progress bar, numbers would be
included.

Just my 2 cents.  



 Greetings,
 Torben Lechner

 --- Ursprüngliche Nachricht ---
 Von: Juiceman juicema...@gmail.com
 Datum: 02.06.2015 17:45:25
 An: Discussion of development issues devl@freenetproject.org
 Betreff: Re: [freenet-dev] Donation page on website

  On Jun 2, 2015 11:07 AM, Gerard Krol ger...@gerardkrol.nl
  wrote:
  
   Yes, that's the reason I didn't spend any time bringing it over. For
  a
   single person donating $10k is a lot of money. A progress bar would
  solve
   that. Our full goal could be to fund the project for 12 months, that
   doesn't sound unreasonable.
  
   Regards,
  
   Gerard
  
 
  12 months is still beyond the horizon of most average people. If you
want
  to lose 50 pounds in six months you don't ignore the scale for 5 months
  and
  then find out you have only lost 10 pounds and stop eating for month 6.
  You give yourself mini goals 5 lbs a week or 10 pounds a month or
whatever
  works so you feel like progress is being made. If you don't make your
mini
  goal you know to work harder for the next check-in.
 
  If you want to put a year progress bar next to it that is fine.
 
   On Tue, Jun 2, 2015 at 4:37 PM, Juiceman juicema...@gmail.com
  wrote:
  
I have been meaning to bring this for a while.  The donate page
  shows
  our
balance $10K+ or whatever. In my mind this actually discourages
  donations.
eh. The project has enough money for now... my $10 isn't
  gonna make a
difference.
   
People respond to goals. We figure out what monthly amounts we
  need to
  fund
at full paid developer level and display that as a progress bar.
  Thoughts?
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
   ___
   Devl mailing list
   Devl@freenetproject.org
   https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Donation page on website

[Juiceman]

I have been meaning to bring this for a while.  The donate page shows our
balance $10K+ or whatever. In my mind this actually discourages donations.
eh. The project has enough money for now... my $10 isn't gonna make a
difference.

People respond to goals. We figure out what monthly amounts we need to fund
at full paid developer level and display that as a progress bar.  Thoughts?
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Donation page on website

[Juiceman]

On Jun 2, 2015 11:07 AM, Gerard Krol ger...@gerardkrol.nl wrote:

 Yes, that's the reason I didn't spend any time bringing it over. For a
 single person donating $10k is a lot of money. A progress bar would solve
 that. Our full goal could be to fund the project for 12 months, that
 doesn't sound unreasonable.

 Regards,

 Gerard


12 months is still beyond the horizon of most average people. If you want
to lose 50 pounds in six months you don't ignore the scale for 5 months and
then find out you have only lost 10 pounds and stop eating for month 6.
You give yourself mini goals 5 lbs a week or 10 pounds a month or whatever
works so you feel like progress is being made. If you don't make your mini
goal you know to work harder for the next check-in.

If you want to put a year progress bar next to it that is fine.

 On Tue, Jun 2, 2015 at 4:37 PM, Juiceman juicema...@gmail.com wrote:

  I have been meaning to bring this for a while.  The donate page shows
our
  balance $10K+ or whatever. In my mind this actually discourages
donations.
  eh. The project has enough money for now... my $10 isn't gonna make a
  difference.
 
  People respond to goals. We figure out what monthly amounts we need to
fund
  at full paid developer level and display that as a progress bar.
Thoughts?
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] New Freenet website (almost finished)

[Juiceman]

Nice!  I am browsing on a mobile device and see a few overlapping texts but
looks good so far!
On May 31, 2015 4:49 PM, Gerard Krol ger...@gerardkrol.nl wrote:

 Hello everyone!

 It has been a busy weekend and now the new Freenet website is almost
 finished!
 Take a look: http://realitysink.com/freenet/en/
 The source is on Github: https://github.com/gerard-/freenet-website

 Thanks to everyone who gave feedback. As you can see in the readme there
 are some things left to do. Some minor licensing stuff needs to be finshed
 and the site will have to be translated. It uses gettext so that should be
 quite easy. All content that was on the freenetproject.org site has been
 migrated over and we can probably re-use most of the translations.

 Comments  pull requests are welcome!

 This message has been posted to the Freenet dev mailing list and to the FMS
 boards Freenet and Freenet.promo. Please reply on the FMS Freenet board if
 possible.

 Regards,

 Gerard
 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1468-pre3

[Juiceman]

the Windows update script is borked.  it needs to be resaved with windows
line endings instead of unix.  otherwise the goto jumps fail...
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Incoming bugfix release 2014-11-22 or 2014-11-23

[Juiceman]

On Nov 21, 2014 10:19 AM, Matthew Toseland mj...@cam.ac.uk wrote:

 On 21/11/14 09:52, Steve Dougherty wrote:
  Bug #6411 [0] got into build 1466.
 
  When Fred writes the configuration file on startup
  `pluginmanager.loadplugins` is blank due to a race condition introduced
  by 869f62559a06b2f72c9224a2179001dd551ea442. If, after all plugins have
  started or failed to start, a configuration change or clean shutdown
  causes the configuration to be written again it will be written
  correctly. This means a crash will likely clear the node's list of
  plugins to load.
 Do we need to reset to the default list of plugins to work around this?
 E.g. UPnP/STUN can be really essential in some cases ... but some people
 really want to turn them off. Thoughts?

Put up a user alert that warns users to check their plugins and re-add
UPnP/STUN etc if missing.  Users that don't want them can ignore it.

Can alerts be set as permanent until dismissed and then not show again
again, even if node is rebooted?

 
  The proposed fix is in pull request 311. [1]
 
  I've started the stable-1467 branch and added a fix for the new default
  bookmark not appearing to it. [2] Are there any other bugs introduced in
  1466 that should be fixed in this (please very very small) upcoming
release?
 
  - Steve
 
  [0] https://bugs.freenetproject.org/view.php?id=6411
  [1] https://github.com/freenet/fred/pull/311
  [2]
 
https://github.com/freenet/fred/commit/12b2664c139dba78eb476373349f5adfae98e003
 
 
 
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Coding Standard

[Juiceman]

The tool I am using to convert all the source in a repository is Jindent
which also has the option to sort classes and interfaces, etc.

On Sat, Nov 1, 2014 at 7:00 PM, David ‘Bombe’ Roden bo...@pterodactylus.net
 wrote:

 Hi there,

 initiated by a change in a pull request[1] the issue of coding style (or
 coding standard) popped up, once again. Instead of inventing our own coding
 style I proposed on IRC that we used either SUN’s Code Conventions[2] or
 Google’s Java Style[3].

 Now that I’ve looked for the URL I would like to retract my suggestion of
 SUN’s Code Conventions, those haven’t been updated since 1999… :)

 So, Google’s Java Style. It’s reasonable close to what we already employ,
 and formatters in the popular IDEs will probably have no bigger problem
 creating output that conforms to this style guide.

 However, adopting a new style guide creates an immediate problem: the
 existing code. Which probably has more different styles combined than the
 style guide has words. :)

 I’m not a big fan of these single large commits that reformat all source
 code at once. As Google’s style guide mandates a little bit more than just
 whitespace and bracket position (e.g. that overloaded methods/constructors
 must not be interrupted by other methods, or that the order of fields and
 method must conform to some logical order, i.e. not a chronological order)
 most of the code must be manually checked and potentially corrected.

 I wouldn’t really touch the existing source code immediately but make sure
 that a) new source code conforms to the style guide, and b) touched code is
 reformatted: at least edited methods should be reformatted, preferrable
 after the “real” commit so that functional changes are not lost in the
 formatting. If the whole file is rather easy to adapt to the new style, the
 whole file can be changed, too.

 Thoughts, suggestions, opinions?


 Greetings,

 Bombe

 [1]: https://github.com/freenet/fred/pull/298/
 [2]: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html
 [3]: https://google-styleguide.googlecode.com/svn/trunk/javaguide.html


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl




-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Coding Standard

[Juiceman]

It also looks like Google and Sun are mostly the same but designating
'Google' does give us one standard to reference which I like.
That said, Google calls out 2 space indents.  Makes it easier to format the
code, but harder to read.  Thoughts?

On Sat, Nov 1, 2014 at 8:57 PM, Juiceman juicema...@gmail.com wrote:

 The tool I am using to convert all the source in a repository is Jindent
 which also has the option to sort classes and interfaces, etc.

 On Sat, Nov 1, 2014 at 7:00 PM, David ‘Bombe’ Roden 
 bo...@pterodactylus.net wrote:

 Hi there,

 initiated by a change in a pull request[1] the issue of coding style (or
 coding standard) popped up, once again. Instead of inventing our own coding
 style I proposed on IRC that we used either SUN’s Code Conventions[2] or
 Google’s Java Style[3].

 Now that I’ve looked for the URL I would like to retract my suggestion of
 SUN’s Code Conventions, those haven’t been updated since 1999… :)

 So, Google’s Java Style. It’s reasonable close to what we already employ,
 and formatters in the popular IDEs will probably have no bigger problem
 creating output that conforms to this style guide.

 However, adopting a new style guide creates an immediate problem: the
 existing code. Which probably has more different styles combined than the
 style guide has words. :)

 I’m not a big fan of these single large commits that reformat all source
 code at once. As Google’s style guide mandates a little bit more than just
 whitespace and bracket position (e.g. that overloaded methods/constructors
 must not be interrupted by other methods, or that the order of fields and
 method must conform to some logical order, i.e. not a chronological order)
 most of the code must be manually checked and potentially corrected.

 I wouldn’t really touch the existing source code immediately but make
 sure that a) new source code conforms to the style guide, and b) touched
 code is reformatted: at least edited methods should be reformatted,
 preferrable after the “real” commit so that functional changes are not lost
 in the formatting. If the whole file is rather easy to adapt to the new
 style, the whole file can be changed, too.

 Thoughts, suggestions, opinions?


 Greetings,

 Bombe

 [1]: https://github.com/freenet/fred/pull/298/
 [2]: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html
 [3]: https://google-styleguide.googlecode.com/svn/trunk/javaguide.html


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl




 --
 I may disagree with what you have to say, but I shall defend, to the
 death, your right to say it. - Voltaire
 Those who would give up Liberty, to purchase temporary Safety, deserve
 neither Liberty nor Safety. - Ben Franklin




-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] 1464 prerelease testing snapshot

[Juiceman]

So far so good.  An hour into it and nothing seems broken :)

On Sat, Jul 5, 2014 at 1:25 AM, Steve Dougherty st...@asksteved.com wrote:
 On 07/05/2014 12:40 AM, Steve Dougherty wrote:
 There's a snapshot of something like what will become 1464 on the
 webserver (update.sh testing or update.cmd testing) and inserting currently.

 CHK@o0rNDSdac4JJyyY50Ikb0-jKjfvzqfLhVFyzmZOoatw,MBYjHJaQPMpKHh~XUwtQooOm~LygLJO2bGdB8qY5l5U,AAMC--8/freenet-build01463-40-g0a16d5645840200a8550c8b0a956a806f597375a-snapshot.jar

 CHK@TTm29-lgNRDKgTu~LYwxqKDixYIuxYj3hHYjOpPmCeo,WOKtLqwZBGDdEgbLtfmfRFCW6VbzOHpE9vuUFXR2vRs,AAMC--8/freenet-build01463-40-g0a16d5645840200a8550c8b0a956a806f597375a-snapshot.jar.sig


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] database

[Juiceman]

On Jul 7, 2014 2:28 AM, Volker Fervers mail...@edv-fervers.de wrote:

 Hi all,

 I remember posts about the search for an alternative to db4o. Are there
 any candidates?

 Thank you!
 GV


I believe Toad (Matthew Toseland) is re-writing the client layer to not use
a database.
___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Fwd: [freenet-support] www not working

[Juiceman]

Who broke the website?  

Freenetproject.org works but www.freenetproject.org does not.
-- Forwarded message --
From: Narcis Garcia informat...@actiu.net
Date: Jun 29, 2014 1:41 PM
Subject: [freenet-support] www not working
To: supp...@freenetproject.org
Cc:

Hello, this URL is linked from diverse websites:
 http://www.freenetproject.org/
 But at this time it doesn't redirect to your website content.

 Regards.
 ___
 Support mailing list
 supp...@freenetproject.org
 http://news.gmane.org/gmane.network.freenet.support
 Unsubscribe at
 http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
 Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Strange client activity

[Juiceman]

On my seed node I am seeing a few IP addresses connecting ridiculously often

 With almost 6 days of uptime these are the three worst

IP  Connected  Announced  Accepted  Completed  Sent refs  Version

184.52.99.110  1473  373  373  373  836  1462
99.60.162.70  1720  422  422  422  944  1462
208.91.115.12  2280  597  597  597  79  1462

The first looks to be someone's satellite internet connection... okay
maybe flaky connection.
The second comes from ATT, perhaps U-verse or similar home internet.
Why so spammy??
The third is very interesting!

Fortinet Network Security

NetRange:   208.91.112.0 - 208.91.115.255
CIDR:   208.91.112.0/22
OriginAS:   AS577, AS852
NetName:FORTINET
NetHandle:  NET-208-91-112-0-1
Parent: NET-208-0-0-0-0
NetType:Direct Assignment
RegDate:2008-06-04
Updated:2012-06-13
Ref:http://whois.arin.net/rest/net/NET-208-91-112-0-1

OrgName:Fortinet Inc.
OrgId:  FTC-58
Address:899 Kifer Road
City:   Sunnyvale
StateProv:  CA
PostalCode: 94086
Country:US
RegDate:2008-04-10
Updated:2014-03-31
Ref:http://whois.arin.net/rest/org/FTC-58

Are we being researched/attacked?


-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Pretty sure 1462 is broken by commit 6d0321c1bbf96c593681719c8d4d0a63555d2e32

[Juiceman]

On Jun 2, 2014 2:06 PM, David Roden bo...@pterodactylus.net wrote:

 Hi,

 you’re right. I pushed a fix to next.



Thanks David!

Steve, can we get a -testing release on this please?  My build machine is
fubared right now.  It is important that we get this tested and deployed
before the remaining seednodes get updated and opennet falls apart.

Thanks.

 Greetings,
 --
  * David ‘Bombe’ Roden bo...@pterodactylus.net

 On 02.06.2014, at 06:22, Juiceman juicema...@gmail.com wrote:

  My seednode came online right before 1462 was released and was
  seeding.  Since 1462 I have not seen a single seed client connect.  My
  logs are full of:
 
  Jun 02, 2014 02:22:12:164 (freenet.support.SerialExecutor$2, FNP
  incoming auth packet handler thread(0), ERROR): Caught
  java.lang.NullPointerException
  java.lang.NullPointerException
 at freenet.node.PeerNode.userToString(PeerNode.java:3819)
 at freenet.node.PeerNode.init(PeerNode.java:624)
 at freenet.node.SeedClientPeerNode.init(SeedClientPeerNode.java:20)
 at
freenet.node.FNPPacketMangler.getPeerNodeFromUnknownInitiator(FNPPacketMangler.java:1493)
 at
freenet.node.FNPPacketMangler.processJFKMessage3(FNPPacketMangler.java:1369)
 at freenet.node.FNPPacketMangler.access$200(FNPPacketMangler.java:75)
 at freenet.node.FNPPacketMangler$2.run(FNPPacketMangler.java:567)
 at freenet.support.SerialExecutor$2.run(SerialExecutor.java:73)
 at
freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:248)
 at
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:188)
 at freenet.support.io.NativeThread.run(NativeThread.java:129)
 
 
https://github.com/freenet/fred-staging/commit/6d0321c1bbf96c593681719c8d4d0a63555d2e32
  was getting rid of string concatenations, but looks like it did more
than that.
 
 
  src/freenet/node/PeerNode.java
  @@ -3816,7 +3816,7 @@ public int selectNegType(OutgoingPacketMangler
mangler) {
 
   }
public String userToString() {
  - return  + getPeer();
  + return  getPeer().toString();
   }
 
   public void setTimeDelta(long delta) {
 
 
  are NOT functionally equivalent.
 
  --
  I may disagree with what you have to say, but I shall defend, to the
  death, your right to say it. - Voltaire
  Those who would give up Liberty, to purchase temporary Safety, deserve
  neither Liberty nor Safety. - Ben Franklin
  ___
  Devl mailing list
  Devl@freenetproject.org
  https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
 


 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Pretty sure 1462 is broken by commit 6d0321c1bbf96c593681719c8d4d0a63555d2e32

[Juiceman]

On Tue, Jun 3, 2014 at 8:46 PM, Steve Dougherty st...@asksteved.com wrote:
 On 06/03/2014 10:17 AM, Juiceman wrote:
 On Jun 2, 2014 2:06 PM, David Roden bo...@pterodactylus.net wrote:

 Hi,

 you’re right. I pushed a fix to next.



 Thanks David!

 Steve, can we get a -testing release on this please?  My build machine is
 fubared right now.  It is important that we get this tested and deployed
 before the remaining seednodes get updated and opennet falls apart.

 Thanks.

 It continues to be a problem that there are no seed node tests.

 Snapshot release:

 https://downloads.freenetproject.org/alpha/freenet-build01462-6-gaad73f6e603edd87b6cc7f79640b3748ac7e3eed-snapshot.jar
 https://downloads.freenetproject.org/alpha/freenet-build01462-6-gaad73f6e603edd87b6cc7f79640b3748ac7e3eed-snapshot.jar.sig

This seems to have fixed my node.  It is happily seeding again.


 The CHKs are inserting now.

 - Steve



 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Pretty sure 1462 is broken by commit 6d0321c1bbf96c593681719c8d4d0a63555d2e32

[Juiceman]

My seednode came online right before 1462 was released and was
seeding.  Since 1462 I have not seen a single seed client connect.  My
logs are full of:

Jun 02, 2014 02:22:12:164 (freenet.support.SerialExecutor$2, FNP
incoming auth packet handler thread(0), ERROR): Caught
java.lang.NullPointerException
java.lang.NullPointerException
at freenet.node.PeerNode.userToString(PeerNode.java:3819)
at freenet.node.PeerNode.init(PeerNode.java:624)
at freenet.node.SeedClientPeerNode.init(SeedClientPeerNode.java:20)
at 
freenet.node.FNPPacketMangler.getPeerNodeFromUnknownInitiator(FNPPacketMangler.java:1493)
at 
freenet.node.FNPPacketMangler.processJFKMessage3(FNPPacketMangler.java:1369)
at freenet.node.FNPPacketMangler.access$200(FNPPacketMangler.java:75)
at freenet.node.FNPPacketMangler$2.run(FNPPacketMangler.java:567)
at freenet.support.SerialExecutor$2.run(SerialExecutor.java:73)
at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:248)
at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:188)
at freenet.support.io.NativeThread.run(NativeThread.java:129)

https://github.com/freenet/fred-staging/commit/6d0321c1bbf96c593681719c8d4d0a63555d2e32
was getting rid of string concatenations, but looks like it did more than that.


src/freenet/node/PeerNode.java
@@ -3816,7 +3816,7 @@ public int selectNegType(OutgoingPacketMangler mangler) {

  }
   public String userToString() {
- return  + getPeer();
+ return  getPeer().toString();
  }

  public void setTimeDelta(long delta) {


are NOT functionally equivalent.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] What do nodes cost in bulk?

[Juiceman]

On Sat, Mar 29, 2014 at 3:08 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 On 29/03/14 15:26,
 adilson_lanpo@8AEGotJKXJ4ABJy1gKjls4SrrzpshQNoEMAbu0IFA94 wrote:

 On Sat, 29 Mar 2014 12:59:34 -
 toad-notrust@h2RzPS4fEzP0zU43GAfEgxqK2Y55~kEUNR01cWvYApI wrote:

 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256

 On 29/03/14 09:21,
 adilson_lanpo@8AEGotJKXJ4ABJy1gKjls4SrrzpshQNoEMAbu0IFA94 wrote:
 There's also a good chance that computing power to run nodes
 may well be more expensive than the fee to join freenet
 (especially if it as low as $5 as proposed in the OP).
 I very much doubt that this is the case. Computing power - CPU,
 bandwidth, CAPTCHAs, IP addresses, geeks, etc - have significant
 economies of scale, and are very cheap in bulk. Whereas the
 costs scale linearly if you have a pay-per-join scheme.
 Of course that pay to join fee only needs to be paid once while
 bandwidth and electricity is a recurring expense (admittedly ones
 that will decline in cost over time as lines get upgraded and
 computers get more efficient).

 For running 10,000 nodes (order of magnitude of current opennet)
 would thus only cost $50,000 under a $5 to join fee system, petty
 cash for basically any intelligence agency or even many medium
 sized companies and organized crime can surely steal that if they
 want to attack us for some reason.

 It's within the budget of some university research projects even,
 depending on what they hope to get out of it (e.g. there is some
 really expensive equipment). But the big questions are:
 1) Is the cost per node greater than $5 (or what we could plausibly
 ask of new users)?
 2) Do you need that many nodes? Can you just MAST? (See my other mail)

 Seriously, how many nodes can you run on one system? Especially
 if you can centralise the datastores and so on. And how much does
 it cost to buy *one* remote server with 1TB/mo transfer?
 Computing power is *very* cheap. Very much cheaper than a $5 per
 join fee for opennet IMHO, but if you want to look into the
 numbers then please do.
 You could probably fit a few nodes on a multi-GHz core but will
 need some serious memory, say a half a Gig for each node (assuming
 a minimal Linux VM for each node), if we go with a 4 core system
 and 3 minimal nodes on each core that is 6 GiB RAM, that's
 something like a pretty normal desktop system today.

 Have you tried it? What you need for a node with WoT and Sone and
 downloads is not the same as what you need for a node that's just
 routing, and our CPU usage for just routing is relatively low. Also
 there's some duplication. And on the subject of economies of scale, if
 you have more nodes, you can 1) hire geeks to improve performance and
 2) have a large shared datastore across many nodes.

 Also, you don't need a VM for each node. You can quite happily run
 them all on the same system image, even all in the same VM (which
 makes sharing a datastore easier).

 And memory is cheap.

 My suspicion is with a little coding you could probably run 100 nodes
 on one reasonably fast system, or a handful of them. Which is enough
 to connect to every node on opennet right now. Sadly I don't have time
 (or bandwidth) to try this, but if somebody wants to try that'd be a
 good thing.

 For 12 nodes I'm pretty sure it'll cost more than $5 per virtual
 node (can you buy quad core desktops for $60?).

 You can buy a reasonable server with 1TB/mo transfer for $70/mo IIRC,
 but I don't recall where. Anyone? Of course they will prohibit p2p,
 but whether they enforce this is less clear. And then there's
 connectivity - I mentioned the cost of unique IP addresses in my other
 mail.

 Partly it's a question of attacker modeling - do you want to
 constantly monitor everyone forever? Do you want to avoid getting
 caught at all costs? Do you know somebody's going to insert something
 sensitive soon (say this month) and you just want to catch them? Or if
 they will insert it in the very near future you could certainly use a
 botnet - how long do they last anyway on average?

 Using a bunch of R.Pi or similar may reduce costs though you won't
 be able to run as many nodes on them.

 It's probably more efficient to use big systems.

 Being able to fit more nodes on a core may help reduce costs,
 though memory usage is then going to become your bottleneck.

 Memory is pretty cheap.

 I'd be very interested in any serious estimates as to cost.

https://www.digitalocean.com/pricing/

Try $10/mo for 2TB transfer.  Root access - NO restrictions.  1 GB
RAM, single core virtual server, 30 GB SSD drive.  Could probably run
1 maybe 2 nodes per server.

$ 20 / mo
2GB Memory
2 Core Processor
40GB SSD Disk
3TB Transfer

$ 40 / mo
4GB Memory
2 Core Processor
60GB SSD Disk
4TB Transfer

$ 80 / mo   Maybe run 15+ nodes?  assuming ~512MB RAM per node
8GB Memory
4 Core Processor
80GB SSD Disk
5TB Transfer

So about $5-7 per node.


Please use this link if anyone signs up so I get credit for a referral
(this 

[freenet-dev] index format

[Juiceman]

Fyi, Freenet is using an ancient version of SnakeYAML.

Current version is 1.12
http://code.google.com/p/snakeyaml/wiki/changes

It might be worth looking into upgrading.

Sent from my wireless phone.
On Jul 20, 2013 6:51 AM, "Matthew Toseland" 
wrote:

> On Saturday 20 Jul 2013 09:47:06 Veronica Estrada wrote:
> > Hi Toad,
> >
> > Could you elaborate more on the actual index tree and on the notation
> > you use (for instance I guess for the chat with others that node could
> > mean different things). This documentation should be clear and we are
> > wasting lost of time because it is not.
>
> I've CC'ed devl for this. We should clean it up and put it into a text
> file in Library though, once it's all clear.
> >
> > Some questions are a bit confusing or repeated, but try to answer all
> > of them independently that will help to make the documentation clear.
> >
> >
> > A) Considering:
> >
> >
> http://127.0.0.1:/freenet:USK at 
> 2BYYFG4C1kJIRsiW9GhdlYMx52tQ06LXJuoC1TjX-EE,-fd9-wyD1WpfHPuNOMi4O8XhD9z78Dwu0uYO8TQy1FU,AQACAAE/index.yml/1?type=text/plain
> >
> >
> > 1)What is node_min? node_min=1024
> >
> > Is it the size of a node and when it reaches that size, it creates
> another node?
>
> It's the minimum size of a node in the btree. All nodes other than the
> root will be between node_min and node_max in size. node_max is 2*node_min.
> >
> > 2) What is a bin? Each entry line is a bin? I mean, each term is a bin?
>
> A bin is a separate insert which contains the detailed information
> (TermPageEntry's) for multiple terms.
> >
> > 3) All bins with the same URI (same id) make one node?
>
> No, bins are separate from nodes. Bins contain the detailed information
> for the TermPageEntry's associated with that node (if the node has
> children, these terms are the keys between the lower nodes).
>
> Within a term within a bin, each TermPageEntry has a relevance level, and
> if the term is enormous, we can split it up into sub-nodes. I.e. each term
> within the bin is actually a tree by relevance of TermPageEntry's. However
> most of the time the terms are small enough that we don't actually insert
> sub-nodes. So a bin is a separately inserted container consisting of a set
> of terms (keys, keywords) and for each one a tree by relevance of
> TermPageEntry's that match that term.
> >
> > 4) What do you call the top level tree, all the content in the file is
> > the top level tree? I mean, when you talk about "level" I am not sure
> > if you are talking about levels on the tree itself, root, 1 level, 2nd
> > level or you are talking about "nested trees". It will help if you can
> > also make a sketch draw. I can later clean the image, digitalise and
> > create a document that explain all this.
>
> The main tree:
> The USK. This is just a redirect.
> The top level node of the ttab tree.
> The bottom level node of the ttab tree. (The tree can have lots of levels)
>
> From each node within the main tree: (Because this is a btree not a b*tree
> as it should be):
> At least 1 bin.
> Within each bin: Term (keyword) -> relevance -> TermPageEntry
> (Most complex case has an extra level: Huge number of hits -> sub-nodes
> within a term, tree of relevance -> TermPageEntry)
> >
> > 4) The ttab (term table) structure maps a term to (the collection of
> > entries for that term)
>
> Right. Overall it creates a tree of:
> term (string) -> (relevance (float) -> TermPageEntry (detail for one hit))
> >
> > 4.1 Why ttab is empty in the index?
>
> It isn't. YAML uses indenting:
>
> ttab:
>   node_min: 1024
>   size: 240701
>   entries:
> 0axdu7jlnmmer9ucegf: !BinInfo { !FreenetURI
> 'CHK at 
> jc6tojQ3lGVpFcV90VfQDEQmdvgEcFrgzB9wtMZuL44,K9f8POu6NFaf~aZTvPrH1fkFwa6Vt2ZwZTAEv3zyEvY,AAMC--8':
> 1}
> '1249': !BinInfo {*id001: 6}
> ...
> >
> > 4.2 Do I need ttab?
>
> Yes.
> >
> >
> > 5) Subnodes
> >
> >
> > 5.1 All entries listed below "subnodes" are pointers to different
> > trees or they are just a children of the entries listed above?
>
> They are nodes. A node is a tree by definition. But they are not the root
> node.
> >
> > 5.2 The first submode line is
> >
> > !FreenetURI
> > 'CHK at CgUaGHkmu73R84Ip6BhHPOZXdH4eBe57l6G0E
> ~vVSFg,x8W8p~lHqhFt8UbjaGpIEBVpmbnVSOpOUiTxQXcRkLc,AAMC--8':
> > 1486
> >
> > What is this 1486? This number is repeated in other lines. Is it an
> > ID? Are lines with such number connected somehow? Or is the ID 148 and
> > the last number indicates something? All lines are 148 something.
>
> I *think* it's the number of elements in the subtree. If so the tree is
> impressively well balanced. It's certainly not an ID.
> >
> > 5.3 Each line is a subnode?
>
> Yes.
> >
> > 5.4 Subnodes of which tree, the top level tree?
>
> Subnodes of the node you are currently looking at. Which sit between the
> entries.
> >
> >
> > 6) Nested B-trees: Each FreenetURI in a subnode takes me to a
> > different nested B-tree?
>
> No, each term in a bin takes you to a different nested B-tree. However
> most of the 

[freenet-dev] Thoughts about Freenet deployment on Windows platforms.

[Juiceman]

Sent from my wireless phone.
On Jul 23, 2013 6:20 AM, "Matthew Toseland" 
wrote:
>
> On Tuesday 23 Jul 2013 11:01:16 Matthew Toseland wrote:
> > On Monday 22 Jul 2013 11:47:17 Rom. wrote:
> > > Hello,
> > >
> > > I would like to expose some thoughts about the current move for the
> > > deployment of Freenet on windows platforms.
> > >
> > > Currently as far as i understand, toad and operhiem1 are the only to
> > > maintain the windows installer of Freenet.
> > > This Freenet installer and all Freenet EXE (freenet.exe,
> > > freenetlauncher.exe ) are written in AutoHotKey.
> > >
> > > Due to its limitations (Unicode support) and recurrent false positives
> > > from anti viruses, it has been considered to move away from
AutoHotKey.
> > > Toad summarize thoughts here:
> > > https://bugs.freenetproject.org/view.php?id=5456#c9883.
> > >
> > > After reading this, i have started (with curiosity in mind) to work on
> > > an installer written with InnoSetup
> > > (https://github.com/freenet/wininstaller-staging/issues/12), which is
a
> > > true and dedicated software for creating installer for Windows.
> >
> > Right. This looks promising.
> > >
> > > But during this process and with some previous experiences related to
> > > Freenet on windows (https://bitbucket.org/romnbb/freenetfortraveler) a
> > > question came to my mind:
> > >
> > > Does Freenet needs an installer on Windows ?
> > >
> > > What this installer currently does :
> > > - Check port availability and writing settings in freenet.ini file
> > > before its first launch.
> > > - Determine how much ram to allocate to java (wrapper.java.maxmemory)
> > > - Extract all Freenet related files
> > >
> > > What if Freenet package is provided as a Zip file
> > > (Toad post: https://bugs.freenetproject.org/view.php?id=5842) and all
> > > pre-required settings handled, at a "First launch step", by the main
> > > program on windows : Freenet.exe (aka Freenet Tray) ?
> > >
> > > Upsides:
> > > - A simple zip file can easily fits the maintainability requirement.
> > > Files that change the most are related to the core of freenet
> > > (freenet.jar, plugins and maybe others) not those related to windows.
> > > - There is no doubts or problems creating zip files natively from
Linux.
> >
> > How will antiviruses deal with it? Will the file insight type thingies
still complain about it because it's not a file they've seen before? Or
will they only look at the files inside it? If a zip file bypasses the need
to deal with this, it'd be sensible; if not, it probably makes more sense
to have a discrete installer.
> >
> > One thing we've been considering is uploading to the website a few days
after we've uploaded to auto-update. All nodes download the installer, so
the file will at least be "visible", although it won't have been run. We
could even run it, with some no-op flag, but that would probably be more
trouble than it's worth.
> > >
> > > Downsides:
> > > - Users need to know what to do with this Zip file. That, most
probably,
> > > why Installers are commonly used on Windows : user will click, click ,
> > > click , click ... (without reading most of the time...)
> >
> > Right. It may make it a bit harder. Which is bad, and can only be
tolerated if it's offset by fewer problems with AV's.
> >
> > > - Handle of pre-settings must be ported to the main program
(freenet.exe).
> > >
> > > And with that come an other related question.
> > > If so, what to do about Freenet.exe (freenet tray), which is the
desktop
> > > interface between Users and Freenet main interface (freenet proxy).
> > > Keep using AutoHotKey ? Re-write it in another language (Java ?
> > > FreePascal ?).
> >
> > As far as AV's are concerned, AHK isn't ideal, but if they've seen the
file before they're less likely to complain about it; if these files are
updated infrequently, we can probably get away with it?
> > >
> > > Maybe i have missed some important things about this deployment on
> > > windows that can changed my thoughts if i am aware of.
> > >
> > > So, feedbacks are welcome.
> > >
> > >
> > > Whatever the direction taken, i will gladly help to maintain the
windows
> > > side of Freenet :) .
> >
> > Awesome!
> > >
> > > Best regards,
> > > Romain.
> > >
> > >
> > > PS: sorry if my english appears to be a bit "crude". It's not my
native
> > > language and long text doesn't help.
> >
> > Your english is fine above.
> >
> One other thing: For invites, we'd probably end up distributing a zip,
with some extra files, which the installer would recognise and deal with.
>
> So the big question is, will an AV always flag a foreign zip file, or
will it only concern itself with the executables inside that zip file?
>
>

I 'think' most AV look at executable files.  Exe, dll, pdf. Etc...

Also some look at heuristics such as trying to install in the autorun
section of the Windows registry.  If the installer platform is somewhat
mainstream it is easier.  I have seen InnoSetup before where as I had not
seen ahk 

Re: [freenet-dev] Freenet wish list

[Juiceman]

On Tue, Mar 19, 2013 at 2:15 AM, Madhawa Chandrasena
dilmadh...@gmail.com wrote:
 Hi,
 I'm computer science and Engineering student and I would like to contribute
 in Freenet developments. Can any one direct me where can I find Freenet wish
 list and any thing useful for my purpose.
 Thanks in advance.

 --
 Dilshan Madhawa Chandrasena
 Undergraduate (BSc Engineering)
 Department of Computer Science and Engineering
 University of Moratuwa
 Sri Lanka.

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Freenet bug-tracker would be a good place to get your feet wet.
https://bugs.freenetproject.org
Also larger projects:.
https://wiki.freenetproject.org/Google_Summer_of_Code/2013

CCing you in case you are not subscribed to the mailing list, which
you should be.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] coding in Freenet

[Juiceman]

On Nov 23, 2012 4:09 PM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 On Friday 23 Nov 2012 20:47:24 Simon Vocella wrote:
  Hi all,
 
  i have more questions after one my little refactoring:
 
  - Why you don't user a log4j or similar project to log?

 There's a lot we could move to third party code, it's an ongoing process,
e.g. we've started work on crypto recently.

 Re logging, we have fairly specialised requirements - even if we use a
standard logging API, we'd probably need our own rotation/compression code,
and we'd likely need other things too. E.g. we use logging quite a lot and
have it all in if(class specific boolean) { ... }. The reason for this is
generating the strings (and GCing them) can use a lot of CPU: it's vital
that if logging is turned off for that class then it not do *anything*.
There have been proposals to solve this in various less-ugly ways. Have a
look at the devl archives if interested. I'd be interested to know if any
of the standard logging solutions have an answer for this... Also, have a
look at the config in advanced mode for logging to get an idea of why we'd
need a custom logfile writer thread.

I just read about Blitz4j Netflix optimized version of log4j.  Supposedly
little to no performance impact under heavy logging due to asynchronous
code.

http://techblog.netflix.com/2012/11/announcing-bitz4j-scalable-logging.html

Hosted on github here
http://www.github.com/Netflix/blitz4j

 
  - The idea to use Apache Maven is worth with the guideline of Freenet?

 Security issues. Maven doesn't verify checksums/signatures when
downloading dependencies. And also we have quite a few anonymous
contributors, so downloading files during the build process is bad.
 
  - How can I test? There is a test suite?

 There is some junit coverage, the tests run during a normal build
(ant). However, most high-level classes don't have unit tests. There are
also some useful tools in freenet/node/simulator/ which run several nodes
inside one JVM and have them test various functions. We need more tests.
Most changes are tested by running a node ...
 
  Simon
 
  On Thu, Nov 22, 2012 at 9:46 AM, Simon Vocella vox...@gmail.com wrote:
 
   Hi Matthew! Thanks for the answer!
  
   I already builded Freenet! Now I'm going to help in some way :)
  
   Simon
  
  
   On Thu, Nov 22, 2012 at 12:46 AM, Matthew Toseland 
   t...@amphibian.dyndns.org wrote:
  
   On Monday 19 Nov 2012 07:55:22 Simon Vocella wrote:
Hi Steve,
   
I compiled all from the source, but why bcprov.jar and
freenet-ext.jar
   is
not in lib dir? license problem?
   
And why junit.jar is not in lib dir too?
  
   It's bad form to put jars in git repositories, since it keeps a full
   history. So you have to download it by hand. The ant script will
fetch it
   for you but that's off by default for security reasons, we have a few
   anonymous developers.
  
   Welcome aboard! Please ask any questions you need answering. You
should
   be able to find bcprov and freenet-ext.jar, if only from an existing
   Freenet install, but otherwise download bcprov from bouncycastle.org(the
1.5 provider) and freenet-ext.jar from
   downloads.freenetproject.org/alpha/
  
  
  
 

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Nextgens' invite idea

[Juiceman]

On Dec 18, 2012 8:26 AM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 On Tuesday 18 Dec 2012 02:49:36 Arne Babenhauserheide wrote:
  Am Freitag, 14. Dezember 2012, 19:32:18 schrieb Matthew Toseland:
   - HTTPS ensures that the executable hasn't been tampered with.
However, the
   friend providing it may be malicious, computer illiterate, or running
a
   corrupted build they got from another friend. Trusting your friend is
not
   necessarily enough here IMHO. - Therefore we want to verify the
signature
   from FPI as well.
 
  I don’t think that this is strictly necessary. If your friend runs a
corrupted
  build, you have a problem anyway. Another layer of security might be
nice,
  anyway, though: Don’t make it too easy for people to infiltrate freenet…

 The problem is you can make your corrupt version spread virally as
people are invited each time distributing your bogus installer, and get a
significant number of corrupted nodes. Verifying the signature avoids this
provided we can trust the PKI. Of course if Freenet is illegal we can't
trust the PKI. :(
 
  I like the zip-idea, though, because it would allow shipping more than
one
  installer: One for Windows, one for GNU/Linux and one for MacOSX.

 Right. And all three OS's have good support for zip's now.
 
  And we can provide the sha1 hash of the files along with
IP:Port:password, so
  GNU/Linux users can easily check for manipulations.

 We could, although it'd be more work for the user.
 
   One fundamental problem with QR codes is they're primarily read by
phones
   and tablets, which can't realistically run Freenet.
 
  It might be possible to prompt the user to send the URL via email to
their
  home-computer.
 
  In that case, the QR-code would simply save the typing of the text from
a
  custom business-card.

 Is that really an improvement in practice?
 
  Also people running freenet might not want to use their email address
to send
  the data: don’t leave a data trail between the two people (which is too
easy
  to follow).

 You should only add darknet friends if you don't care about there being a
trail between them. You should connect to people that you know. This is the
same as people the bad guys already know are connected to you from your
phone records etc.

 You are going to be connecting to them directly over IP, so if They look
at you individually, they can identify your friends. Like the message says
on the wizard, don't connect over darknet to your secret mole in guantanamo!

 Your friends do not have to be perfectly trustworthy. I'd be happy to add
people from the same university club. If you only add your direct family
you will not have enough links and there won't be enough long links. The
one case where you don't want to add them is when you have only ever
contacted them for the purpose of using Freenet, especially if it's an
automated system; this will ruin the topology, and they are probably
malicious.
 

What about some kind of Facebook app then?
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Automated seednode collection was: Depth-first announcement

[Juiceman]

On Nov 26, 2012 6:05 AM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 On Monday 26 Nov 2012 01:00:43 Juiceman wrote:
  We need more seednodes.  It would be nice if this could be more
  automated and best if it could be done within Freenet itself.
 
  Assumption:
  The official Freenet website will be shutdown or blocked
  someplaces\everywhere Toad (or other project maintainer\s) live
  someday in the future.  Development will need to go underground and
  from within Freenet itself.  These officials will need to stay
  anonymous.
  Seednode operators live somewhere more free or only development of
  Freenet is illegal and seednode operators are willing to accepted and
  make connections.

 If the main website is blocked, and you are distributing a single
official seednodes list, it's a fair assumption that the seednodes will
also be blocked. IMHO we should walk before we try to run. You could try to
avoid giving out all the seednodes, but that would mean dividing them up
somehow, probably using a central server, and even if you can avoid a
central server you would certainly need a way to partition it, e.g. by
email address or IP address. Both email addresses and IP addresses are
rather cheap, so just as with Tor, harvesting all the seednodes is likely
to be ridiculously easy. Having said that the chinese seem to have started
out by harvesting bridges via creating IP addresses and moved on to their
0day exploit that allows fingerprinting bridges directly; I'm assuming that
will be fixed soon so they'll be back to harvesting.

 Actually there's a good chance that opennet is blocked completely in such
a case. But it's very likely that the individual seednodes are.

 Only solution long-term is darknet.

 So main site is blocked but seednodes are not is a corner-case that may
be worth some effort, but not very much.
 

Ok, the proposal still has merits in the automation aspects...

  Problems:
  We need a way that lists of volunteers can be compiled by whoever is
  releasing the official Freenet USK (updates, seednodes list, etc)
  This method cannot be spammable.

 Seednodes that go down should be deleted automatically.
 Seednodes that don't connect should not be included in the first place.

  Need users to opt-in by giving us consent.
  Volunteers need to be able to remove themselves from the official
  seednodes if they want.
  Need to be able to test volunteers firewalls and obviously not from
  the computer of the official maintainer.
 
  Proposal:
  Official seednodes do this work for us!

 I agree. See my previous proposal, which included various advanced
verification features. Admittedly my proposal was rather complex, and I'm
hoping to implement something simple in the near future. Of course I don't
have time under Dec 6th, and if somebody else wants to take it on that'd be
awesome...
 
  Major changes to routing code required?
  Add a flag field to noderefs Seednode=true  If missing or 'false'
  this means a node is unwilling to volunteer.
  If not already implemented somewhere, all seednodes must insert a USK
  key (that can be polled by those that know the noderef\ARK) that
  contains a list of volunteers it has collected.  Easiest would be to
  use a field similar to ark.pubURI in the noderef pointing to a USK.
 
  Implementation:
  When a node with Seednode=true has been up and connected for 15
  minutes it starts accepting announcements from connecting nodes. The
  15 minutes gives it time to settle in. Next it polls the official
  Freenet USK and checks if it is on the official seednode list.  If yes
  it is an 'official seednode'.

 Is this the USK that is used by auto-update, that is uploaded only on a
release? Or something else?


Your call.

  *The remainder of this email will only talk about official seednodes.*
 
  When a seednode accepts a newbie node for announcement it checks if
  that newbie node has its Seednode=true flag set.

 The flag should only be set if the node thinks it is eligible (it's port
forwarded and has sufficient uptime and bandwidth), and the user has opted
in. If the node thinks it is port forwarded and hasn't asked the user it
should ask the user. Whatever they say, once they have answered, we don't
ask again.

 Another problem is a node won't have the seednode flag set when it first
announces. And if it's a good, high uptime node, like we want, we may need
it to contact the seednodes without doing a normal announcement, just to
add itself.

Well, the user obviously hasn't used Freenet yet enough to decide to be a
seednode.  After they select the option, the very next time they announce
they will be picked up.


  If yes it puts this node on a list of potential volunteers.
  After 30 minutes of not being connected to each volunteer:
  The seednode tries to connect to the volunteer to test its firewall
  and that it accepts an announcement attempt. If everything looks good
  it adds this node to a list of volunteer nodes that can be inserted

[freenet-dev] Automated seednode collection was: Depth-first announcement

[Juiceman]

We need more seednodes.  It would be nice if this could be more
automated and best if it could be done within Freenet itself.

Assumption:
The official Freenet website will be shutdown or blocked
someplaces\everywhere Toad (or other project maintainer\s) live
someday in the future.  Development will need to go underground and
from within Freenet itself.  These officials will need to stay
anonymous.
Seednode operators live somewhere more free or only development of
Freenet is illegal and seednode operators are willing to accepted and
make connections.

Problems:
We need a way that lists of volunteers can be compiled by whoever is
releasing the official Freenet USK (updates, seednodes list, etc)
This method cannot be spammable.
Need users to opt-in by giving us consent.
Volunteers need to be able to remove themselves from the official
seednodes if they want.
Need to be able to test volunteers firewalls and obviously not from
the computer of the official maintainer.

Proposal:
Official seednodes do this work for us!

Major changes to routing code required?
Add a flag field to noderefs "Seednode=true"  If missing or 'false'
this means a node is unwilling to volunteer.
If not already implemented somewhere, all seednodes must insert a USK
key (that can be polled by those that know the noderef\ARK) that
contains a list of volunteers it has collected.  Easiest would be to
use a field similar to ark.pubURI in the noderef pointing to a USK.

Implementation:
When a node with "Seednode=true" has been up and connected for 15
minutes it starts accepting announcements from connecting nodes. The
15 minutes gives it time to settle in. Next it polls the official
Freenet USK and checks if it is on the official seednode list.  If yes
it is an 'official seednode'.
*The remainder of this email will only talk about official seednodes.*

When a seednode accepts a newbie node for announcement it checks if
that newbie node has its "Seednode=true" flag set.
If yes it puts this node on a list of potential volunteers.
After 30 minutes of not being connected to each volunteer:
The seednode tries to connect to the volunteer to test its firewall
and that it accepts an announcement attempt. If everything looks good
it adds this node to a list of volunteer nodes that can be inserted
into the network. The reason we wait 30 minutes is to give the new
volunteers time to settle into the network and make sure they stuck
around.

Seednodes insert their list of volunteers (hourly? daily?) to a USK
key that can be polled by whoever is creating and inserting the
official project USK seednodes list. This central person\node can
compile a list from all the official seednodes and this central
person\node can poll the volunteers arks and the "Seednode=true" flag
to determine when to add or remove a seednode from the official
seednodes list. If a node turns their "Seednode=true" flag to false
then volunteers can come and go as needed.



Something similar can be used to anonymously(to the maintainer)
determine if an official seednode is defunct:  Have official seednodes
ping each other every so often and insert that info into a USK with
'last uptime' for each seednode.  The maintainer can poll this info
and remove seednodes from the official list based on whatever criteria
he\she wants.



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

Re: [freenet-dev] Depth-first announcement

[Juiceman]

On Thu, Nov 22, 2012 at 10:54 AM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 On Thursday 22 Nov 2012 00:22:25 Juiceman wrote:
 Sent from my wireless phone.
 On Nov 21, 2012 6:55 PM, Matthew Toseland t...@amphibian.dyndns.org
 wrote:
 
  On Monday 19 Nov 2012 16:09:02 Juiceman wrote:
   Sent from my wireless phone.
   On Nov 19, 2012 10:24 AM, Juiceman juicema...@gmail.com wrote:
   
Idea for automated seednode collection:
   
Could official seednodes pass a list of second tier seednodes that
   newbies can try to connect to when official nodes are overloaded?
   
Implementation:
   
When an official seednode accepts a newbie node for announcement it
   checks if that node has its be a seednode flag set.  It puts this
 node on
   a list of potential volunteers.
   
After 30 minutes of not being connected to the volunteer:
The official seednode then tries to connect to the newbie to test its
   firewall and that it accepts an announcement attempt.  If everything
 looks
   good it adds this node to a list of volunteer nodes that can be doled
 out
   to the future newbies that connect.
  
   Clarification: the reason we wait 30 minutes is to give the new
 volunteers
   time to settle into the network and make sure they stuck around.
  
   I suggest we make it so volunteers can't dole out their own list of
   sub-volunteers somehow or else routing will be fubared.  Perhaps when
   volunteer nodes get connected they fetch the latest list of official
   seednodes from Freenet and if they are not on it disable handing out
 their
   list of their own volunteers.
  
   Let's make it so seednodes don't hand out second tiers until they
   themselves have been up for 30 minutes.  This gives time to check
 whether
   they are official seednodes and settle into the network.  Seednodes
 should
   not persist their volunteer list past shutdown so they collect fresh
   volunteers and don't hand out ancient lists.
 
  Interesting. Isn't it better to only have mature nodes, with good
 connections, fast bandwidth, and so on? There are probably a lot more such
 nodes than are in the seednodes list at the moment.
 
  I do think the user should be asked if we add them to the seednodes.
 
  Also, what is the point of secondary nodes anyway if they're not gonna be
 in the main list? I mean once you've connected to a primary seednode you
 can announce through that - this is added to your seednodes list for backup
 purposes for later on? One problem with that is it would increase the
 Internet Background Radiation impact of Freenet, since we don't know when
 the secondary seednode goes down; with the main seednodes, we update the
 list, and hopefully we will soon update it even when we are behind the
 latest version (using UOM).

 This would be an automated system that wouldn't require users emailing
 someone to add them to the list.

 At the moment the plan is to detect when a node is eligible to be a seednode, 
 ask the user to configure it, and then periodically contact a central server.

Long term we need something better than your plan (or my idea) like
inserting to a central node within Freenet.  Enhancement to my idea:
Perhaps official seednodes could insert their list of volunteers to a
USK key (listed in their ark?) that could be polled by whoever is
creating and inserting the official project USK seednodes list.  This
central person\node can compile a list from all the official
seednodes.  If the seednode flag was part of a noderef, then this
central person\node can poll the volunteers arks and this flag to
determine when to add or remove a volunteer from the official
seednodes list.  Then volunteers can come and go as needed.

I will actual start a new email thread and rewrite this as a more
coherent proposal.  Stay tuned.


 If they have selected the checkbox to be a seednode aren't they opting in?

 How long does an announcement take to complete so the seednode can
 disconnect?   If a seednode could say i'm overloaded, here are some other
 seednodes in a quick message to some of the nodes waiting to announce it
 would help, no?

 Maybe. It would be a bit faster, but more complex. Wouldn't it just be better 
 to have a single global seednodes list with more nodes in? We can always 
 slice it up for individual installs.

 The seednodes forget the volunteer list on shutdown so those nodes won't
 keep getting spammed.  Also the official seednode could rotate the list it
 hands out.

 So the recipient tries to connect to it and then eventually gives up and 
 forgets it? It doesn't store the references for the alternates?

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben

Re: [freenet-dev] Depth-first announcement

[Juiceman]

Sent from my wireless phone.
On Nov 21, 2012 6:55 PM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 On Monday 19 Nov 2012 16:09:02 Juiceman wrote:
  Sent from my wireless phone.
  On Nov 19, 2012 10:24 AM, Juiceman juicema...@gmail.com wrote:
  
   Idea for automated seednode collection:
  
   Could official seednodes pass a list of second tier seednodes that
  newbies can try to connect to when official nodes are overloaded?
  
   Implementation:
  
   When an official seednode accepts a newbie node for announcement it
  checks if that node has its be a seednode flag set.  It puts this
node on
  a list of potential volunteers.
  
   After 30 minutes of not being connected to the volunteer:
   The official seednode then tries to connect to the newbie to test its
  firewall and that it accepts an announcement attempt.  If everything
looks
  good it adds this node to a list of volunteer nodes that can be doled
out
  to the future newbies that connect.
 
  Clarification: the reason we wait 30 minutes is to give the new
volunteers
  time to settle into the network and make sure they stuck around.
 
  I suggest we make it so volunteers can't dole out their own list of
  sub-volunteers somehow or else routing will be fubared.  Perhaps when
  volunteer nodes get connected they fetch the latest list of official
  seednodes from Freenet and if they are not on it disable handing out
their
  list of their own volunteers.
 
  Let's make it so seednodes don't hand out second tiers until they
  themselves have been up for 30 minutes.  This gives time to check
whether
  they are official seednodes and settle into the network.  Seednodes
should
  not persist their volunteer list past shutdown so they collect fresh
  volunteers and don't hand out ancient lists.

 Interesting. Isn't it better to only have mature nodes, with good
connections, fast bandwidth, and so on? There are probably a lot more such
nodes than are in the seednodes list at the moment.

 I do think the user should be asked if we add them to the seednodes.

 Also, what is the point of secondary nodes anyway if they're not gonna be
in the main list? I mean once you've connected to a primary seednode you
can announce through that - this is added to your seednodes list for backup
purposes for later on? One problem with that is it would increase the
Internet Background Radiation impact of Freenet, since we don't know when
the secondary seednode goes down; with the main seednodes, we update the
list, and hopefully we will soon update it even when we are behind the
latest version (using UOM).



This would be an automated system that wouldn't require users emailing
someone to add them to the list.

If they have selected the checkbox to be a seednode aren't they opting in?

How long does an announcement take to complete so the seednode can
disconnect?   If a seednode could say i'm overloaded, here are some other
seednodes in a quick message to some of the nodes waiting to announce it
would help, no?

The seednodes forget the volunteer list on shutdown so those nodes won't
keep getting spammed.  Also the official seednode could rotate the list it
hands out.
___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Depth-first announcement

[Juiceman]

Idea for automated seednode collection:

Could official seednodes pass a list of second tier seednodes that newbies
can try to connect to when official nodes are overloaded?

Implementation:

When an official seednode accepts a newbie node for announcement it checks
if that node has its be a seednode flag set.  It puts this node on a list
of potential volunteers.

After 30 minutes of not being connected to the volunteer:
The official seednode then tries to connect to the newbie to test its
firewall and that it accepts an announcement attempt.  If everything looks
good it adds this node to a list of volunteer nodes that can be doled out
to the future newbies that connect.

Sent from my wireless phone.
On Nov 19, 2012 7:42 AM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 I have merged Robert's original patch (compile fixed) for depth-first
 announcement onto a branch, opennet-changes.

 It will need to be tested thoroughly:
 - Do new nodes announce with new seeds?
 - Do new nodes announce with old seeds?
 - Do old nodes announce with new seeds?
 (Note that Update Over Mandatory relies on announcement, as well as
 announcing existing nodes)

 However, it is a very small patch, and since we wait for transfers to
 complete *after* we call addRefIfWanted(), it should be okay.

 IMHO the theoretical justification for this patch is more than adequate:
 - The nodes at the end of the announcement path should reply first. They
 are much less likely to be overloaded.
 - They are also closer to the target location, so announcement should be
 more effective.

 However, I suspect the difference in practice will be nil:
 - We will receive the same set of announcement offers, just backwards.
 - We will accept all of them because we are a newbie, and normally we get
 rather fewer announcement offers than our connection limit.

 = Getting more seednodes (preferably via an automated process) is more
 important.

 Thoughts?

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Depth-first announcement

[Juiceman]

Sent from my wireless phone.
On Nov 19, 2012 10:24 AM, Juiceman juicema...@gmail.com wrote:

 Idea for automated seednode collection:

 Could official seednodes pass a list of second tier seednodes that
newbies can try to connect to when official nodes are overloaded?

 Implementation:

 When an official seednode accepts a newbie node for announcement it
checks if that node has its be a seednode flag set.  It puts this node on
a list of potential volunteers.

 After 30 minutes of not being connected to the volunteer:
 The official seednode then tries to connect to the newbie to test its
firewall and that it accepts an announcement attempt.  If everything looks
good it adds this node to a list of volunteer nodes that can be doled out
to the future newbies that connect.

Clarification: the reason we wait 30 minutes is to give the new volunteers
time to settle into the network and make sure they stuck around.

I suggest we make it so volunteers can't dole out their own list of
sub-volunteers somehow or else routing will be fubared.  Perhaps when
volunteer nodes get connected they fetch the latest list of official
seednodes from Freenet and if they are not on it disable handing out their
list of their own volunteers.

Let's make it so seednodes don't hand out second tiers until they
themselves have been up for 30 minutes.  This gives time to check whether
they are official seednodes and settle into the network.  Seednodes should
not persist their volunteer list past shutdown so they collect fresh
volunteers and don't hand out ancient lists.


 On Nov 19, 2012 7:42 AM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 I have merged Robert's original patch (compile fixed) for depth-first
announcement onto a branch, opennet-changes.

 It will need to be tested thoroughly:
 - Do new nodes announce with new seeds?
 - Do new nodes announce with old seeds?
 - Do old nodes announce with new seeds?
 (Note that Update Over Mandatory relies on announcement, as well as
announcing existing nodes)

 However, it is a very small patch, and since we wait for transfers to
complete *after* we call addRefIfWanted(), it should be okay.

 IMHO the theoretical justification for this patch is more than adequate:
 - The nodes at the end of the announcement path should reply first.
They are much less likely to be overloaded.
 - They are also closer to the target location, so announcement should be
more effective.

 However, I suspect the difference in practice will be nil:
 - We will receive the same set of announcement offers, just backwards.
 - We will accept all of them because we are a newbie, and normally we
get rather fewer announcement offers than our connection limit.

 = Getting more seednodes (preferably via an automated process) is more
important.

 Thoughts?

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Should we move to 128-bit link encryption?

[Juiceman]

I tend to think seednodes are more likely bound by bandwidth constraints
than CPU, at least the one I run.  However I agree that the packet size
going over the MTU is a dealbreaker.

Sent from my wireless phone.
On Nov 16, 2012 7:04 AM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 Nextgens is making some largish changes to connection setup and link
 encryption, to improve security and performance.

 Nextgens wants to use 128-bit AES for link encryption, on the theory that:
 1) On opennet, even with the optimisations we have proposed, there are
 much easier attacks than breaking AES128.
 2) Even on darknet that's still probably true.
 3) Using AES256 properly would require using secp521r1 (or at least
 secp384r1) for connection setup (currently we use 2048-bit DSA, we are
 about to switch to using ECDSA with secp256r1; see keylength.com).
 4) secp521r1 is 10x slower than secp256r1. So on opennet seednodes, CPU
 usage for handshaking would be a problem. We can maybe reduce this a bit by
 using a lot more seednodes. Also, we can reduce CPU usage for ECDH
 dramatically by using NSS, although it's ugly due to bugs that haven't been
 fixed in years; arguably we shouldn't be using code that is effectively
 unmaintained, but the other side of the argument is it's just Sun's glacial
 release cycle (bugs in the Java side of NSS are mostly fixed in Java 1.7).
 5) For opennet initial connection setup with a seednode, packets would
 have to increase in size by about 415 bytes. This might well push them over
 the MTU; the anonymous initiator packets are already rather large.
 Reassembling connection setup packets ourselves is a bad idea, and sending
 packets over the MTU is dangerous - that is, they get dropped across most
 of the internet.
 6) We could support 128-bit crypto for opennet and 256-bit crypto for
 darknet (possibly configurable by the user, although I doubt 256-bit is
 possible on opennet due to packet size issues). This would solve most of
 these problems, but would involve more code complexity. Nextgens is opposed
 to it for this reason.

 Currently we use Rijndael with 256-bit key and 256-bit block size (and
 2048-bit DSA). AES is Rijndael with 128-bit block size; we should use the
 standard, but that doesn't settle what key length to use. Using ECDSA is
 necessary because a bigger DSA would make for very large packets, and in
 any case ECC is preferable for both security and performance.

 ___
 Devl mailing list
 Devl@freenetproject.org
 https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] [website-official] Add a link to gun.io (#1)

[Juiceman]

Forwarding to devl list

On Sat, Apr 7, 2012 at 12:13 PM, Steve Dougherty

wrote:
> As far as I'm aware, the gun.io tasks are unofficial. I could see a link 
> going on the wiki, but not the website menu. Thoughts?
>
> Pull requests should go to website-staging; deploys are made from 
> website-official.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/freenet/website-official/pull/1#issuecomment-5009692

Agreed on the website-staging.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

Re: [freenet-dev] [website-official] Add a link to gun.io (#1)

[Juiceman]

Forwarding to devl list

On Sat, Apr 7, 2012 at 12:13 PM, Steve Dougherty
reply+i-3536451-8cb4f7b814a0b85d0d0fbb8939b6faae056b128c-77...@reply.github.com
wrote:
 As far as I'm aware, the gun.io tasks are unofficial. I could see a link 
 going on the wiki, but not the website menu. Thoughts?

 Pull requests should go to website-staging; deploys are made from 
 website-official.

 ---
 Reply to this email directly or view it on GitHub:
 https://github.com/freenet/website-official/pull/1#issuecomment-5009692

Agreed on the website-staging.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Promiscuous opennet

[Juiceman]

Should we do something about the amount of announcements/refs handed
out?? Seems a good way to harvest opennet (known problem, but perhaps
we could slow it down...) or perhaps monopolize/monitor the key-space
somehow?

opennetSizeEstimateSession:?18985?nodes
opennetSizeEstimate24h:   ?12435?nodes
opennetSizeEstimate48h:?   14855?nodes
nodeUptimeSession:?  4d23h


Seed stats
IPConnected  Announced  Accepted  Completed  Sent
refsVersion
24.126.77.671766352352352
  5201406
202.134.203.35 1785279279279
 1812  1377
213.134.163.3   1792275275275
  1819  1388
68.227.101.68   1793293293293
  1747  1389
62.107.42.7   1803257257257
1774  1389
67.61.122.2461840267267267
   1809 1397
82.66.7.51 1843247247247
 1400  1397
78.105.55.2061846290290290
   2053  1388
68.144.7.7 1853438438438
 1481406
80.217.175.104  1868314314314
  2053  1388
67.169.243.331919317317317
   4161406
208.76.88.92  1939327327327
1980  1376
98.21.244.1131951317317317
   2238  1376
50.4.40.1461979308308308
 2106  1385
71.204.143.231   2041292292292
   1629  1385
81.56.65.622043278278278
 2209  1384
88.174.162.112   2071297297297
   2104  1378
88.90.64.247  2110278278278
1658  1397
88.172.49.91  2120305305305
1730  1372
69.228.173.126   2146318318318
   2247  1364


--
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

[freenet-dev] Promiscuous opennet

[Juiceman]

Should we do something about the amount of announcements/refs handed
out?  Seems a good way to harvest opennet (known problem, but perhaps
we could slow it down...) or perhaps monopolize/monitor the key-space
somehow?

opennetSizeEstimateSession: 18985 nodes
opennetSizeEstimate24h:    12435 nodes
opennetSizeEstimate48h:    14855 nodes
nodeUptimeSession:   4d23h


Seed stats
IPConnected  Announced  Accepted  Completed  Sent
refsVersion
24.126.77.671766352352352
  5201406
202.134.203.35 1785279279279
 1812  1377
213.134.163.3   1792275275275
  1819  1388
68.227.101.68   1793293293293
  1747  1389
62.107.42.7   1803257257257
1774  1389
67.61.122.2461840267267267
   1809 1397
82.66.7.51 1843247247247
 1400  1397
78.105.55.2061846290290290
   2053  1388
68.144.7.7 1853438438438
 1481406
80.217.175.104  1868314314314
  2053  1388
67.169.243.331919317317317
   4161406
208.76.88.92  1939327327327
1980  1376
98.21.244.1131951317317317
   2238  1376
50.4.40.1461979308308308
 2106  1385
71.204.143.231   2041292292292
   1629  1385
81.56.65.622043278278278
 2209  1384
88.174.162.112   2071297297297
   2104  1378
88.90.64.247  2110278278278
1658  1397
88.172.49.91  2120305305305
1730  1372
69.228.173.126   2146318318318
   2247  1364


--
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Coding standards

[Juiceman]

On Mar 30, 2012 1:12 PM, "Matthew Toseland" 
wrote:
>
> On Sunday 25 Mar 2012 19:33:45 Juiceman wrote:
> > On Mon, Mar 19, 2012 at 6:13 PM, Marco Schulze
> >  wrote:
> > > May I add a vote to standardise indentation? This mess of spaces with
tabs
> > > really bugs me.
> > >
> >
> > Assuming tabs 8 spaces wide the current code yields 9,187 lines with
> > warnings about being longer than 120 chars.
>
> Doesn't eclipse use 4 space tabs by default?
>

I think so, but that is not what our wiki says is freenets standard
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20120330/3b5ab257/attachment.html>

Re: [freenet-dev] Coding standards

[Juiceman]

On Mar 30, 2012 1:12 PM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 On Sunday 25 Mar 2012 19:33:45 Juiceman wrote:
  On Mon, Mar 19, 2012 at 6:13 PM, Marco Schulze
  marco.c.schu...@gmail.com wrote:
   May I add a vote to standardise indentation? This mess of spaces with
tabs
   really bugs me.
  
 
  Assuming tabs 8 spaces wide the current code yields 9,187 lines with
  warnings about being longer than 120 chars.

 Doesn't eclipse use 4 space tabs by default?


I think so, but that is not what our wiki says is freenets standard
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Coding standards

[Juiceman]

On Mon, Mar 19, 2012 at 6:13 PM, Marco Schulze
 wrote:
> May I add a vote to standardise indentation? This mess of spaces with tabs
> really bugs me.
>

Assuming tabs 8 spaces wide the current code yields 9,187 lines with
warnings about being longer than 120 chars.

Re: [freenet-dev] Coding standards

[Juiceman]

On Mon, Mar 19, 2012 at 6:13 PM, Marco Schulze
marco.c.schu...@gmail.com wrote:
 May I add a vote to standardise indentation? This mess of spaces with tabs
 really bugs me.


Assuming tabs 8 spaces wide the current code yields 9,187 lines with
warnings about being longer than 120 chars.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] GSoC: is experience with security a necessity?

[Juiceman]

On Tue, Mar 13, 2012 at 9:58 PM, Kieran Donegan wrote:

> Hi,
>
> I'm a second year BSc Computer Science student in University College Cork,
> Ireland. Freenet's development goals really resonate with me and I'd love
> to help enhance Freenet for GSoC this year. My Java skills are excellent
> and I have a good knowledge of application layer and transport layer
> networking protocols. My security knowledge however is basic to
> non-existent. Being that security is one of the main concerns when
> operating a service like Freenet would I be hopeless in contributing to the
> project? I have a keen interest to learn however and would appreciate some
> pointers on how to get started before GSoC kicks off.
>
> Regards,
> Kieran
>
>
There are many areas of Freenet development that can benefit from a good
Java coder, most don't require any security knowledge.  For the most part,
the heavy lifting (crypto, hashing, etc) is taken care of for you.

Check out http://new-wiki.freenetproject.org/Google_Summer_of_Code/2012
for places to start!  :)

-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] GSoC: is experience with security a necessity?

[Juiceman]

On Tue, Mar 13, 2012 at 9:58 PM, Kieran Donegan kdonegan...@gmail.comwrote:

 Hi,

 I'm a second year BSc Computer Science student in University College Cork,
 Ireland. Freenet's development goals really resonate with me and I'd love
 to help enhance Freenet for GSoC this year. My Java skills are excellent
 and I have a good knowledge of application layer and transport layer
 networking protocols. My security knowledge however is basic to
 non-existent. Being that security is one of the main concerns when
 operating a service like Freenet would I be hopeless in contributing to the
 project? I have a keen interest to learn however and would appreciate some
 pointers on how to get started before GSoC kicks off.

 Regards,
 Kieran


There are many areas of Freenet development that can benefit from a good
Java coder, most don't require any security knowledge.  For the most part,
the heavy lifting (crypto, hashing, etc) is taken care of for you.

Check out http://new-wiki.freenetproject.org/Google_Summer_of_Code/2012
for places to start!  :)

-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Gun.io

[Juiceman]

On Sat, Feb 11, 2012 at 8:41 PM, Evan Daniel  wrote:

> On Mon, Jan 16, 2012 at 6:20 PM, Evan Daniel  wrote:
> > On Mon, Jan 16, 2012 at 11:46 AM, Ian Clarke 
> wrote:
> >> On Sun, Jan 15, 2012 at 9:17 PM, Evan Daniel  wrote:
> >>>
> >>> Dumb question time: how would I go about searching for hypothetical
> >>> freenet tasks on gun.io?
> >>
> >>
> >> Right now there are only 10 open source gigs listed:
> http://gun.io/open/
> >>
> >> I think we'd probably need to attract attention to any gigs we list,
> perhaps
> >> with an appropriate post on reddit.com/r/programming.
> >>
> >>>
> >>> Can anyone post a job for Freenet, or only project admins? How is
> >>> payment handled?
> >>
> >>
> >> Perhaps Rich can answer this or provide a pointer to an explanation.
> >>
> >>>
> >>> Also, if it works, I think this would be an excellent use of FPI money.
> >>
> >>
> >> I agree, especially since Matthew isn't burning too many hours on
> Freenet
> >> these days.
> >
> > I haven't actually tried posting a gig, but I'd be happy to set up a
> > few issues as tests, including putting up a little cash for bounties.
> > I'll do that tonight or tomorrow depending on time.
> >
> > Is there a way for additional people to add money to an open source
> > gig? Eg, if I set up an issue with a $30 bounty, can someone else add
> > another $30 to the same gig easily?
> >
> > Evan
>
> OK, I created a pair of simple Freenet gigs. If it works, I might post
> more.
> http://gun.io/open/30/freenet-node-diagnostics-page
> http://gun.io/open/31/fix-freenet-network-usage-stats
>
> To answer my own questions:
>
> I don't see any way to search. Anyone can post a gig for any project.
> Anyone can add more money to an existing gig.
>
> All in all, it looks simple and effective. Neat.


I added a little money to one of your projects.  It all adds up, right?  :)

Should we put a link to gun.io freenet projects from the main freenet
website, perhaps under the "Donate" tab call it "Post a bounty!" ?


-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] Gun.io

[Juiceman]

On Sat, Feb 11, 2012 at 8:41 PM, Evan Daniel eva...@gmail.com wrote:

 On Mon, Jan 16, 2012 at 6:20 PM, Evan Daniel eva...@gmail.com wrote:
  On Mon, Jan 16, 2012 at 11:46 AM, Ian Clarke i...@freenetproject.org
 wrote:
  On Sun, Jan 15, 2012 at 9:17 PM, Evan Daniel eva...@gmail.com wrote:
 
  Dumb question time: how would I go about searching for hypothetical
  freenet tasks on gun.io?
 
 
  Right now there are only 10 open source gigs listed:
 http://gun.io/open/
 
  I think we'd probably need to attract attention to any gigs we list,
 perhaps
  with an appropriate post on reddit.com/r/programming.
 
 
  Can anyone post a job for Freenet, or only project admins? How is
  payment handled?
 
 
  Perhaps Rich can answer this or provide a pointer to an explanation.
 
 
  Also, if it works, I think this would be an excellent use of FPI money.
 
 
  I agree, especially since Matthew isn't burning too many hours on
 Freenet
  these days.
 
  I haven't actually tried posting a gig, but I'd be happy to set up a
  few issues as tests, including putting up a little cash for bounties.
  I'll do that tonight or tomorrow depending on time.
 
  Is there a way for additional people to add money to an open source
  gig? Eg, if I set up an issue with a $30 bounty, can someone else add
  another $30 to the same gig easily?
 
  Evan

 OK, I created a pair of simple Freenet gigs. If it works, I might post
 more.
 http://gun.io/open/30/freenet-node-diagnostics-page
 http://gun.io/open/31/fix-freenet-network-usage-stats

 To answer my own questions:

 I don't see any way to search. Anyone can post a gig for any project.
 Anyone can add more money to an existing gig.

 All in all, it looks simple and effective. Neat.


I added a little money to one of your projects.  It all adds up, right?  :)

Should we put a link to gun.io freenet projects from the main freenet
website, perhaps under the Donate tab call it Post a bounty! ?


-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Website traffic increased substantially

[Juiceman]

On Tue, Jan 24, 2012 at 1:22 PM, Michael Grube wrote:

>
>
> On Tue, Jan 24, 2012 at 12:34 PM, Robert Hailey  > wrote:
>
>>
>> On 2012/01/23 (Jan), at 8:21 AM, Martin 'The Bishop' Scheffler wrote:
>>
>> > well, i see the megaupload-bust as a second factor to that.
>> > we should thank the FBI for pushing users in our direction :-)
>>
>> And then we should push development of freenet into freenet itself before
>> the FBI comes in our direction. :-)
>>
>
> =/
>
> Development alone will not save us.
>
> With a sufficient set of arguments and PR, we should be able not only to
> keep the FBI at bay, but even portray ourselves as people who are doing
> good(because we are!). This is exactly how WikiLeaks protected themselves
> before they got really big. They were very practiced at answering 
> *all*counterarguments to their activities. I have seen a good deal of
> development and tech support discussion in #freenet, but I have not seen a
> proportionate amount of legal and social defenses.
>
> Maybe it would be possible to make friends with the EFF or ACLU? I'm not
> sure how we'd get the help we may need.
>
>
Could we at least get an update on the front page that is newer than 13th
April 2011 please?  If I didn't know better I would think this project was
abandoned...
Maybe a link to somewhere advising folks to read up on SOPA or other
Internet blacklist activities?
Perhaps:

"Freenet is becoming more necessary every day.  We recommend reading up on
laws that may affect you, such as
https://www.eff.org/deeplinks/Internet-Blacklist-Legislation;

-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] Website traffic increased substantially

[Juiceman]

On Tue, Jan 24, 2012 at 1:22 PM, Michael Grube michael.gr...@gmail.comwrote:



 On Tue, Jan 24, 2012 at 12:34 PM, Robert Hailey rob...@freenetproject.org
  wrote:


 On 2012/01/23 (Jan), at 8:21 AM, Martin 'The Bishop' Scheffler wrote:

  well, i see the megaupload-bust as a second factor to that.
  we should thank the FBI for pushing users in our direction :-)

 And then we should push development of freenet into freenet itself before
 the FBI comes in our direction. :-)


 =/

 Development alone will not save us.

 With a sufficient set of arguments and PR, we should be able not only to
 keep the FBI at bay, but even portray ourselves as people who are doing
 good(because we are!). This is exactly how WikiLeaks protected themselves
 before they got really big. They were very practiced at answering 
 *all*counterarguments to their activities. I have seen a good deal of
 development and tech support discussion in #freenet, but I have not seen a
 proportionate amount of legal and social defenses.

 Maybe it would be possible to make friends with the EFF or ACLU? I'm not
 sure how we'd get the help we may need.


Could we at least get an update on the front page that is newer than 13th
April 2011 please?  If I didn't know better I would think this project was
abandoned...
Maybe a link to somewhere advising folks to read up on SOPA or other
Internet blacklist activities?
Perhaps:

Freenet is becoming more necessary every day.  We recommend reading up on
laws that may affect you, such as
https://www.eff.org/deeplinks/Internet-Blacklist-Legislation;

-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Internet SOPA blackout

[Juiceman]

Anyway we can get something on our webpage?
-- next part --
An HTML attachment was scrubbed...
URL: 

[freenet-dev] Internet SOPA blackout

[Juiceman]

Anyway we can get something on our webpage?
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] [RFC] Allow more people to release a Freenet build

[Juiceman]

On Sun, Nov 6, 2011 at 3:11 PM, David ?Bombe? Roden  wrote:

> **
>
> Hi Matthew,
>
> > Also we could have many "streams" of test builds, by different
> developers,
>
> > and thus let them release whatever they want to without it being
>
> > officially endorsed, but the users still be able to use the update.sh
>
> >  / update.cmd  conveniently.
>
> That would require quite some trickery in the update scripts, especially
> in the Windows version of it, I guess.
>

Not really.  Just need to make the download path a variable that is set at
the beginning of the script.  I could do the Windows script in less than an
hour once decided how the files are named and where they are kept.


>  > True. Eventually we need real builds. Right now me, Ian and Nextgens
> could
>
> > do a release (in some cases with significant effort). It may be that
>
> > others should be added to that list.
>
> Uhm? yes. One person on that list doesn?t have the time to do it anymore,
> and the other two persons are? who are they, anyway? Ian has even less time
> than you do, and he?s been completely detached from Freenet development for
> years now; Nextgens at least sometimes drops by and tells us our crypto
> sucks. :)
>
>  > It's all automated, but it's a question of what level of automation is
>
> > sufficiently secure. A build MUST be SIGNED by a specific developer, and
>
> > his signing keys must be encrypted. So I don't think release-on-commit is
>
> > a good idea. However there is a set of scripts that allows a developer to
>
> > release a build reasonably easily - provided he has the secret keys and
>
> > SSH access to freenetproject.org.
>
> I didn?t necessarily mean non-interactive server-side automation. Building
> and signing could happen locally but script-supported.
>
>  > Big features should of course be on feature branches. Beyond that, it
> makes
>
> > sense to have people who can build test-builds who can't actually do a
>
> > release, and they should have their own repositories.
>
> The way I see it test builds are releases as well; they just have to be
> requested manually from those users that like to live on the bleeding edge.
> Other than that I don?t see any distinction, especially not on their
> ?officialness.?
>
>  Greetings,
>
>  David
>
> --
>
> David ?Bombe? Roden 
>
> ___
> Devl mailing list
> Devl at freenetproject.org
> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
>



-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] [RFC] Allow more people to release a Freenet build

[Juiceman]

On Sun, Nov 6, 2011 at 3:11 PM, David ‘Bombe’ Roden bo...@pterodactylus.net
 wrote:

 **

 Hi Matthew,

  Also we could have many streams of test builds, by different
 developers,

  and thus let them release whatever they want to without it being

  officially endorsed, but the users still be able to use the update.sh

  name / update.cmd name conveniently.

 That would require quite some trickery in the update scripts, especially
 in the Windows version of it, I guess.


Not really.  Just need to make the download path a variable that is set at
the beginning of the script.  I could do the Windows script in less than an
hour once decided how the files are named and where they are kept.


   True. Eventually we need real builds. Right now me, Ian and Nextgens
 could

  do a release (in some cases with significant effort). It may be that

  others should be added to that list.

 Uhm… yes. One person on that list doesn’t have the time to do it anymore,
 and the other two persons are… who are they, anyway? Ian has even less time
 than you do, and he’s been completely detached from Freenet development for
 years now; Nextgens at least sometimes drops by and tells us our crypto
 sucks. :)

   It's all automated, but it's a question of what level of automation is

  sufficiently secure. A build MUST be SIGNED by a specific developer, and

  his signing keys must be encrypted. So I don't think release-on-commit is

  a good idea. However there is a set of scripts that allows a developer to

  release a build reasonably easily - provided he has the secret keys and

  SSH access to freenetproject.org.

 I didn’t necessarily mean non-interactive server-side automation. Building
 and signing could happen locally but script-supported.

   Big features should of course be on feature branches. Beyond that, it
 makes

  sense to have people who can build test-builds who can't actually do a

  release, and they should have their own repositories.

 The way I see it test builds are releases as well; they just have to be
 requested manually from those users that like to live on the bleeding edge.
 Other than that I don’t see any distinction, especially not on their
 “officialness.”

  Greetings,

  David

 --

 David ‘Bombe’ Roden bo...@pterodactylus.net

 ___
 Devl mailing list
 Devl@freenetproject.org
 http://freenetproject.org/cgi-bin/mailman/listinfo/devl




-- 
I may disagree with what you have to say, but I shall defend, to the death,
your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Website text

[Juiceman]

On Jul 9, 2011 12:39 PM, "Matthew Toseland" 
wrote:
>
> Please look at what I've put up at the moment:
>
> "Share files, chat on forums, browse and publish, anonymously and without
fear of blocking or censorship! Then connect to your friends for even better
security!"
>

I like this.  Informative, upbeat and encourages darknet without scaring
newbies.

> On Friday 08 Jul 2011 01:14:00 Steve Dougherty wrote:
> > I think "sites" is better - it portrays the website-like properties.
> > "Pages" has a relative connotation of disconnectedness.
> >
> > "without fear" in the first part seems overly emotional.
>
> It's plain english, isn't that a good thing? What's your alternative?
>
> > It isn't clear from
> > this that a darknet is connecting only to one's friends. Do you mean
running
> > darknet and opennet simultaneously? "Even better" security makes the
> > assertion of "anonymously and without fear" seem a large exaggeration.
How
> > about something like:
> >
> > Share files, chat on forums, and browse and publish sites, anonymously
and
> > without blocking or censorship. Use "darknet" mode to connect only to
your
> > friends for improved security.
>
> Darknet is jargon. Jargon is bad but sometimes unavoidable, but it's
especially bad at this point.
> >
> > Is it okay to mention attackers? The threat of attacks on privacy or
person
> > are arguably the reason for the security, but it makes the whole ordeal
seem
> > stressful.
>
> IMHO explicitly mentioning attackers would be bad here yes.
>
> > The exclamation marks come off as overly enthusiastic to me.
>
> Well maybe we should get rid of the sentence about darknet completely
then?
> >
> > On Thu, Jul 7, 2011 at 10:27 AM, Matthew Toseland <
toad at amphibian.dyndns.org
> > > wrote:
> >
> > > Three different versions of the text at the top of the website
recently.
> > > My favoured option:
> > >
> > > Share files, chat on forums and browse and publish sites, anonymously
and
> > > without fear of blocking or censorship! Then connect to your friends
in
> > > "darknet" mode for even better security!
> > >
> > > (Is pages better than sites? It makes sense to avoid jargon here...)
> > >
> > > Previous:
> > > (* = bold, ** = mouseover for "web sites accessible only through
Freenet")
> > >
> > > Freenet lets you *anonymously* *share* files, browse and *publish*
> > > freesites** and *chat* on forums, without fear of censorship. Freenet
is a
> > > peer to peer network with no central servers to make it less
vulnerable to
> > > attack, and if used in "*darknet*" mode, where users only connect to
their
> > > friends, is very difficult to detect or block.
> > >
> > > Before that:
> > >
> > > Freenet is free software which lets you *anonymously* *share* files,
browse
> > > and *publish* freesites** and *chat* on forums, without fear of
censorship.
> > > Freenet is *decentralised* to make it less vulnerable to attack, and
if used
> > > in "*darknet*" mode, where users only connect to their friends, is
very
> > > difficult to detect.
> > >
> > > ___
> > > Devl mailing list
> > > Devl at freenetproject.org
> > > http://freenetproject.org/cgi-bin/mailman/listinfo/devl
> > >
> >
>
> ___
> Devl mailing list
> Devl at freenetproject.org
> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] Website text

[Juiceman]

On Jul 9, 2011 12:39 PM, Matthew Toseland t...@amphibian.dyndns.org
wrote:

 Please look at what I've put up at the moment:

 Share files, chat on forums, browse and publish, anonymously and without
fear of blocking or censorship! Then connect to your friends for even better
security!


I like this.  Informative, upbeat and encourages darknet without scaring
newbies.

 On Friday 08 Jul 2011 01:14:00 Steve Dougherty wrote:
  I think sites is better - it portrays the website-like properties.
  Pages has a relative connotation of disconnectedness.
 
  without fear in the first part seems overly emotional.

 It's plain english, isn't that a good thing? What's your alternative?

  It isn't clear from
  this that a darknet is connecting only to one's friends. Do you mean
running
  darknet and opennet simultaneously? Even better security makes the
  assertion of anonymously and without fear seem a large exaggeration.
How
  about something like:
 
  Share files, chat on forums, and browse and publish sites, anonymously
and
  without blocking or censorship. Use darknet mode to connect only to
your
  friends for improved security.

 Darknet is jargon. Jargon is bad but sometimes unavoidable, but it's
especially bad at this point.
 
  Is it okay to mention attackers? The threat of attacks on privacy or
person
  are arguably the reason for the security, but it makes the whole ordeal
seem
  stressful.

 IMHO explicitly mentioning attackers would be bad here yes.

  The exclamation marks come off as overly enthusiastic to me.

 Well maybe we should get rid of the sentence about darknet completely
then?
 
  On Thu, Jul 7, 2011 at 10:27 AM, Matthew Toseland 
t...@amphibian.dyndns.org
   wrote:
 
   Three different versions of the text at the top of the website
recently.
   My favoured option:
  
   Share files, chat on forums and browse and publish sites, anonymously
and
   without fear of blocking or censorship! Then connect to your friends
in
   darknet mode for even better security!
  
   (Is pages better than sites? It makes sense to avoid jargon here...)
  
   Previous:
   (* = bold, ** = mouseover for web sites accessible only through
Freenet)
  
   Freenet lets you *anonymously* *share* files, browse and *publish*
   freesites** and *chat* on forums, without fear of censorship. Freenet
is a
   peer to peer network with no central servers to make it less
vulnerable to
   attack, and if used in *darknet* mode, where users only connect to
their
   friends, is very difficult to detect or block.
  
   Before that:
  
   Freenet is free software which lets you *anonymously* *share* files,
browse
   and *publish* freesites** and *chat* on forums, without fear of
censorship.
   Freenet is *decentralised* to make it less vulnerable to attack, and
if used
   in *darknet* mode, where users only connect to their friends, is
very
   difficult to detect.
  
   ___
   Devl mailing list
   Devl@freenetproject.org
   http://freenetproject.org/cgi-bin/mailman/listinfo/devl
  
 

 ___
 Devl mailing list
 Devl@freenetproject.org
 http://freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] China effectively blocking opennet

[Juiceman]

Do we even know that Chinese users are using 0.7.5 and not 0.5 or earlier?
On May 13, 2011 7:09 PM, "Matthew Toseland" 
wrote:
> Our old friend sdiz came up with some interesting, if depressing, news
from China:
>  just some news from china -- no english media have reported this
yet... china gfw have "upgraded". if your ip have download too much data
from foreign hosts, it is blocked from accessing any foreign ip.
>  they call it "the whitelist", because all foreign host expect a
short whitelist are affected
>
> Given that there is no obvious evidence of a lot of chinese users on
freenet, and yet the recent survey showed that Freenet is the most trusted
circumvention tool in China, there is some chance that there is already a
large Chinese darknet, but I doubt it.
>
> In any case, our options appear to be:
>
> 1) Try to make opennet work in China.
> We could do some sort of selective announcement protocol, but the problem
with this is:
> a) Why would any chinese nodes be connected / reachable through an
announcement from a western node?
> b) We'd need to reannounce every time we reconnect. Most people in China
have limited uptime because of how broadband is sold.
>
> We could try to rotate links even, so that only a few nodes have external
connections at a time. The catch is that we don't know what the limit above
is, and it will probably vary from time to time. So this is probably a
dead-end.
>
> 2) Focus on darknet.
> This is my preferred option. There are a number of relatively easy things
we can do to make darknet easier and perform better, such as FOAF
connections and invites.
> Difficulties:
> a) If the Chinese darknet is completely sealed off from the western
network, how would they even get software updates? We need better tools for
migrating binary blobs.
> b) We need some way to ensure that FOAF connections don't result in
dangerous external connections.
>
> In any case we should add an option to warn about / not connect to peers
outside or inside a given jurisdiction.
>
> Thoughts?
>
> Also, we might be able to get some publicity. Given we have less than 17
weeks funding even with relatively generous bitcoin donations recently
included, we need something soon. Of course the obvious thing is Freetalk,
but there remain serious performance and scalability worries which are being
worked on...
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] China effectively blocking opennet

[Juiceman]

Do we even know that Chinese users are using 0.7.5 and not 0.5 or earlier?
On May 13, 2011 7:09 PM, Matthew Toseland t...@amphibian.dyndns.org
wrote:
 Our old friend sdiz came up with some interesting, if depressing, news
from China:
 sdiz just some news from china -- no english media have reported this
yet... china gfw have upgraded. if your ip have download too much data
from foreign hosts, it is blocked from accessing any foreign ip.
 sdiz they call it the whitelist, because all foreign host expect a
short whitelist are affected

 Given that there is no obvious evidence of a lot of chinese users on
freenet, and yet the recent survey showed that Freenet is the most trusted
circumvention tool in China, there is some chance that there is already a
large Chinese darknet, but I doubt it.

 In any case, our options appear to be:

 1) Try to make opennet work in China.
 We could do some sort of selective announcement protocol, but the problem
with this is:
 a) Why would any chinese nodes be connected / reachable through an
announcement from a western node?
 b) We'd need to reannounce every time we reconnect. Most people in China
have limited uptime because of how broadband is sold.

 We could try to rotate links even, so that only a few nodes have external
connections at a time. The catch is that we don't know what the limit above
is, and it will probably vary from time to time. So this is probably a
dead-end.

 2) Focus on darknet.
 This is my preferred option. There are a number of relatively easy things
we can do to make darknet easier and perform better, such as FOAF
connections and invites.
 Difficulties:
 a) If the Chinese darknet is completely sealed off from the western
network, how would they even get software updates? We need better tools for
migrating binary blobs.
 b) We need some way to ensure that FOAF connections don't result in
dangerous external connections.

 In any case we should add an option to warn about / not connect to peers
outside or inside a given jurisdiction.

 Thoughts?

 Also, we might be able to get some publicity. Given we have less than 17
weeks funding even with relatively generous bitcoin donations recently
included, we need something soon. Of course the obvious thing is Freetalk,
but there remain serious performance and scalability worries which are being
worked on...
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Should we include JNA in freenet-ext.jar?

[Juiceman]

On Sat, Apr 23, 2011 at 1:58 PM, Matthew Toseland
 wrote:
> This is a very small and very promising patch, but we would need to include 
> the JNA library. The JNA library allows us to conveniently call native APIs 
> without JNI code. We could use this for not only what this patch does - set 
> background mode to significantly reduce system impact of our on-startup disk 
> I/O - but also for setting thread priorities on unix, for which we currently 
> have a native JNI library. And there may well be other things we'd like to 
> call native libraries for too.
>
> Also its platform detection code might well replace our existing code in that 
> area - or at least some of it.
>
> The catch is the library is 900KB, and the platform library (which I think 
> just has some standard convenience functions) is 700KB. So we might be 
> looking at increasing the download by 1.6MB.
>
> Thoughts? I'm in favour but not totally convinced...
>
> The original pull request (more info in attached messages):
> https://github.com/freenet/fred-staging/pull/29
>
>

The ext is updated very rarely so it should not be an issue with the
update script, and users are used to downloading large install files
since there is such bloatware out there.  Our main user base has
broadband so it shouldn't be a big problem for them.  How will it
affect our hosting bandwidth?

Imho, the benefits of improving system responsiveness far outweigh the
minor increase in file size.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

Re: [freenet-dev] Should we include JNA in freenet-ext.jar?

[Juiceman]

On Sat, Apr 23, 2011 at 1:58 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 This is a very small and very promising patch, but we would need to include 
 the JNA library. The JNA library allows us to conveniently call native APIs 
 without JNI code. We could use this for not only what this patch does - set 
 background mode to significantly reduce system impact of our on-startup disk 
 I/O - but also for setting thread priorities on unix, for which we currently 
 have a native JNI library. And there may well be other things we'd like to 
 call native libraries for too.

 Also its platform detection code might well replace our existing code in that 
 area - or at least some of it.

 The catch is the library is 900KB, and the platform library (which I think 
 just has some standard convenience functions) is 700KB. So we might be 
 looking at increasing the download by 1.6MB.

 Thoughts? I'm in favour but not totally convinced...

 The original pull request (more info in attached messages):
 https://github.com/freenet/fred-staging/pull/29



The ext is updated very rarely so it should not be an issue with the
update script, and users are used to downloading large install files
since there is such bloatware out there.  Our main user base has
broadband so it shouldn't be a big problem for them.  How will it
affect our hosting bandwidth?

Imho, the benefits of improving system responsiveness far outweigh the
minor increase in file size.

-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Initiating a bugfix

[Juiceman]

On Sat, Mar 19, 2011 at 9:54 PM, Ashan Fernando  wrote:
> Hi,
> Im a final year student from the Department of Computer Science and
> Engineering and interested in Freenet for GSoC 2011. To get started I have
> cloned the source of Freenet from the git and would like to start working on
> fixing a bug.I have gone though the list in the Bugtracker but its quite
> difficult to identify the complexity initially.Therefore it would be a great
> help if someone can guide me to start work with.
> Thanks,
> Ashan
>

https://bugs.freenetproject.org/roadmap_page.php  would be a good
place to look at an overview of bugs desired to be resolved to release
the next big version.  Look them over and pick one that looks
interesting.  Many should be relatively easy fixes just choose
something in an area of the codebase you would like to work.

Re: [freenet-dev] Initiating a bugfix

[Juiceman]

On Sat, Mar 19, 2011 at 9:54 PM, Ashan Fernando ashan...@gmail.com wrote:
 Hi,
 Im a final year student from the Department of Computer Science and
 Engineering and interested in Freenet for GSoC 2011. To get started I have
 cloned the source of Freenet from the git and would like to start working on
 fixing a bug.I have gone though the list in the Bugtracker but its quite
 difficult to identify the complexity initially.Therefore it would be a great
 help if someone can guide me to start work with.
 Thanks,
 Ashan


https://bugs.freenetproject.org/roadmap_page.php  would be a good
place to look at an overview of bugs desired to be resolved to release
the next big version.  Look them over and pick one that looks
interesting.  Many should be relatively easy fixes just choose
something in an area of the codebase you would like to work.
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I forgot to mention that it was free...  I am willing to be an official
tester/contact if you need one.
On Mar 16, 2011 10:19 AM, "Juiceman"  wrote:
> I got an answer back from Kaspersky. Basically we will need to whitelist
> each release for now. I asked if they could give me the technical details
> of what file or behavior is causing the flag, but they will only share
that
> with the official organization developers. They have a partner program to
> ensure whitelisting. HTTP://USA.kaspersky.
com/partners/white-list-program.
>
> On Mar 15, 2011 2:01 PM, "Ian Clarke"  wrote:
>> Yeah, if they are just whitelisting a md5sum then we could get caught out
>> again by any subsequent release of that file :-/
>>
>> Ian.
>>
>> On Tue, Mar 15, 2011 at 12:21 AM, Juiceman  wrote:
>>
>>> I have been in contact with Kaspersky regarding the false positive
>>> detections. They have been quite helpful. I still need to find out
>>> what they are whitelisting, just the FreenetInstaller-1355.exe or the
>>> underlying files.
>>>
>>>
>>> -- Forwarded message --
>>> From: 
>>> Date: Mon, Mar 14, 2011 at 10:37 PM
>>> Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>>> [KLAN-117070913] [KLAN-118829548]
>>> To: juiceman69 at gmail.com
>>>
>>>
>>> Hello,
>>>
>>> It was added to the whitelist.
>>> Detection will disappear within 6 hours.
>>>
>>> Please quote all when answering.
>>> -
>>> Regards, Baranov Artiom
>>> Virus Analyst, Kaspersky Lab.
>>>
>>> >From: juiceman69 at gmail.com
>>> >Sent: 15.03.2011 5:28:00
>>> >To: "New Virus" 
>>> >Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>>> [KLAN-117070913]
>>> >
>>> > On Fri, Mar 4, 2011 at 5:58 AM,  wrote:
>>> > > Hello,
>>> > >
>>> > > We can not reproduce the detection, could you send us a screen shot
>>> about the detection ?
>>> > >
>>> > > Regards,
>>> > > VirusLab China
>>> > >
>>> > >>From: juiceman69 at gmail.com
>>> > >>Sent: 03.03.2011 6:02:00
>>> > >>To: "New Virus" 
>>> > >>Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>>> > >>
>>> > >>
>>> > >> LANG: en
>>> > >> email: juiceman69 at gmail.com
>>> > >>
>>> > >> description:
>>> > >> Kaspersky Anti Virus 11.0.1.400 detects Freenet as
>>> PDM.Worm.P2P.generic
>>> > >> Freenet is P2P software promoting freedom of speech in oppressive
>>> countries such as we are seeing in the Middle East now.
>>> > >>
>>> > >> To reproduce:
>>> > >> Install
> http://freenet.googlecode.com/files/FreenetInstaller-1355.exefrom
>>> > >> http://freenetproject.org/index.html. Half way through the install
>>> Kaspersky stops it and quarantines the installer.
>>> > >>
>>> > >> I have heard of other users having a similar problem, but
> encountered
>>> this personally.
>>> > >>
>>> > >> I have attached the file. Note the file passes virus scan before
the
>>> install is attempted.
>>> > >>
>>> > >> uploaded files:
>>> > >> FREENETINSTALLER-1355.zip
>>> >
>>> > Sorry, to reply so late, I was on vacation. I am attaching two
>>> > screenshots. The "Freenet_Install_Start.jpg" shows the install
>>> > beginning just fine, the second screenshot
>>> > "FreenetInstaller_AV_Flagged.jpg" is when the install is continued and
>>> > files are unpacked.
>>> > It is not until the files are unpacked all the way and some other
>>> > programs/scripts inside are run that Kaspersky sees it as a virus.
>>> >
>>> > Thank you for looking further into this. Please keep me advised and
>>> > let me know if I can help in any way.
>>> >
>>> 10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
>>> Tel./Fax: + 7 (495) 797 8700
>>> http://www.kaspersky.com http://www.viruslist.com
>>>
>>>
>>>
>>> --
>>> I may disagree with what you have to say, but I shall defend, to the
>>> death, your right to say it. - Voltaire
>>> Those who would give up Liberty, to purchase temporary Safety, deserve
>>> neither Liberty nor Safety. - Ben Franklin
>>> ___
>>> Devl mailing list
>>> Devl at freenetproject.org
>>> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
>>
>>
>>
>>
>> --
>> Ian Clarke
>> Personal blog: http://blog.locut.us/
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20110316/0bc4df15/attachment.html>

[freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I got an answer back from Kaspersky.   Basically we will need to whitelist
each release for now.  I asked if they could give me the technical details
of what file or behavior is causing the flag, but they will only share that
with the official organization developers.   They have a partner program to
ensure whitelisting.  HTTP://USA.kaspersky. com/partners/white-list-program.

On Mar 15, 2011 2:01 PM, "Ian Clarke"  wrote:
> Yeah, if they are just whitelisting a md5sum then we could get caught out
> again by any subsequent release of that file :-/
>
> Ian.
>
> On Tue, Mar 15, 2011 at 12:21 AM, Juiceman  wrote:
>
>> I have been in contact with Kaspersky regarding the false positive
>> detections. They have been quite helpful. I still need to find out
>> what they are whitelisting, just the FreenetInstaller-1355.exe or the
>> underlying files.
>>
>>
>> -- Forwarded message --
>> From: 
>> Date: Mon, Mar 14, 2011 at 10:37 PM
>> Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>> [KLAN-117070913] [KLAN-118829548]
>> To: juiceman69 at gmail.com
>>
>>
>> Hello,
>>
>> It was added to the whitelist.
>> Detection will disappear within 6 hours.
>>
>> Please quote all when answering.
>> -
>> Regards, Baranov Artiom
>> Virus Analyst, Kaspersky Lab.
>>
>> >From: juiceman69 at gmail.com
>> >Sent: 15.03.2011 5:28:00
>> >To: "New Virus" 
>> >Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>> [KLAN-117070913]
>> >
>> > On Fri, Mar 4, 2011 at 5:58 AM,  wrote:
>> > > Hello,
>> > >
>> > > We can not reproduce the detection, could you send us a screen shot
>> about the detection ?
>> > >
>> > > Regards,
>> > > VirusLab China
>> > >
>> > >>From: juiceman69 at gmail.com
>> > >>Sent: 03.03.2011 6:02:00
>> > >>To: "New Virus" 
>> > >>Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
>> > >>
>> > >>
>> > >> LANG: en
>> > >> email: juiceman69 at gmail.com
>> > >>
>> > >> description:
>> > >> Kaspersky Anti Virus 11.0.1.400 detects Freenet as
>> PDM.Worm.P2P.generic
>> > >> Freenet is P2P software promoting freedom of speech in oppressive
>> countries such as we are seeing in the Middle East now.
>> > >>
>> > >> To reproduce:
>> > >> Install
http://freenet.googlecode.com/files/FreenetInstaller-1355.exefrom
>> > >> http://freenetproject.org/index.html. Half way through the install
>> Kaspersky stops it and quarantines the installer.
>> > >>
>> > >> I have heard of other users having a similar problem, but
encountered
>> this personally.
>> > >>
>> > >> I have attached the file. Note the file passes virus scan before the
>> install is attempted.
>> > >>
>> > >> uploaded files:
>> > >> FREENETINSTALLER-1355.zip
>> >
>> > Sorry, to reply so late, I was on vacation. I am attaching two
>> > screenshots. The "Freenet_Install_Start.jpg" shows the install
>> > beginning just fine, the second screenshot
>> > "FreenetInstaller_AV_Flagged.jpg" is when the install is continued and
>> > files are unpacked.
>> > It is not until the files are unpacked all the way and some other
>> > programs/scripts inside are run that Kaspersky sees it as a virus.
>> >
>> > Thank you for looking further into this. Please keep me advised and
>> > let me know if I can help in any way.
>> >
>> 10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
>> Tel./Fax: + 7 (495) 797 8700
>> http://www.kaspersky.com http://www.viruslist.com
>>
>>
>>
>> --
>> I may disagree with what you have to say, but I shall defend, to the
>> death, your right to say it. - Voltaire
>> Those who would give up Liberty, to purchase temporary Safety, deserve
>> neither Liberty nor Safety. - Ben Franklin
>> ___
>> Devl mailing list
>> Devl at freenetproject.org
>> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>
>
>
> --
> Ian Clarke
> Personal blog: http://blog.locut.us/
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20110316/cdba2575/attachment.html>

Re: [freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I got an answer back from Kaspersky.   Basically we will need to whitelist
each release for now.  I asked if they could give me the technical details
of what file or behavior is causing the flag, but they will only share that
with the official organization developers.   They have a partner program to
ensure whitelisting.  HTTP://USA.kaspersky. com/partners/white-list-program.

On Mar 15, 2011 2:01 PM, Ian Clarke i...@locut.us wrote:
 Yeah, if they are just whitelisting a md5sum then we could get caught out
 again by any subsequent release of that file :-/

 Ian.

 On Tue, Mar 15, 2011 at 12:21 AM, Juiceman juicema...@gmail.com wrote:

 I have been in contact with Kaspersky regarding the false positive
 detections. They have been quite helpful. I still need to find out
 what they are whitelisting, just the FreenetInstaller-1355.exe or the
 underlying files.


 -- Forwarded message --
 From: newvi...@kaspersky.com
 Date: Mon, Mar 14, 2011 at 10:37 PM
 Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
 [KLAN-117070913] [KLAN-118829548]
 To: juicema...@gmail.com


 Hello,

 It was added to the whitelist.
 Detection will disappear within 6 hours.

 Please quote all when answering.
 -
 Regards, Baranov Artiom
 Virus Analyst, Kaspersky Lab.

 From: juicema...@gmail.com
 Sent: 15.03.2011 5:28:00
 To: New Virus newvi...@kaspersky.com
 Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
 [KLAN-117070913]
 
  On Fri, Mar 4, 2011 at 5:58 AM, newvi...@kaspersky.com wrote:
   Hello,
  
   We can not reproduce the detection, could you send us a screen shot
 about the detection ?
  
   Regards,
   VirusLab China
  
  From: juicema...@gmail.com
  Sent: 03.03.2011 6:02:00
  To: New Virus newvi...@kaspersky.com
  Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
  
  
   LANG: en
   email: juicema...@gmail.com
  
   description:
   Kaspersky Anti Virus 11.0.1.400 detects Freenet as
 PDM.Worm.P2P.generic
   Freenet is P2P software promoting freedom of speech in oppressive
 countries such as we are seeing in the Middle East now.
  
   To reproduce:
   Install
http://freenet.googlecode.com/files/FreenetInstaller-1355.exefrom
   http://freenetproject.org/index.html. Half way through the install
 Kaspersky stops it and quarantines the installer.
  
   I have heard of other users having a similar problem, but
encountered
 this personally.
  
   I have attached the file. Note the file passes virus scan before the
 install is attempted.
  
   uploaded files:
   FREENETINSTALLER-1355.zip
 
  Sorry, to reply so late, I was on vacation. I am attaching two
  screenshots. The Freenet_Install_Start.jpg shows the install
  beginning just fine, the second screenshot
  FreenetInstaller_AV_Flagged.jpg is when the install is continued and
  files are unpacked.
  It is not until the files are unpacked all the way and some other
  programs/scripts inside are run that Kaspersky sees it as a virus.
 
  Thank you for looking further into this. Please keep me advised and
  let me know if I can help in any way.
 
 10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
 Tel./Fax: + 7 (495) 797 8700
 http://www.kaspersky.com http://www.viruslist.com



 --
 I may disagree with what you have to say, but I shall defend, to the
 death, your right to say it. - Voltaire
 Those who would give up Liberty, to purchase temporary Safety, deserve
 neither Liberty nor Safety. - Ben Franklin
 ___
 Devl mailing list
 Devl@freenetproject.org
 http://freenetproject.org/cgi-bin/mailman/listinfo/devl




 --
 Ian Clarke
 Personal blog: http://blog.locut.us/
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I forgot to mention that it was free...  I am willing to be an official
tester/contact if you need one.
On Mar 16, 2011 10:19 AM, Juiceman juicema...@gmail.com wrote:
 I got an answer back from Kaspersky. Basically we will need to whitelist
 each release for now. I asked if they could give me the technical details
 of what file or behavior is causing the flag, but they will only share
that
 with the official organization developers. They have a partner program to
 ensure whitelisting. HTTP://USA.kaspersky.
com/partners/white-list-program.

 On Mar 15, 2011 2:01 PM, Ian Clarke i...@locut.us wrote:
 Yeah, if they are just whitelisting a md5sum then we could get caught out
 again by any subsequent release of that file :-/

 Ian.

 On Tue, Mar 15, 2011 at 12:21 AM, Juiceman juicema...@gmail.com wrote:

 I have been in contact with Kaspersky regarding the false positive
 detections. They have been quite helpful. I still need to find out
 what they are whitelisting, just the FreenetInstaller-1355.exe or the
 underlying files.


 -- Forwarded message --
 From: newvi...@kaspersky.com
 Date: Mon, Mar 14, 2011 at 10:37 PM
 Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
 [KLAN-117070913] [KLAN-118829548]
 To: juicema...@gmail.com


 Hello,

 It was added to the whitelist.
 Detection will disappear within 6 hours.

 Please quote all when answering.
 -
 Regards, Baranov Artiom
 Virus Analyst, Kaspersky Lab.

 From: juicema...@gmail.com
 Sent: 15.03.2011 5:28:00
 To: New Virus newvi...@kaspersky.com
 Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
 [KLAN-117070913]
 
  On Fri, Mar 4, 2011 at 5:58 AM, newvi...@kaspersky.com wrote:
   Hello,
  
   We can not reproduce the detection, could you send us a screen shot
 about the detection ?
  
   Regards,
   VirusLab China
  
  From: juicema...@gmail.com
  Sent: 03.03.2011 6:02:00
  To: New Virus newvi...@kaspersky.com
  Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
  
  
   LANG: en
   email: juicema...@gmail.com
  
   description:
   Kaspersky Anti Virus 11.0.1.400 detects Freenet as
 PDM.Worm.P2P.generic
   Freenet is P2P software promoting freedom of speech in oppressive
 countries such as we are seeing in the Middle East now.
  
   To reproduce:
   Install
 http://freenet.googlecode.com/files/FreenetInstaller-1355.exefrom
   http://freenetproject.org/index.html. Half way through the install
 Kaspersky stops it and quarantines the installer.
  
   I have heard of other users having a similar problem, but
 encountered
 this personally.
  
   I have attached the file. Note the file passes virus scan before
the
 install is attempted.
  
   uploaded files:
   FREENETINSTALLER-1355.zip
 
  Sorry, to reply so late, I was on vacation. I am attaching two
  screenshots. The Freenet_Install_Start.jpg shows the install
  beginning just fine, the second screenshot
  FreenetInstaller_AV_Flagged.jpg is when the install is continued and
  files are unpacked.
  It is not until the files are unpacked all the way and some other
  programs/scripts inside are run that Kaspersky sees it as a virus.
 
  Thank you for looking further into this. Please keep me advised and
  let me know if I can help in any way.
 
 10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
 Tel./Fax: + 7 (495) 797 8700
 http://www.kaspersky.com http://www.viruslist.com



 --
 I may disagree with what you have to say, but I shall defend, to the
 death, your right to say it. - Voltaire
 Those who would give up Liberty, to purchase temporary Safety, deserve
 neither Liberty nor Safety. - Ben Franklin
 ___
 Devl mailing list
 Devl@freenetproject.org
 http://freenetproject.org/cgi-bin/mailman/listinfo/devl




 --
 Ian Clarke
 Personal blog: http://blog.locut.us/
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I have been in contact with Kaspersky regarding the false positive
detections.  They have been quite helpful.  I still need to find out
what they are whitelisting, just the FreenetInstaller-1355.exe or the
underlying files.


-- Forwarded message --
From:  
Date: Mon, Mar 14, 2011 at 10:37 PM
Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
[KLAN-117070913] [KLAN-118829548]
To: juiceman69 at gmail.com


Hello,

It was added to the whitelist.
Detection will disappear within 6 hours.

Please quote all when answering.
-
Regards, Baranov Artiom
Virus Analyst, Kaspersky Lab.

>From: juiceman69 at gmail.com
>Sent: 15.03.2011 5:28:00
>To: "New Virus" 
>Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0] 
>[KLAN-117070913]
>
> On Fri, Mar 4, 2011 at 5:58 AM, ? wrote:
> > Hello,
> >
> > We can not reproduce the detection, could you send us a screen shot about 
> > the detection ?
> >
> > Regards,
> > VirusLab China
> >
> >>From: juiceman69 at gmail.com
> >>Sent: 03.03.2011 6:02:00
> >>To: "New Virus" 
> >>Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
> >>
> >>
> >> LANG: en
> >> email: juiceman69 at gmail.com
> >>
> >> description:
> >> Kaspersky Anti Virus 11.0.1.400 detects Freenet as PDM.Worm.P2P.generic
> >> Freenet is P2P software promoting freedom of speech in oppressive 
> >> countries such as we are seeing in the Middle East now.
> >>
> >> To reproduce:
> >> Install http://freenet.googlecode.com/files/FreenetInstaller-1355.exe from
> >> http://freenetproject.org/index.html. ?Half way through the install 
> >> Kaspersky stops it and quarantines the installer.
> >>
> >> I have heard of other users having a similar problem, but encountered this 
> >> personally.
> >>
> >> I have attached the file. ?Note the file passes virus scan before the 
> >> install is attempted.
> >>
> >> uploaded files:
> >> FREENETINSTALLER-1355.zip
>
> Sorry, to reply so late, I was on vacation. ?I am attaching two
> screenshots. ?The "Freenet_Install_Start.jpg" shows the install
> beginning just fine, the second screenshot
> "FreenetInstaller_AV_Flagged.jpg" is when the install is continued and
> files are unpacked.
> It is not until the files are unpacked all the way and some other
> programs/scripts inside are run that Kaspersky sees it as a virus.
>
> Thank you for looking further into this. ?Please keep me advised and
> let me know if I can help in any way.
>
10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
Tel./Fax: + 7 (495) 797 8700
http://www.kaspersky.com http://www.viruslist.com



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin

[freenet-dev] Kaspersky working on whitelisting Freenet

[Juiceman]

I have been in contact with Kaspersky regarding the false positive
detections.  They have been quite helpful.  I still need to find out
what they are whitelisting, just the FreenetInstaller-1355.exe or the
underlying files.


-- Forwarded message --
From:  newvi...@kaspersky.com
Date: Mon, Mar 14, 2011 at 10:37 PM
Subject: RE: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
[KLAN-117070913] [KLAN-118829548]
To: juicema...@gmail.com


Hello,

It was added to the whitelist.
Detection will disappear within 6 hours.

Please quote all when answering.
-
Regards, Baranov Artiom
Virus Analyst, Kaspersky Lab.

From: juicema...@gmail.com
Sent: 15.03.2011 5:28:00
To: New Virus newvi...@kaspersky.com
Subject: Re: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0] 
[KLAN-117070913]

 On Fri, Mar 4, 2011 at 5:58 AM,  newvi...@kaspersky.com wrote:
  Hello,
 
  We can not reproduce the detection, could you send us a screen shot about 
  the detection ?
 
  Regards,
  VirusLab China
 
 From: juicema...@gmail.com
 Sent: 03.03.2011 6:02:00
 To: New Virus newvi...@kaspersky.com
 Subject: [VirLabSRF][False alarm on a file][M:1][LN:EN][L:0]
 
 
  LANG: en
  email: juicema...@gmail.com
 
  description:
  Kaspersky Anti Virus 11.0.1.400 detects Freenet as PDM.Worm.P2P.generic
  Freenet is P2P software promoting freedom of speech in oppressive 
  countries such as we are seeing in the Middle East now.
 
  To reproduce:
  Install http://freenet.googlecode.com/files/FreenetInstaller-1355.exe from
  http://freenetproject.org/index.html.  Half way through the install 
  Kaspersky stops it and quarantines the installer.
 
  I have heard of other users having a similar problem, but encountered this 
  personally.
 
  I have attached the file.  Note the file passes virus scan before the 
  install is attempted.
 
  uploaded files:
  FREENETINSTALLER-1355.zip

 Sorry, to reply so late, I was on vacation.  I am attaching two
 screenshots.  The Freenet_Install_Start.jpg shows the install
 beginning just fine, the second screenshot
 FreenetInstaller_AV_Flagged.jpg is when the install is continued and
 files are unpacked.
 It is not until the files are unpacked all the way and some other
 programs/scripts inside are run that Kaspersky sees it as a virus.

 Thank you for looking further into this.  Please keep me advised and
 let me know if I can help in any way.

10/1, 1st Volokolamsky Proezd, Moscow, 123060, Russia
Tel./Fax: + 7 (495) 797 8700
http://www.kaspersky.com http://www.viruslist.com



-- 
I may disagree with what you have to say, but I shall defend, to the
death, your right to say it. - Voltaire
Those who would give up Liberty, to purchase temporary Safety, deserve
neither Liberty nor Safety. - Ben Franklin
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] New freenet-ext.jar, please test!

[Juiceman]

On Wed, Mar 9, 2011 at 6:29 PM, Matthew Toseland
 wrote:
> We want to deploy this soon. Please test it.
> http://downloads.freenetproject.org/alpha/freenet-ext-v27pre8.jar
>
> You can build this from the tag.

So far so good...

Re: [freenet-dev] New freenet-ext.jar, please test!

[Juiceman]

On Wed, Mar 9, 2011 at 6:29 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 We want to deploy this soon. Please test it.
 http://downloads.freenetproject.org/alpha/freenet-ext-v27pre8.jar

 You can build this from the tag.

So far so good...
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Thu, Feb 10, 2011 at 8:49 PM, Matthew Toseland
 wrote:
> On Saturday 05 Feb 2011 19:26:46 Juiceman wrote:
>> On Sat, Feb 5, 2011 at 2:24 PM, Juiceman  wrote:
>> > On Sat, Feb 5, 2011 at 2:17 PM, Juiceman  wrote:
>> >> On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
>> >>  wrote:
>> >>> We need more seednodes. I will explain the broader situation below. If 
>> >>> you can run a seednode - which means you need a forwarded port, a 
>> >>> reasonably static IP address (or dyndns name), and a reasonable amount 
>> >>> of bandwidth (especially upstream), and a reasonably stable node, please 
>> >>> send me your opennet noderef (from the strangers page in advanced mode), 
>> >>> and enable "Be a seednode" in the advanced config. Thanks.
>> >>>
>> >>> Details:
>> >>>
>> >>> One of the problems Freenet has at the moment is that bootstrapping a 
>> >>> new node can take an awfully long time - 20 minutes or more sometimes. 
>> >>> It is not clear why; we seem to either get rejected by seednodes (most 
>> >>> of the time), or they return nothing, maybe a few "not wanted" notices, 
>> >>> or they return lots of noderefs and we manage to announce.
>> >>>
>> >>> This might be due to bugs. 1343 fixed a bug that apparently badly 
>> >>> affected some seednodes. However it appears most seednodes have upgraded 
>> >>> now.
>> >>>
>> >>> There doesn't seem to be a problem with losing connections - backoff yes 
>> >>> but once a node is connected it seems to mostly stay connected.
>> >>>
>> >>> The most likely answer seems to be that we just don't have enough 
>> >>> seednodes to cope with the load.
>> >>>
>> >>> It is also possible that this is due to an attack. It did come on 
>> >>> relatively suddenly a few weeks ago (it was bad before but it got much 
>> >>> worse), and it seems to have got significantly worse in the last week. 
>> >>> It is not clear how we would identify an attack if that was the problem; 
>> >>> there are no obvious signs so far.
>> >>>
>> >>> It is also possible it is a client-side bug. Testing of the master 
>> >>> branch would be useful, it has some small changes.
>> >>>
>> >>
>> >> Errors in my log (build 1344)
>> >
>> > Also nodestats have been horrible on my seednode for last week or two.
>> > ?I am noticing node ping times in the 1500 - 3500 ms range. ?Mostly
>> > during daytime hours here (GMT -5). ?Not sure if ATT Uverse has
>> > quietly started throttling p2p (they say they don't), or if it is an
>> > attack or bug. ?Seeding for 206 is typical and didn't kill my node in
>> > the past. ?Let me know what logger settings to set and I can send you
>> > my logs if you want.
>> >
>> > Peer statistics
>> >
>> > ? ?* Connected: 15
>> > ? ?* Backed off: 3
>> > ? ?* Too old: 67
>> > ? ?* Disconnected: 13
>> > ? ?* Never connected: 5
>> > ? ?* Clock Problem: 1
>> > ? ?* Seeding for: 206
>> > ? ?* Max peers: 36
>> > ? ?* Max strangers: 36
>> >
>> > Bandwidth
>> >
>> > ? ?* Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
>> > ? ?* Output Rate: 31.6 KiB/s (of 105 KiB/s)
>> > ? ?* Session Total Input: 49.2 MiB (43.7 KiB/s average)
>> > ? ?* Session Total Output: 35.7 MiB (31.7 KiB/s average)
>> > ? ?* Payload Output: 214 KiB (190 B/sec)(0%)
>> >
>>
>> Node status overview
>>
>> ? ? * bwlimitDelayTime: 2947ms
>> ? ? * bwlimitDelayTimeBulk: 2893ms
>> ? ? * bwlimitDelayTimeRT: 9078ms
>> ? ? * nodeAveragePingTime: 2315ms
>> ? ? * darknetSizeEstimateSession: 0 nodes
>> ? ? * opennetSizeEstimateSession: 833 nodes
>> ? ? * nodeUptimeSession: 26m34s
>> ? ? * nodeUptimeTotal: 8w2d
>> ? ? * routingMissDistanceLocal: 0.0650
>> ? ? * routingMissDistanceRemote: 0.0141
>> ? ? * routingMissDistanceOverall: 0.0261
>> ? ? * backedOffPercent: 22.3%
>> ? ? * pInstantReject: 95.8%
>> ? ? * unclaimedFIFOSize: 2663
>> ? ? * RAMBucketPoolSize: 12.8 MiB / 150 MiB
>> ? ? * uptimeAverage: 99.3%
>
> Ping times that high mean your node won't accept any requests at all, 
> although it might accept some announcements.
>
> Usually this is caused by network or CPU problems. When I've run my seednode 
> lately it hasn't had high ping times, nor have any of my other nodes.
>
> The NPE is fixed btw.

I have a tech coming out to diagnose my DSL issues, but the last
several builds have improved my ping times.

[freenet-dev] Wonder why bootstrapping is slow

[Juiceman]

On Thu, Feb 10, 2011 at 8:47 PM, Matthew Toseland
 wrote:
>
> On Tuesday 08 Feb 2011 04:16:25 Juiceman wrote:
> > Bootstrapping from seednodes is really slow right now. ?I run one of
> > those seednodes. ?Here are my stats, they have been horrible for about
> > 2 weeks now. ?I don't suppose my node is serving many announcements,
> > huh? ?Are other seednodes in similarly bad shape?
>
> I have some theories.
>
> It looks like most of the announcement load is caused by old nodes trying and 
> repeatedly failing to update using Update Over Mandatory.
>
> Recent builds should help with this, 1349 should help even more (and might 
> help improve announcement performance generally).
>

Much better!? 1349 stats:

Node status overview

bwlimitDelayTime:?1152ms
bwlimitDelayTimeBulk:?1152ms
bwlimitDelayTimeRT:?444ms
nodeAveragePingTime:?356ms
darknetSizeEstimateSession:?0?nodes
opennetSizeEstimateSession:?1804?nodes
nodeUptimeSession:?1h28m
nodeUptimeTotal:?9w21h
routingMissDistanceLocal:?0.1760
routingMissDistanceRemote:?0.1475
routingMissDistanceOverall:?0.1481
backedOffPercent:?36.7%
pInstantReject:?0.0%
unclaimedFIFOSize:?1398
RAMBucketPoolSize:?66.2 MiB / 150 MiB
uptimeAverage:?90.1%

Peer statistics

Connected:?26
Backed off:?9
Disconnected:?1
Never connected:?1
Seeding for:?32
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 31.7?KiB/s (of 1.0?MiB/s)
Output Rate: 33.4?KiB/s (of 105?KiB/s)
Session Total Input: 267?MiB (51.4?KiB/s average)
Session Total Output: 311?MiB (60.0?KiB/s average)
Payload Output: 236?MiB (45.4?KiB/sec)(75%)
Global Total Input: 369?GiB
Global Total Output: 433?GiB
Request output (excluding payload): CHK -6.61?MiB SSK 23.6?MiB.
Insert output (excluding payload): CHK -2.26?MiB SSK 492?KiB.
Offered keys: sending keys -79.8?KiB, sending offers 307?KiB
Swapping Output: 2.75?MiB.
Connection setup: 4.78?MiB output
Ack-only packets: 6.74?MiB
Resent bytes: 6.70?MiB (2%)
Updater Output: 113?KiB
Announcement output: 9.14?MiB (transferring node refs payload 8.26?MiB)
Admin bytes: 313?KiB initial messages, 0?B IP change messages, 917?B
disconnection notifications, 0?B routing status
Debugging bytes: 0?B network coloring, 0?B ping, 0?B probe requests, 0
B routed test messages.
Node to node messages: 564?KiB
Load allocation notices: 1.08?MiB
Other output: 28.0?MiB (8%)
Total non-request overhead: 6.19 KiB/sec (10%).

Re: [freenet-dev] Wonder why bootstrapping is slow

[Juiceman]

On Thu, Feb 10, 2011 at 8:47 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:

 On Tuesday 08 Feb 2011 04:16:25 Juiceman wrote:
  Bootstrapping from seednodes is really slow right now.  I run one of
  those seednodes.  Here are my stats, they have been horrible for about
  2 weeks now.  I don't suppose my node is serving many announcements,
  huh?  Are other seednodes in similarly bad shape?

 I have some theories.

 It looks like most of the announcement load is caused by old nodes trying and 
 repeatedly failing to update using Update Over Mandatory.

 Recent builds should help with this, 1349 should help even more (and might 
 help improve announcement performance generally).


Much better!  1349 stats:

Node status overview

bwlimitDelayTime: 1152ms
bwlimitDelayTimeBulk: 1152ms
bwlimitDelayTimeRT: 444ms
nodeAveragePingTime: 356ms
darknetSizeEstimateSession: 0 nodes
opennetSizeEstimateSession: 1804 nodes
nodeUptimeSession: 1h28m
nodeUptimeTotal: 9w21h
routingMissDistanceLocal: 0.1760
routingMissDistanceRemote: 0.1475
routingMissDistanceOverall: 0.1481
backedOffPercent: 36.7%
pInstantReject: 0.0%
unclaimedFIFOSize: 1398
RAMBucketPoolSize: 66.2 MiB / 150 MiB
uptimeAverage: 90.1%

Peer statistics

Connected: 26
Backed off: 9
Disconnected: 1
Never connected: 1
Seeding for: 32
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 31.7 KiB/s (of 1.0 MiB/s)
Output Rate: 33.4 KiB/s (of 105 KiB/s)
Session Total Input: 267 MiB (51.4 KiB/s average)
Session Total Output: 311 MiB (60.0 KiB/s average)
Payload Output: 236 MiB (45.4 KiB/sec)(75%)
Global Total Input: 369 GiB
Global Total Output: 433 GiB
Request output (excluding payload): CHK -6.61 MiB SSK 23.6 MiB.
Insert output (excluding payload): CHK -2.26 MiB SSK 492 KiB.
Offered keys: sending keys -79.8 KiB, sending offers 307 KiB
Swapping Output: 2.75 MiB.
Connection setup: 4.78 MiB output
Ack-only packets: 6.74 MiB
Resent bytes: 6.70 MiB (2%)
Updater Output: 113 KiB
Announcement output: 9.14 MiB (transferring node refs payload 8.26 MiB)
Admin bytes: 313 KiB initial messages, 0 B IP change messages, 917 B
disconnection notifications, 0 B routing status
Debugging bytes: 0 B network coloring, 0 B ping, 0 B probe requests, 0
B routed test messages.
Node to node messages: 564 KiB
Load allocation notices: 1.08 MiB
Other output: 28.0 MiB (8%)
Total non-request overhead: 6.19 KiB/sec (10%).
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Thu, Feb 10, 2011 at 8:49 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 On Saturday 05 Feb 2011 19:26:46 Juiceman wrote:
 On Sat, Feb 5, 2011 at 2:24 PM, Juiceman juicema...@gmail.com wrote:
  On Sat, Feb 5, 2011 at 2:17 PM, Juiceman juicema...@gmail.com wrote:
  On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
  t...@amphibian.dyndns.org wrote:
  We need more seednodes. I will explain the broader situation below. If 
  you can run a seednode - which means you need a forwarded port, a 
  reasonably static IP address (or dyndns name), and a reasonable amount 
  of bandwidth (especially upstream), and a reasonably stable node, please 
  send me your opennet noderef (from the strangers page in advanced mode), 
  and enable Be a seednode in the advanced config. Thanks.
 
  Details:
 
  One of the problems Freenet has at the moment is that bootstrapping a 
  new node can take an awfully long time - 20 minutes or more sometimes. 
  It is not clear why; we seem to either get rejected by seednodes (most 
  of the time), or they return nothing, maybe a few not wanted notices, 
  or they return lots of noderefs and we manage to announce.
 
  This might be due to bugs. 1343 fixed a bug that apparently badly 
  affected some seednodes. However it appears most seednodes have upgraded 
  now.
 
  There doesn't seem to be a problem with losing connections - backoff yes 
  but once a node is connected it seems to mostly stay connected.
 
  The most likely answer seems to be that we just don't have enough 
  seednodes to cope with the load.
 
  It is also possible that this is due to an attack. It did come on 
  relatively suddenly a few weeks ago (it was bad before but it got much 
  worse), and it seems to have got significantly worse in the last week. 
  It is not clear how we would identify an attack if that was the problem; 
  there are no obvious signs so far.
 
  It is also possible it is a client-side bug. Testing of the master 
  branch would be useful, it has some small changes.
 
 
  Errors in my log (build 1344)
 
  Also nodestats have been horrible on my seednode for last week or two.
   I am noticing node ping times in the 1500 - 3500 ms range.  Mostly
  during daytime hours here (GMT -5).  Not sure if ATT Uverse has
  quietly started throttling p2p (they say they don't), or if it is an
  attack or bug.  Seeding for 206 is typical and didn't kill my node in
  the past.  Let me know what logger settings to set and I can send you
  my logs if you want.
 
  Peer statistics
 
     * Connected: 15
     * Backed off: 3
     * Too old: 67
     * Disconnected: 13
     * Never connected: 5
     * Clock Problem: 1
     * Seeding for: 206
     * Max peers: 36
     * Max strangers: 36
 
  Bandwidth
 
     * Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
     * Output Rate: 31.6 KiB/s (of 105 KiB/s)
     * Session Total Input: 49.2 MiB (43.7 KiB/s average)
     * Session Total Output: 35.7 MiB (31.7 KiB/s average)
     * Payload Output: 214 KiB (190 B/sec)(0%)
 

 Node status overview

     * bwlimitDelayTime: 2947ms
     * bwlimitDelayTimeBulk: 2893ms
     * bwlimitDelayTimeRT: 9078ms
     * nodeAveragePingTime: 2315ms
     * darknetSizeEstimateSession: 0 nodes
     * opennetSizeEstimateSession: 833 nodes
     * nodeUptimeSession: 26m34s
     * nodeUptimeTotal: 8w2d
     * routingMissDistanceLocal: 0.0650
     * routingMissDistanceRemote: 0.0141
     * routingMissDistanceOverall: 0.0261
     * backedOffPercent: 22.3%
     * pInstantReject: 95.8%
     * unclaimedFIFOSize: 2663
     * RAMBucketPoolSize: 12.8 MiB / 150 MiB
     * uptimeAverage: 99.3%

 Ping times that high mean your node won't accept any requests at all, 
 although it might accept some announcements.

 Usually this is caused by network or CPU problems. When I've run my seednode 
 lately it hasn't had high ping times, nor have any of my other nodes.

 The NPE is fixed btw.

I have a tech coming out to diagnose my DSL issues, but the last
several builds have improved my ping times.
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Wonder why bootstrapping is slow

[Juiceman]

Bootstrapping from seednodes is really slow right now.? I run one of
those seednodes.? Here are my stats, they have been horrible for about
2 weeks now.? I don't suppose my node is serving many announcements,
huh?  Are other seednodes in similarly bad shape?

Node status overview

bwlimitDelayTime:?6706ms
bwlimitDelayTimeBulk:?6706ms
bwlimitDelayTimeRT:?0ms
nodeAveragePingTime:?2452ms
darknetSizeEstimateSession:?0?nodes
opennetSizeEstimateSession:?762?nodes
nodeUptimeSession:?44m57s
nodeUptimeTotal:?8w5d
routingMissDistanceLocal:?0.1065
routingMissDistanceRemote:?0.1270
routingMissDistanceOverall:?0.1234
backedOffPercent:?34.4%
pInstantReject:?92.5%
unclaimedFIFOSize:?4155
RAMBucketPoolSize:?12.5 MiB / 150 MiB
uptimeAverage:?97.2%

Peer statistics

Connected:?17
Backed off:?4
Too old:?65
Disconnected:?9
Never connected:?6
Disconnecting:?1
Seeding for:?199
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 42.2?KiB/s (of 1.0?MiB/s)
Output Rate: 31.2?KiB/s (of 105?KiB/s)
Session Total Input: 115?MiB (43.8?KiB/s average)
Session Total Output: 86.0?MiB (32.6?KiB/s average)
Payload Output: 253?KiB (96?B/sec)(0%)
Global Total Input: 357?GiB
Global Total Output: 422?GiB
Request output (excluding payload): CHK 39.7?KiB SSK 111?KiB.
Insert output (excluding payload): CHK 7.53?KiB SSK 1.70?KiB.
Offered keys: sending keys 100?B, sending offers 1016?B
Swapping Output: 1.99?MiB.
Connection setup: 30.3?MiB output
Ack-only packets: 31.6?MiB
Resent bytes: 5.83?MiB (6%)
Updater Output: 104?KiB
Announcement output: 6.29?MiB (transferring node refs payload 6.48?MiB)
Admin bytes: 1.08?MiB initial messages, 1.37?KiB IP change messages,
2.10?KiB disconnection notifications, 0?B routing status
Debugging bytes: 0?B network coloring, 0?B ping, 6.12?KiB probe
requests, 0?B routed test messages.
Node to node messages: 1.45?MiB
Load allocation notices: 288?KiB
Other output: 6.59?MiB (7%)
Total non-request overhead: 31.4 KiB/sec (96%).

[freenet-dev] Wonder why bootstrapping is slow

[Juiceman]

Bootstrapping from seednodes is really slow right now.  I run one of
those seednodes.  Here are my stats, they have been horrible for about
2 weeks now.  I don't suppose my node is serving many announcements,
huh?  Are other seednodes in similarly bad shape?

Node status overview

bwlimitDelayTime: 6706ms
bwlimitDelayTimeBulk: 6706ms
bwlimitDelayTimeRT: 0ms
nodeAveragePingTime: 2452ms
darknetSizeEstimateSession: 0 nodes
opennetSizeEstimateSession: 762 nodes
nodeUptimeSession: 44m57s
nodeUptimeTotal: 8w5d
routingMissDistanceLocal: 0.1065
routingMissDistanceRemote: 0.1270
routingMissDistanceOverall: 0.1234
backedOffPercent: 34.4%
pInstantReject: 92.5%
unclaimedFIFOSize: 4155
RAMBucketPoolSize: 12.5 MiB / 150 MiB
uptimeAverage: 97.2%

Peer statistics

Connected: 17
Backed off: 4
Too old: 65
Disconnected: 9
Never connected: 6
Disconnecting: 1
Seeding for: 199
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 42.2 KiB/s (of 1.0 MiB/s)
Output Rate: 31.2 KiB/s (of 105 KiB/s)
Session Total Input: 115 MiB (43.8 KiB/s average)
Session Total Output: 86.0 MiB (32.6 KiB/s average)
Payload Output: 253 KiB (96 B/sec)(0%)
Global Total Input: 357 GiB
Global Total Output: 422 GiB
Request output (excluding payload): CHK 39.7 KiB SSK 111 KiB.
Insert output (excluding payload): CHK 7.53 KiB SSK 1.70 KiB.
Offered keys: sending keys 100 B, sending offers 1016 B
Swapping Output: 1.99 MiB.
Connection setup: 30.3 MiB output
Ack-only packets: 31.6 MiB
Resent bytes: 5.83 MiB (6%)
Updater Output: 104 KiB
Announcement output: 6.29 MiB (transferring node refs payload 6.48 MiB)
Admin bytes: 1.08 MiB initial messages, 1.37 KiB IP change messages,
2.10 KiB disconnection notifications, 0 B routing status
Debugging bytes: 0 B network coloring, 0 B ping, 6.12 KiB probe
requests, 0 B routed test messages.
Node to node messages: 1.45 MiB
Load allocation notices: 288 KiB
Other output: 6.59 MiB (7%)
Total non-request overhead: 31.4 KiB/sec (96%).
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:17 PM, Juiceman  wrote:
> On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
>  wrote:
>> We need more seednodes. I will explain the broader situation below. If you 
>> can run a seednode - which means you need a forwarded port, a reasonably 
>> static IP address (or dyndns name), and a reasonable amount of bandwidth 
>> (especially upstream), and a reasonably stable node, please send me your 
>> opennet noderef (from the strangers page in advanced mode), and enable "Be a 
>> seednode" in the advanced config. Thanks.
>>
>> Details:
>>
>> One of the problems Freenet has at the moment is that bootstrapping a new 
>> node can take an awfully long time - 20 minutes or more sometimes. It is not 
>> clear why; we seem to either get rejected by seednodes (most of the time), 
>> or they return nothing, maybe a few "not wanted" notices, or they return 
>> lots of noderefs and we manage to announce.
>>
>> This might be due to bugs. 1343 fixed a bug that apparently badly affected 
>> some seednodes. However it appears most seednodes have upgraded now.
>>
>> There doesn't seem to be a problem with losing connections - backoff yes but 
>> once a node is connected it seems to mostly stay connected.
>>
>> The most likely answer seems to be that we just don't have enough seednodes 
>> to cope with the load.
>>
>> It is also possible that this is due to an attack. It did come on relatively 
>> suddenly a few weeks ago (it was bad before but it got much worse), and it 
>> seems to have got significantly worse in the last week. It is not clear how 
>> we would identify an attack if that was the problem; there are no obvious 
>> signs so far.
>>
>> It is also possible it is a client-side bug. Testing of the master branch 
>> would be useful, it has some small changes.
>>
>

(More) Errors in my log (build 1344)

Feb 05, 2011 19:09:21:468 (freenet.io.xfer.BlockReceiver$3$1,
(576), ERROR): Other side did not acknowlege transfer failure
on freenet.io.xfer.BlockReceiver at 
12e7d4e:5083681545186716019:freenet.node.OpennetPeerNode at 
42831fde@119.237.181.5:17829 at 
6970775c69d506563ac265b939f5d0884a99ba19f5b8483841de847a36e0709c
Feb 05, 2011 19:09:21:468 (freenet.node.RequestSender$7,
(576), ERROR): Fatal timeout receiving requested block on
freenet.node.RequestSender$7 at 124baa6 from
freenet.node.OpennetPeerNode at 42831fde@119.237.181.5:17829 at 
6970775c69d506563ac265b939f5d0884a99ba19f5b8483841de847a36e0709c@d9b967
Feb 05, 2011 19:09:22:999 (freenet.io.comm.MessageCore,
UdpSocketHandler for port 8476(1), ERROR): Dispatcher threw
java.lang.NullPointerException
java.lang.NullPointerException
at freenet.node.PeerNode.getPeerNodeStatus(PeerNode.java:3496)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3550)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.NodeDispatcher.handleMessage(NodeDispatcher.java:193)
at freenet.io.comm.MessageCore.checkFilters(MessageCore.java:233)
at freenet.node.PeerNode.handleMessage(PeerNode.java:4954)
at 
freenet.node.PeerNode$MyDecodingMessageGroup.complete(PeerNode.java:5055)
at 
freenet.node.NewPacketFormat.handleReceivedPacket(NewPacketFormat.java:127)
at freenet.node.PeerNode.handleReceivedPacket(PeerNode.java:4926)
at 
freenet.io.comm.IncomingPacketFilterImpl.process(IncomingPacketFilterImpl.java:62)
at freenet.io.comm.UdpSocketHandler.realRun(UdpSocketHandler.java:171)
at freenet.io.comm.UdpSocketHandler.runLoop(UdpSocketHandler.java:137)
at freenet.io.comm.UdpSocketHandler.run(UdpSocketHandler.java:94)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227)
at freenet.support.io.NativeThread.run(NativeThread.java:130)
Feb 05, 2011 19:09:23:593 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Unknown neg type: 5
Feb 05, 2011 19:09:30:468 (freenet.node.PeerManager, UdpSocketHandler
for port 8476(1), ERROR): removePeerNodeStatus(): identity
'ok4pyMM2Pddv~g1GOwHyZMMxBFycY0nPNI6irEd1WTA for
freenet.node.OpennetPeerNode at b72265c8@77.58.193.66:55131 at 
a24e29c8c3363dd76ffa0d463b01f264c331045c9c6349cf348ea2ac47755930'
not in peerNodeStatuses with status 'BACKED OFF'
java.lang.Exception: debug
at freenet.node.PeerManager.removePeerNodeStatus(PeerManager.java:1585)
at freenet.node.PeerManager.removePeerNodeStatus(PeerManager.java:1573)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3553)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.N

[freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:24 PM, Juiceman  wrote:
> On Sat, Feb 5, 2011 at 2:17 PM, Juiceman  wrote:
>> On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
>>  wrote:
>>> We need more seednodes. I will explain the broader situation below. If you 
>>> can run a seednode - which means you need a forwarded port, a reasonably 
>>> static IP address (or dyndns name), and a reasonable amount of bandwidth 
>>> (especially upstream), and a reasonably stable node, please send me your 
>>> opennet noderef (from the strangers page in advanced mode), and enable "Be 
>>> a seednode" in the advanced config. Thanks.
>>>
>>> Details:
>>>
>>> One of the problems Freenet has at the moment is that bootstrapping a new 
>>> node can take an awfully long time - 20 minutes or more sometimes. It is 
>>> not clear why; we seem to either get rejected by seednodes (most of the 
>>> time), or they return nothing, maybe a few "not wanted" notices, or they 
>>> return lots of noderefs and we manage to announce.
>>>
>>> This might be due to bugs. 1343 fixed a bug that apparently badly affected 
>>> some seednodes. However it appears most seednodes have upgraded now.
>>>
>>> There doesn't seem to be a problem with losing connections - backoff yes 
>>> but once a node is connected it seems to mostly stay connected.
>>>
>>> The most likely answer seems to be that we just don't have enough seednodes 
>>> to cope with the load.
>>>
>>> It is also possible that this is due to an attack. It did come on 
>>> relatively suddenly a few weeks ago (it was bad before but it got much 
>>> worse), and it seems to have got significantly worse in the last week. It 
>>> is not clear how we would identify an attack if that was the problem; there 
>>> are no obvious signs so far.
>>>
>>> It is also possible it is a client-side bug. Testing of the master branch 
>>> would be useful, it has some small changes.
>>>
>>
>> Errors in my log (build 1344)
>
> Also nodestats have been horrible on my seednode for last week or two.
> ?I am noticing node ping times in the 1500 - 3500 ms range. ?Mostly
> during daytime hours here (GMT -5). ?Not sure if ATT Uverse has
> quietly started throttling p2p (they say they don't), or if it is an
> attack or bug. ?Seeding for 206 is typical and didn't kill my node in
> the past. ?Let me know what logger settings to set and I can send you
> my logs if you want.
>
> Peer statistics
>
> ? ?* Connected: 15
> ? ?* Backed off: 3
> ? ?* Too old: 67
> ? ?* Disconnected: 13
> ? ?* Never connected: 5
> ? ?* Clock Problem: 1
> ? ?* Seeding for: 206
> ? ?* Max peers: 36
> ? ?* Max strangers: 36
>
> Bandwidth
>
> ? ?* Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
> ? ?* Output Rate: 31.6 KiB/s (of 105 KiB/s)
> ? ?* Session Total Input: 49.2 MiB (43.7 KiB/s average)
> ? ?* Session Total Output: 35.7 MiB (31.7 KiB/s average)
> ? ?* Payload Output: 214 KiB (190 B/sec)(0%)
>

Node status overview

* bwlimitDelayTime: 2947ms
* bwlimitDelayTimeBulk: 2893ms
* bwlimitDelayTimeRT: 9078ms
* nodeAveragePingTime: 2315ms
* darknetSizeEstimateSession: 0 nodes
* opennetSizeEstimateSession: 833 nodes
* nodeUptimeSession: 26m34s
* nodeUptimeTotal: 8w2d
* routingMissDistanceLocal: 0.0650
* routingMissDistanceRemote: 0.0141
* routingMissDistanceOverall: 0.0261
* backedOffPercent: 22.3%
* pInstantReject: 95.8%
* unclaimedFIFOSize: 2663
* RAMBucketPoolSize: 12.8 MiB / 150 MiB
* uptimeAverage: 99.3%

[freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:17 PM, Juiceman  wrote:
> On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
>  wrote:
>> We need more seednodes. I will explain the broader situation below. If you 
>> can run a seednode - which means you need a forwarded port, a reasonably 
>> static IP address (or dyndns name), and a reasonable amount of bandwidth 
>> (especially upstream), and a reasonably stable node, please send me your 
>> opennet noderef (from the strangers page in advanced mode), and enable "Be a 
>> seednode" in the advanced config. Thanks.
>>
>> Details:
>>
>> One of the problems Freenet has at the moment is that bootstrapping a new 
>> node can take an awfully long time - 20 minutes or more sometimes. It is not 
>> clear why; we seem to either get rejected by seednodes (most of the time), 
>> or they return nothing, maybe a few "not wanted" notices, or they return 
>> lots of noderefs and we manage to announce.
>>
>> This might be due to bugs. 1343 fixed a bug that apparently badly affected 
>> some seednodes. However it appears most seednodes have upgraded now.
>>
>> There doesn't seem to be a problem with losing connections - backoff yes but 
>> once a node is connected it seems to mostly stay connected.
>>
>> The most likely answer seems to be that we just don't have enough seednodes 
>> to cope with the load.
>>
>> It is also possible that this is due to an attack. It did come on relatively 
>> suddenly a few weeks ago (it was bad before but it got much worse), and it 
>> seems to have got significantly worse in the last week. It is not clear how 
>> we would identify an attack if that was the problem; there are no obvious 
>> signs so far.
>>
>> It is also possible it is a client-side bug. Testing of the master branch 
>> would be useful, it has some small changes.
>>
>
> Errors in my log (build 1344)

Also nodestats have been horrible on my seednode for last week or two.
 I am noticing node ping times in the 1500 - 3500 ms range.  Mostly
during daytime hours here (GMT -5).  Not sure if ATT Uverse has
quietly started throttling p2p (they say they don't), or if it is an
attack or bug.  Seeding for 206 is typical and didn't kill my node in
the past.  Let me know what logger settings to set and I can send you
my logs if you want.

Peer statistics

* Connected: 15
* Backed off: 3
* Too old: 67
* Disconnected: 13
* Never connected: 5
* Clock Problem: 1
* Seeding for: 206
* Max peers: 36
* Max strangers: 36

Bandwidth

* Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
* Output Rate: 31.6 KiB/s (of 105 KiB/s)
* Session Total Input: 49.2 MiB (43.7 KiB/s average)
* Session Total Output: 35.7 MiB (31.7 KiB/s average)
* Payload Output: 214 KiB (190 B/sec)(0%)

[freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
 wrote:
> We need more seednodes. I will explain the broader situation below. If you 
> can run a seednode - which means you need a forwarded port, a reasonably 
> static IP address (or dyndns name), and a reasonable amount of bandwidth 
> (especially upstream), and a reasonably stable node, please send me your 
> opennet noderef (from the strangers page in advanced mode), and enable "Be a 
> seednode" in the advanced config. Thanks.
>
> Details:
>
> One of the problems Freenet has at the moment is that bootstrapping a new 
> node can take an awfully long time - 20 minutes or more sometimes. It is not 
> clear why; we seem to either get rejected by seednodes (most of the time), or 
> they return nothing, maybe a few "not wanted" notices, or they return lots of 
> noderefs and we manage to announce.
>
> This might be due to bugs. 1343 fixed a bug that apparently badly affected 
> some seednodes. However it appears most seednodes have upgraded now.
>
> There doesn't seem to be a problem with losing connections - backoff yes but 
> once a node is connected it seems to mostly stay connected.
>
> The most likely answer seems to be that we just don't have enough seednodes 
> to cope with the load.
>
> It is also possible that this is due to an attack. It did come on relatively 
> suddenly a few weeks ago (it was bad before but it got much worse), and it 
> seems to have got significantly worse in the last week. It is not clear how 
> we would identify an attack if that was the problem; there are no obvious 
> signs so far.
>
> It is also possible it is a client-side bug. Testing of the master branch 
> would be useful, it has some small changes.
>

Errors in my log (build 1344)

Feb 05, 2011 19:02:26:530 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:26:968 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:030 (freenet.io.comm.MessageCore,
UdpSocketHandler for port 8476(1), ERROR): Dispatcher threw
java.lang.NullPointerException
java.lang.NullPointerException
at freenet.node.PeerNode.getPeerNodeStatus(PeerNode.java:3496)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3550)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.NodeDispatcher.handleMessage(NodeDispatcher.java:193)
at freenet.io.comm.MessageCore.checkFilters(MessageCore.java:233)
at freenet.node.PeerNode.handleMessage(PeerNode.java:4954)
at 
freenet.node.PeerNode$MyDecodingMessageGroup.complete(PeerNode.java:5055)
at 
freenet.node.NewPacketFormat.handleReceivedPacket(NewPacketFormat.java:127)
at freenet.node.PeerNode.handleReceivedPacket(PeerNode.java:4926)
at 
freenet.io.comm.IncomingPacketFilterImpl.process(IncomingPacketFilterImpl.java:62)
at freenet.io.comm.UdpSocketHandler.realRun(UdpSocketHandler.java:171)
at freenet.io.comm.UdpSocketHandler.runLoop(UdpSocketHandler.java:137)
at freenet.io.comm.UdpSocketHandler.run(UdpSocketHandler.java:94)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227)
at freenet.support.io.NativeThread.run(NativeThread.java:130)
Feb 05, 2011 19:02:28:343 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:546 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Unknown neg type: 5
Feb 05, 2011 19:02:28:640 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:718 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:32:952 (freenet.io.xfer.PacketThrottle,
Announcement sender for -6664479198334775233(57), ERROR): Unable to
send throttled message, waited 3ms
Feb 05, 2011 19:02:32:952 (freenet.io.xfer.BulkTransmitter,
Announcement sender for -6664479198334775233(57), ERROR): Failed to
send bulk packet 2 for
BulkTransmitter:3594291877902462283:freenet.node.SeedClientPeerNode at 
332c6e37@198.166.24.103:17593 at 
774cd7d61d346340f5a2f2802d53ef2950bccd9519a7bf3e3245a91736f8f43a
RTT is 0s
Feb 05, 2011 19:02:42:374 

Re: [freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
 We need more seednodes. I will explain the broader situation below. If you 
 can run a seednode - which means you need a forwarded port, a reasonably 
 static IP address (or dyndns name), and a reasonable amount of bandwidth 
 (especially upstream), and a reasonably stable node, please send me your 
 opennet noderef (from the strangers page in advanced mode), and enable Be a 
 seednode in the advanced config. Thanks.

 Details:

 One of the problems Freenet has at the moment is that bootstrapping a new 
 node can take an awfully long time - 20 minutes or more sometimes. It is not 
 clear why; we seem to either get rejected by seednodes (most of the time), or 
 they return nothing, maybe a few not wanted notices, or they return lots of 
 noderefs and we manage to announce.

 This might be due to bugs. 1343 fixed a bug that apparently badly affected 
 some seednodes. However it appears most seednodes have upgraded now.

 There doesn't seem to be a problem with losing connections - backoff yes but 
 once a node is connected it seems to mostly stay connected.

 The most likely answer seems to be that we just don't have enough seednodes 
 to cope with the load.

 It is also possible that this is due to an attack. It did come on relatively 
 suddenly a few weeks ago (it was bad before but it got much worse), and it 
 seems to have got significantly worse in the last week. It is not clear how 
 we would identify an attack if that was the problem; there are no obvious 
 signs so far.

 It is also possible it is a client-side bug. Testing of the master branch 
 would be useful, it has some small changes.


Errors in my log (build 1344)

Feb 05, 2011 19:02:26:530 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:26:968 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:030 (freenet.io.comm.MessageCore,
UdpSocketHandler for port 8476(1), ERROR): Dispatcher threw
java.lang.NullPointerException
java.lang.NullPointerException
at freenet.node.PeerNode.getPeerNodeStatus(PeerNode.java:3496)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3550)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.NodeDispatcher.handleMessage(NodeDispatcher.java:193)
at freenet.io.comm.MessageCore.checkFilters(MessageCore.java:233)
at freenet.node.PeerNode.handleMessage(PeerNode.java:4954)
at 
freenet.node.PeerNode$MyDecodingMessageGroup.complete(PeerNode.java:5055)
at 
freenet.node.NewPacketFormat.handleReceivedPacket(NewPacketFormat.java:127)
at freenet.node.PeerNode.handleReceivedPacket(PeerNode.java:4926)
at 
freenet.io.comm.IncomingPacketFilterImpl.process(IncomingPacketFilterImpl.java:62)
at freenet.io.comm.UdpSocketHandler.realRun(UdpSocketHandler.java:171)
at freenet.io.comm.UdpSocketHandler.runLoop(UdpSocketHandler.java:137)
at freenet.io.comm.UdpSocketHandler.run(UdpSocketHandler.java:94)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227)
at freenet.support.io.NativeThread.run(NativeThread.java:130)
Feb 05, 2011 19:02:28:343 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:546 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Unknown neg type: 5
Feb 05, 2011 19:02:28:640 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:28:718 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Last resort match anon-auth
against all anon setup peernodes succeeded - this should not happen!
(It can happen if they change address)
Feb 05, 2011 19:02:32:952 (freenet.io.xfer.PacketThrottle,
Announcement sender for -6664479198334775233(57), ERROR): Unable to
send throttled message, waited 3ms
Feb 05, 2011 19:02:32:952 (freenet.io.xfer.BulkTransmitter,
Announcement sender for -6664479198334775233(57), ERROR): Failed to
send bulk packet 2 for
BulkTransmitter:3594291877902462283:freenet.node.SeedClientPeerNode@332c6e37@198.166.24.103:17593@774cd7d61d346340f5a2f2802d53ef2950bccd9519a7bf3e3245a91736f8f43a
RTT is 0s
Feb 05, 2011 19:02:42:374 

Re: [freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:17 PM, Juiceman juicema...@gmail.com wrote:
 On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
 t...@amphibian.dyndns.org wrote:
 We need more seednodes. I will explain the broader situation below. If you 
 can run a seednode - which means you need a forwarded port, a reasonably 
 static IP address (or dyndns name), and a reasonable amount of bandwidth 
 (especially upstream), and a reasonably stable node, please send me your 
 opennet noderef (from the strangers page in advanced mode), and enable Be a 
 seednode in the advanced config. Thanks.

 Details:

 One of the problems Freenet has at the moment is that bootstrapping a new 
 node can take an awfully long time - 20 minutes or more sometimes. It is not 
 clear why; we seem to either get rejected by seednodes (most of the time), 
 or they return nothing, maybe a few not wanted notices, or they return 
 lots of noderefs and we manage to announce.

 This might be due to bugs. 1343 fixed a bug that apparently badly affected 
 some seednodes. However it appears most seednodes have upgraded now.

 There doesn't seem to be a problem with losing connections - backoff yes but 
 once a node is connected it seems to mostly stay connected.

 The most likely answer seems to be that we just don't have enough seednodes 
 to cope with the load.

 It is also possible that this is due to an attack. It did come on relatively 
 suddenly a few weeks ago (it was bad before but it got much worse), and it 
 seems to have got significantly worse in the last week. It is not clear how 
 we would identify an attack if that was the problem; there are no obvious 
 signs so far.

 It is also possible it is a client-side bug. Testing of the master branch 
 would be useful, it has some small changes.


 Errors in my log (build 1344)

Also nodestats have been horrible on my seednode for last week or two.
 I am noticing node ping times in the 1500 - 3500 ms range.  Mostly
during daytime hours here (GMT -5).  Not sure if ATT Uverse has
quietly started throttling p2p (they say they don't), or if it is an
attack or bug.  Seeding for 206 is typical and didn't kill my node in
the past.  Let me know what logger settings to set and I can send you
my logs if you want.

Peer statistics

* Connected: 15
* Backed off: 3
* Too old: 67
* Disconnected: 13
* Never connected: 5
* Clock Problem: 1
* Seeding for: 206
* Max peers: 36
* Max strangers: 36

Bandwidth

* Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
* Output Rate: 31.6 KiB/s (of 105 KiB/s)
* Session Total Input: 49.2 MiB (43.7 KiB/s average)
* Session Total Output: 35.7 MiB (31.7 KiB/s average)
* Payload Output: 214 KiB (190 B/sec)(0%)
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:24 PM, Juiceman juicema...@gmail.com wrote:
 On Sat, Feb 5, 2011 at 2:17 PM, Juiceman juicema...@gmail.com wrote:
 On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
 t...@amphibian.dyndns.org wrote:
 We need more seednodes. I will explain the broader situation below. If you 
 can run a seednode - which means you need a forwarded port, a reasonably 
 static IP address (or dyndns name), and a reasonable amount of bandwidth 
 (especially upstream), and a reasonably stable node, please send me your 
 opennet noderef (from the strangers page in advanced mode), and enable Be 
 a seednode in the advanced config. Thanks.

 Details:

 One of the problems Freenet has at the moment is that bootstrapping a new 
 node can take an awfully long time - 20 minutes or more sometimes. It is 
 not clear why; we seem to either get rejected by seednodes (most of the 
 time), or they return nothing, maybe a few not wanted notices, or they 
 return lots of noderefs and we manage to announce.

 This might be due to bugs. 1343 fixed a bug that apparently badly affected 
 some seednodes. However it appears most seednodes have upgraded now.

 There doesn't seem to be a problem with losing connections - backoff yes 
 but once a node is connected it seems to mostly stay connected.

 The most likely answer seems to be that we just don't have enough seednodes 
 to cope with the load.

 It is also possible that this is due to an attack. It did come on 
 relatively suddenly a few weeks ago (it was bad before but it got much 
 worse), and it seems to have got significantly worse in the last week. It 
 is not clear how we would identify an attack if that was the problem; there 
 are no obvious signs so far.

 It is also possible it is a client-side bug. Testing of the master branch 
 would be useful, it has some small changes.


 Errors in my log (build 1344)

 Also nodestats have been horrible on my seednode for last week or two.
  I am noticing node ping times in the 1500 - 3500 ms range.  Mostly
 during daytime hours here (GMT -5).  Not sure if ATT Uverse has
 quietly started throttling p2p (they say they don't), or if it is an
 attack or bug.  Seeding for 206 is typical and didn't kill my node in
 the past.  Let me know what logger settings to set and I can send you
 my logs if you want.

 Peer statistics

    * Connected: 15
    * Backed off: 3
    * Too old: 67
    * Disconnected: 13
    * Never connected: 5
    * Clock Problem: 1
    * Seeding for: 206
    * Max peers: 36
    * Max strangers: 36

 Bandwidth

    * Input Rate: 48.2 KiB/s (of 1.0 MiB/s)
    * Output Rate: 31.6 KiB/s (of 105 KiB/s)
    * Session Total Input: 49.2 MiB (43.7 KiB/s average)
    * Session Total Output: 35.7 MiB (31.7 KiB/s average)
    * Payload Output: 214 KiB (190 B/sec)(0%)


Node status overview

* bwlimitDelayTime: 2947ms
* bwlimitDelayTimeBulk: 2893ms
* bwlimitDelayTimeRT: 9078ms
* nodeAveragePingTime: 2315ms
* darknetSizeEstimateSession: 0 nodes
* opennetSizeEstimateSession: 833 nodes
* nodeUptimeSession: 26m34s
* nodeUptimeTotal: 8w2d
* routingMissDistanceLocal: 0.0650
* routingMissDistanceRemote: 0.0141
* routingMissDistanceOverall: 0.0261
* backedOffPercent: 22.3%
* pInstantReject: 95.8%
* unclaimedFIFOSize: 2663
* RAMBucketPoolSize: 12.8 MiB / 150 MiB
* uptimeAverage: 99.3%
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] [freenet-support] Call for seednodes and explanation of current problems

[Juiceman]

On Sat, Feb 5, 2011 at 2:17 PM, Juiceman juicema...@gmail.com wrote:
 On Sat, Feb 5, 2011 at 1:39 PM, Matthew Toseland
 t...@amphibian.dyndns.org wrote:
 We need more seednodes. I will explain the broader situation below. If you 
 can run a seednode - which means you need a forwarded port, a reasonably 
 static IP address (or dyndns name), and a reasonable amount of bandwidth 
 (especially upstream), and a reasonably stable node, please send me your 
 opennet noderef (from the strangers page in advanced mode), and enable Be a 
 seednode in the advanced config. Thanks.

 Details:

 One of the problems Freenet has at the moment is that bootstrapping a new 
 node can take an awfully long time - 20 minutes or more sometimes. It is not 
 clear why; we seem to either get rejected by seednodes (most of the time), 
 or they return nothing, maybe a few not wanted notices, or they return 
 lots of noderefs and we manage to announce.

 This might be due to bugs. 1343 fixed a bug that apparently badly affected 
 some seednodes. However it appears most seednodes have upgraded now.

 There doesn't seem to be a problem with losing connections - backoff yes but 
 once a node is connected it seems to mostly stay connected.

 The most likely answer seems to be that we just don't have enough seednodes 
 to cope with the load.

 It is also possible that this is due to an attack. It did come on relatively 
 suddenly a few weeks ago (it was bad before but it got much worse), and it 
 seems to have got significantly worse in the last week. It is not clear how 
 we would identify an attack if that was the problem; there are no obvious 
 signs so far.

 It is also possible it is a client-side bug. Testing of the master branch 
 would be useful, it has some small changes.



(More) Errors in my log (build 1344)

Feb 05, 2011 19:09:21:468 (freenet.io.xfer.BlockReceiver$3$1,
noname(576), ERROR): Other side did not acknowlege transfer failure
on 
freenet.io.xfer.BlockReceiver@12e7d4e:5083681545186716019:freenet.node.OpennetPeerNode@42831fde@119.237.181.5:17829@6970775c69d506563ac265b939f5d0884a99ba19f5b8483841de847a36e0709c
Feb 05, 2011 19:09:21:468 (freenet.node.RequestSender$7,
noname(576), ERROR): Fatal timeout receiving requested block on
freenet.node.RequestSender$7@124baa6 from
freenet.node.OpennetPeerNode@42831fde@119.237.181.5:17829@6970775c69d506563ac265b939f5d0884a99ba19f5b8483841de847a36e0709c@d9b967
Feb 05, 2011 19:09:22:999 (freenet.io.comm.MessageCore,
UdpSocketHandler for port 8476(1), ERROR): Dispatcher threw
java.lang.NullPointerException
java.lang.NullPointerException
at freenet.node.PeerNode.getPeerNodeStatus(PeerNode.java:3496)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3550)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.NodeDispatcher.handleMessage(NodeDispatcher.java:193)
at freenet.io.comm.MessageCore.checkFilters(MessageCore.java:233)
at freenet.node.PeerNode.handleMessage(PeerNode.java:4954)
at 
freenet.node.PeerNode$MyDecodingMessageGroup.complete(PeerNode.java:5055)
at 
freenet.node.NewPacketFormat.handleReceivedPacket(NewPacketFormat.java:127)
at freenet.node.PeerNode.handleReceivedPacket(PeerNode.java:4926)
at 
freenet.io.comm.IncomingPacketFilterImpl.process(IncomingPacketFilterImpl.java:62)
at freenet.io.comm.UdpSocketHandler.realRun(UdpSocketHandler.java:171)
at freenet.io.comm.UdpSocketHandler.runLoop(UdpSocketHandler.java:137)
at freenet.io.comm.UdpSocketHandler.run(UdpSocketHandler.java:94)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:227)
at freenet.support.io.NativeThread.run(NativeThread.java:130)
Feb 05, 2011 19:09:23:593 (freenet.node.FNPPacketMangler,
UdpSocketHandler for port 8476(1), ERROR): Unknown neg type: 5
Feb 05, 2011 19:09:30:468 (freenet.node.PeerManager, UdpSocketHandler
for port 8476(1), ERROR): removePeerNodeStatus(): identity
'ok4pyMM2Pddv~g1GOwHyZMMxBFycY0nPNI6irEd1WTA for
freenet.node.OpennetPeerNode@b72265c8@77.58.193.66:55131@a24e29c8c3363dd76ffa0d463b01f264c331045c9c6349cf348ea2ac47755930'
not in peerNodeStatuses with status 'BACKED OFF'
java.lang.Exception: debug
at freenet.node.PeerManager.removePeerNodeStatus(PeerManager.java:1585)
at freenet.node.PeerManager.removePeerNodeStatus(PeerManager.java:1573)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3553)
at freenet.node.PeerNode.setPeerNodeStatus(PeerNode.java:3538)
at freenet.node.PeerNode.updateLocation(PeerNode.java:1740)
at freenet.node.NodeDispatcher.handleMessage(NodeDispatcher.java:193)
at freenet.io.comm.MessageCore.checkFilters(MessageCore.java:233)
at freenet.node.PeerNode.handleMessage(PeerNode.java:4954)
at 
freenet.node.PeerNode$MyDecodingMessageGroup.complete

[freenet-dev] Please test the new load management branch

[Juiceman]

On Sat, Jan 29, 2011 at 7:30 PM, Matthew Toseland
 wrote:
>
> Please get the snapshot (update.cmd testing / update.sh testing), and test 
> it. I want to know if it causes serious problems, and also any other bugs you 
> run into. I know there will be various errors, but I am still interested in 
> the more severe ones.
>
> For people building from source:
> The tag is: testing-build-1340-maybe-merge-new-load-management-pre1
> The branch is: merge-new-load-management
> The git rev is 47edfe611a1f088b51fccb36d3e7710e28c3d2b8 (that commit does 
> matter despite it appearing to be a logging fix).
>
> THANKS!

My seednode is not too healthy:

Node Version Information

* Freenet 0.7.5 Build #1339
testing-build-1340-maybe-merge-new-load-management-pre1
* Freenet-ext Build #26 r23771

Java Info

* Used Java memory: 138 MiB
* Allocated Java memory: 216 MiB
* Maximum Java memory: 870 MiB
* Running threads: 302/750
* Available CPUs: 4
* Java Version: 1.6.0_23
* Java VM Vendor: Sun Microsystems Inc.
* Java VM Name: Java HotSpot(TM) Client VM
* Java VM Version: 19.0-b09
* OS Name: Windows XP
* OS Version: 5.1
* OS Architecture: x86

Node status overview

bwlimitDelayTime:?1464ms
bwlimitDelayTimeBulk:?1464ms
bwlimitDelayTimeRT:?892ms
nodeAveragePingTime:?942ms
darknetSizeEstimateSession:?0?nodes
opennetSizeEstimateSession:?2560?nodes
nodeUptimeSession:?1h39m
nodeUptimeTotal:?7w3d
routingMissDistanceLocal:?0.1437
routingMissDistanceRemote:?0.1598
routingMissDistanceOverall:?0.1587
backedOffPercent:?80.3%
pInstantReject:?25.0%
unclaimedFIFOSize:?3045
RAMBucketPoolSize:?21.8 MiB / 150 MiB
uptimeAverage:?99.8%

Peer statistics

Connected:?10
Backed off:?18
Too old:?77
Disconnected:?7
Never connected:?1
Clock Problem:?1
Disconnecting:?1
Seeding for:?142
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 102?KiB/s (of 1.0?MiB/s)
Output Rate: 110?KiB/s (of 105?KiB/s)
Session Total Input: 425?MiB (73.1?KiB/s average)
Session Total Output: 634?MiB (108?KiB/s average)
Payload Output: 6.16?MiB (1.05?KiB/sec)(0%)
Global Total Input: 315?GiB
Global Total Output: 371?GiB
Request output (excluding payload): CHK 381?KiB SSK 1.51?MiB.
Insert output (excluding payload): CHK 122?KiB SSK 29.7?KiB.
Offered keys: sending keys 58.6?KiB, sending offers 27.6?KiB
Swapping Output: 2.85?MiB.
Connection setup: 58.0?MiB output
Ack-only packets: 57.5?MiB
Resent bytes: 418?MiB  (WTF is with this one?)
Updater Output: 366?KiB
Announcement output: 20.3?MiB (transferring node refs payload 15.5?MiB)
Admin bytes: 1.23?MiB initial messages, 2.59?KiB IP change messages,
14.5?KiB disconnection notifications, 0?B routing status
Debugging bytes: 0?B network coloring, 0?B ping, 0?B probe requests, 0
B routed test messages.
Node to node messages: 1.39?MiB
Load allocation notices: 257?KiB
Other output: 65.5?MiB (10%)
Total non-request overhead: 98.3 KiB/sec (90%).

Peer Backoff
Current backoff reasons (bulk)

AcceptedTimeout?4
ForwardRejectedOverload?4
SENDER_DIED?1
SendSyncTimeout?3
TransferFailedRequest7?1

Current backoff reasons (realtime)

AcceptedTimeout?3
FatalTimeout?1
ForwardRejectedOverload?8
SENDER_DIED?2
SendSyncTimeout?3
TransferFailedRequest5?1

Routing Backoff Reason (bulk)CountAvg. TimeTotal Time
SendSyncTimeout512m32s2h9m
Timeout61m53s11m18s
AcceptedTimeout2001m10s3h55m
ForwardRejectedOverload20231.364s1h45m
ForwardRejectedOverload31321.043s4m33s
Timeout3812.321s1m38s
TransferFailedRequest5723.130s3m45s
TimedOutAwaitingDataInsert11.758s1.758s
ForwardRejectedOverload5121.348s16.177s
TransferFailedRequest781.176s9.410s
TransferFailedInsert171.074s18.260s
Routing Backoff Reason (realtime)CountAvg. TimeTotal Time
SendSyncTimeout565m5s4h45m
ForwardRejectedOverload1224m17s8h42m
AcceptedTimeout1821m10s3h32m
FatalTimeoutForked342.111s2m6s
TransferFailedRequest510432.716s56m42s
FatalTimeout3010.567s5m17s
ForwardRejectedOverload2198.198s2m35s
TransferFailedRequest711.283s1.283s
Transfer Backoff Reason (bulk)CountAvg. TimeTotal Time
SENDER_DIED533m3s2h42m
RequestSenderGetOfferedTransferFailed148.327s48.327s
Transfer Backoff Reason (realtime)CountAvg. TimeTotal Time
SENDER_DIED915m54s8h57m
Location swaps

location:?0.22831853895397802
averageSwapTime:?8.000s
sendSwapInterval:?8.000s

unclaimedFIFO Message Counts

FNPPeerLoadStatusByte:?1545?(50.7%)
FNPBulkPacketSend:?379?(12.4%)
FNPOpennetAnnounceNodeNotWanted:?334?(11.0%)
FNPRejectOverload:?229?(7.5%)
FNPOpennetAnnounceReply:?134?(4.4%)
packetTransmit:?123?(4.0%)
FNPAccepted:?47?(1.5%)
FNPOpennetCompletedAck:?42?(1.4%)
FNPSSKDataRequest:?35?(1.1%)
FNPBulkSendAborted:?32?(1.1%)
FNPDataNotFound:?23?(0.8%)
FNPOpennetNoderefRejected:?23?(0.8%)
FNPBulkReceiveAborted:?21?(0.7%)
FNPOpennetAnnounceCompleted:?19?(0.6%)
sendAborted:?11?(0.4%)
FNPInsertTransfersCompleted:?9?(0.3%)
FNPBulkReceivedAll:?6?(0.2%)
FNPDataInsertRejected:?6?(0.2%)
FNPRouteNotFound:?6?(0.2%)
FNPCHKDataRequest:?5?(0.2%)
FNPCHKDataFound:?5?(0.2%)

Re: [freenet-dev] Please test the new load management branch

[Juiceman]

On Sat, Jan 29, 2011 at 7:30 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:

 Please get the snapshot (update.cmd testing / update.sh testing), and test 
 it. I want to know if it causes serious problems, and also any other bugs you 
 run into. I know there will be various errors, but I am still interested in 
 the more severe ones.

 For people building from source:
 The tag is: testing-build-1340-maybe-merge-new-load-management-pre1
 The branch is: merge-new-load-management
 The git rev is 47edfe611a1f088b51fccb36d3e7710e28c3d2b8 (that commit does 
 matter despite it appearing to be a logging fix).

 THANKS!

My seednode is not too healthy:

Node Version Information

* Freenet 0.7.5 Build #1339
testing-build-1340-maybe-merge-new-load-management-pre1
* Freenet-ext Build #26 r23771

Java Info

* Used Java memory: 138 MiB
* Allocated Java memory: 216 MiB
* Maximum Java memory: 870 MiB
* Running threads: 302/750
* Available CPUs: 4
* Java Version: 1.6.0_23
* Java VM Vendor: Sun Microsystems Inc.
* Java VM Name: Java HotSpot(TM) Client VM
* Java VM Version: 19.0-b09
* OS Name: Windows XP
* OS Version: 5.1
* OS Architecture: x86

Node status overview

bwlimitDelayTime: 1464ms
bwlimitDelayTimeBulk: 1464ms
bwlimitDelayTimeRT: 892ms
nodeAveragePingTime: 942ms
darknetSizeEstimateSession: 0 nodes
opennetSizeEstimateSession: 2560 nodes
nodeUptimeSession: 1h39m
nodeUptimeTotal: 7w3d
routingMissDistanceLocal: 0.1437
routingMissDistanceRemote: 0.1598
routingMissDistanceOverall: 0.1587
backedOffPercent: 80.3%
pInstantReject: 25.0%
unclaimedFIFOSize: 3045
RAMBucketPoolSize: 21.8 MiB / 150 MiB
uptimeAverage: 99.8%

Peer statistics

Connected: 10
Backed off: 18
Too old: 77
Disconnected: 7
Never connected: 1
Clock Problem: 1
Disconnecting: 1
Seeding for: 142
Max peers: 36
Max strangers: 36

Bandwidth

Input Rate: 102 KiB/s (of 1.0 MiB/s)
Output Rate: 110 KiB/s (of 105 KiB/s)
Session Total Input: 425 MiB (73.1 KiB/s average)
Session Total Output: 634 MiB (108 KiB/s average)
Payload Output: 6.16 MiB (1.05 KiB/sec)(0%)
Global Total Input: 315 GiB
Global Total Output: 371 GiB
Request output (excluding payload): CHK 381 KiB SSK 1.51 MiB.
Insert output (excluding payload): CHK 122 KiB SSK 29.7 KiB.
Offered keys: sending keys 58.6 KiB, sending offers 27.6 KiB
Swapping Output: 2.85 MiB.
Connection setup: 58.0 MiB output
Ack-only packets: 57.5 MiB
Resent bytes: 418 MiB  (WTF is with this one?)
Updater Output: 366 KiB
Announcement output: 20.3 MiB (transferring node refs payload 15.5 MiB)
Admin bytes: 1.23 MiB initial messages, 2.59 KiB IP change messages,
14.5 KiB disconnection notifications, 0 B routing status
Debugging bytes: 0 B network coloring, 0 B ping, 0 B probe requests, 0
B routed test messages.
Node to node messages: 1.39 MiB
Load allocation notices: 257 KiB
Other output: 65.5 MiB (10%)
Total non-request overhead: 98.3 KiB/sec (90%).

Peer Backoff
Current backoff reasons (bulk)

AcceptedTimeout 4
ForwardRejectedOverload 4
SENDER_DIED 1
SendSyncTimeout 3
TransferFailedRequest7 1

Current backoff reasons (realtime)

AcceptedTimeout 3
FatalTimeout 1
ForwardRejectedOverload 8
SENDER_DIED 2
SendSyncTimeout 3
TransferFailedRequest5 1

Routing Backoff Reason (bulk)CountAvg. TimeTotal Time
SendSyncTimeout512m32s2h9m
Timeout61m53s11m18s
AcceptedTimeout2001m10s3h55m
ForwardRejectedOverload20231.364s1h45m
ForwardRejectedOverload31321.043s4m33s
Timeout3812.321s1m38s
TransferFailedRequest5723.130s3m45s
TimedOutAwaitingDataInsert11.758s1.758s
ForwardRejectedOverload5121.348s16.177s
TransferFailedRequest781.176s9.410s
TransferFailedInsert171.074s18.260s
Routing Backoff Reason (realtime)CountAvg. TimeTotal Time
SendSyncTimeout565m5s4h45m
ForwardRejectedOverload1224m17s8h42m
AcceptedTimeout1821m10s3h32m
FatalTimeoutForked342.111s2m6s
TransferFailedRequest510432.716s56m42s
FatalTimeout3010.567s5m17s
ForwardRejectedOverload2198.198s2m35s
TransferFailedRequest711.283s1.283s
Transfer Backoff Reason (bulk)CountAvg. TimeTotal Time
SENDER_DIED533m3s2h42m
RequestSenderGetOfferedTransferFailed148.327s48.327s
Transfer Backoff Reason (realtime)CountAvg. TimeTotal Time
SENDER_DIED915m54s8h57m
Location swaps

location: 0.22831853895397802
averageSwapTime: 8.000s
sendSwapInterval: 8.000s

unclaimedFIFO Message Counts

FNPPeerLoadStatusByte: 1545 (50.7%)
FNPBulkPacketSend: 379 (12.4%)
FNPOpennetAnnounceNodeNotWanted: 334 (11.0%)
FNPRejectOverload: 229 (7.5%)
FNPOpennetAnnounceReply: 134 (4.4%)
packetTransmit: 123 (4.0%)
FNPAccepted: 47 (1.5%)
FNPOpennetCompletedAck: 42 (1.4%)
FNPSSKDataRequest: 35 (1.1%)
FNPBulkSendAborted: 32 (1.1%)
FNPDataNotFound: 23 (0.8%)
FNPOpennetNoderefRejected: 23 (0.8%)
FNPBulkReceiveAborted: 21 (0.7%)
FNPOpennetAnnounceCompleted: 19 (0.6%)
sendAborted: 11 (0.4%)
FNPInsertTransfersCompleted: 9 (0.3%)
FNPBulkReceivedAll: 6 (0.2%)
FNPDataInsertRejected: 6 (0.2%)
FNPRouteNotFound: 6 (0.2%)
FNPCHKDataRequest: 5 (0.2%)
FNPCHKDataFound: 5 (0.2%)

[freenet-dev] Freenet 0.7.5 build 1314 (and 1313)

[Juiceman]

On Thu, Dec 30, 2010 at 7:48 PM, Matthew Toseland  wrote:

> Freenet 0.7.5 build 1314 is now available, please upgrade! It will be
> mandatory on Tuesday.
>
> This build's main new feature is a new packet format. This should give
> significant improvements in several areas:
> - Fewer small packets.
> - Much more efficient. Expect improved payload percentages, and failing SSK
> requests in particular (which are very important for chat etc) should use
> significantly fewer bytes.
> - Better (faster) retransmission on lossy links.
> - Able to adapt to any reasonable MTU.
> - Lays the foundations for transport plugins (although not with really tiny
> packets).
> - Also necessary for the next stage of new load management, which should go
> in next week if all goes well.
>
> This was zidel's Summer of Code project, although I've done some last
> minute improvements.
>
> There are also some minor changes to filename sanitising on unix OS's and
> some language infrastructure needed by Freetalk.
>
> Please upgrade! And please let me know if you have any problems.
>
> (1313 was never released due to finding some serious bugs at the last
> minute)
>

Something is seriously broken in 1314.  Output seems to be shooting past
limits and payload % has fallen from 40+ to 15 and still going down.
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] Freenet 0.7.5 build 1314 (and 1313)

[Juiceman]

On Thu, Dec 30, 2010 at 7:48 PM, Matthew Toseland t...@amphibian.dyndns.org
 wrote:

 Freenet 0.7.5 build 1314 is now available, please upgrade! It will be
 mandatory on Tuesday.

 This build's main new feature is a new packet format. This should give
 significant improvements in several areas:
 - Fewer small packets.
 - Much more efficient. Expect improved payload percentages, and failing SSK
 requests in particular (which are very important for chat etc) should use
 significantly fewer bytes.
 - Better (faster) retransmission on lossy links.
 - Able to adapt to any reasonable MTU.
 - Lays the foundations for transport plugins (although not with really tiny
 packets).
 - Also necessary for the next stage of new load management, which should go
 in next week if all goes well.

 This was zidel's Summer of Code project, although I've done some last
 minute improvements.

 There are also some minor changes to filename sanitising on unix OS's and
 some language infrastructure needed by Freetalk.

 Please upgrade! And please let me know if you have any problems.

 (1313 was never released due to finding some serious bugs at the last
 minute)


Something is seriously broken in 1314.  Output seems to be shooting past
limits and payload % has fallen from 40+ to 15 and still going down.
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Introduction and minor contribution (?)...

[Juiceman]

Welcome!  Another experienced Java and Mac dev will come in handy =)
On Dec 22, 2010 7:50 AM, "Richy (Wired Up and Fired Up)" <
wiredupandfiredup at gmail.com> wrote:
> Hi,
>
> Great project and I hope I can be of some help. I've been developing java
systems, initially in the banking sector - more recently all over the show
but mostly large scale web projects since the late '90s and I also build
Mac/iPhone apps.
>
> Anyway, the first thing I noticed on installing Freenet 0.7.5 on OS X
(10.6.2) was that I received the warning "Upgrade your Java immediately!
Freenet has disabled important functions including search to limit damage
due to a severe vulnerability in your outdated Java version!" (I saw a few
users have reported this on the support list as well)
>
> Odd, I was pretty sure that I was more or less up to date.. Anyway,
running java -version gave the following :
>
> java version "1.6.0_17"
> Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-10M3025)
> Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)
>
> I isolated and ran the code in Node.java (using the default JVM) that
should trigger this warning but it didn't appear to, so I figured that there
must be something in the wrapper config or similar overriding the choice of
JVM.
>
> In run.sh (line #158 onwards) there is an if statement that selects the
1.5.0 version if it exists. By changing the JAVA_HOME export to
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0 and rerunning my
test of Node.js the warning is triggered.
>
> This made sense for my install as the JVM in that location is version
1.5.0_19 and should trigger the warning.
>
> Replacing this if statement with simply :
> export
JAVA_HOME="/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home"
>
> Or commenting out the entire thing, fixes this as the default java home on
OS X is a mess of symlinks that eventually arrive at
/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home anyway.
>
> By default CurrentJDK should be pointing at the latest version installed
on the machine, whereas 1.5.0 won't necessarily.
>
> I think, out of preference I'd remove this statement entirely. This will
give the user the option to set either their JAVA_HOME themselves and/or
manage their own JVM installs (say, for those using openjdk or other
'non-apple' java versions, which by the looks of it will soon be
everyone...) plus, for now, at least in recent versions of os x the default
behavior is correct.
>
> I'm still new to the code and it's layout and haven't actually managed to
get it to build yet.. (git clone and ant bails out) So I don't have a patch
or anything I can send for this, but just thought I'd send it over in the
hope that it will help :)
>
> In the meantime, I'd just like to say 'hi' and I'll carry on messing about
with the build and trying to familiarise myself with what is already there,
as I said I hope to be able to make a contribution as time goes on and will
probably pop up again sooner or later either here or on irc looking for some
direction into where I can help out.
>
> Cheers,
>
> Richy
> ___
> Devl mailing list
> Devl at freenetproject.org
> http://freenetproject.org/cgi-bin/mailman/listinfo/devl
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-dev] Introduction and minor contribution (?)...

[Juiceman]

Welcome!  Another experienced Java and Mac dev will come in handy =)
On Dec 22, 2010 7:50 AM, Richy (Wired Up and Fired Up) 
wiredupandfire...@gmail.com wrote:
 Hi,

 Great project and I hope I can be of some help. I've been developing java
systems, initially in the banking sector - more recently all over the show
but mostly large scale web projects since the late '90s and I also build
Mac/iPhone apps.

 Anyway, the first thing I noticed on installing Freenet 0.7.5 on OS X
(10.6.2) was that I received the warning Upgrade your Java immediately!
Freenet has disabled important functions including search to limit damage
due to a severe vulnerability in your outdated Java version! (I saw a few
users have reported this on the support list as well)

 Odd, I was pretty sure that I was more or less up to date.. Anyway,
running java -version gave the following :

 java version 1.6.0_17
 Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-10M3025)
 Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)

 I isolated and ran the code in Node.java (using the default JVM) that
should trigger this warning but it didn't appear to, so I figured that there
must be something in the wrapper config or similar overriding the choice of
JVM.

 In run.sh (line #158 onwards) there is an if statement that selects the
1.5.0 version if it exists. By changing the JAVA_HOME export to
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0 and rerunning my
test of Node.js the warning is triggered.

 This made sense for my install as the JVM in that location is version
1.5.0_19 and should trigger the warning.

 Replacing this if statement with simply :
 export
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home

 Or commenting out the entire thing, fixes this as the default java home on
OS X is a mess of symlinks that eventually arrive at
/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home anyway.

 By default CurrentJDK should be pointing at the latest version installed
on the machine, whereas 1.5.0 won't necessarily.

 I think, out of preference I'd remove this statement entirely. This will
give the user the option to set either their JAVA_HOME themselves and/or
manage their own JVM installs (say, for those using openjdk or other
'non-apple' java versions, which by the looks of it will soon be
everyone...) plus, for now, at least in recent versions of os x the default
behavior is correct.

 I'm still new to the code and it's layout and haven't actually managed to
get it to build yet.. (git clone and ant bails out) So I don't have a patch
or anything I can send for this, but just thought I'd send it over in the
hope that it will help :)

 In the meantime, I'd just like to say 'hi' and I'll carry on messing about
with the build and trying to familiarise myself with what is already there,
as I said I hope to be able to make a contribution as time goes on and will
probably pop up again sooner or later either here or on irc looking for some
direction into where I can help out.

 Cheers,

 Richy
 ___
 Devl mailing list
 Devl@freenetproject.org
 http://freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
http://freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Fwd: Re: Deploying the wininstaller

[Juiceman]

On Fri, Dec 17, 2010 at 7:07 PM, Matthew Toseland  wrote:

> On Friday 17 December 2010 17:34:35 Juiceman wrote:
> > A quick workaround would be to put a pause in if the user is using the
> new
> > install method.  They could be asked to shutdown manually and press a
> key.
> > I will do at least this when I get home from work.
>
> Okay, that'd be great.
>
>
Done, the alpha branch is ready for merge and deployment.
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20101217/1d7a5863/attachment.html>