From toad at amphibian.dyndns.org  Sat Jul  7 00:40:36 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Sat, 7 Jul 2007 01:40:36 +0100
Subject: [freenet-dev] Freenet 0.7 build 1041
Message-ID: <200707070140.41838.toad@amphibian.dyndns.org>

Freenet 0.7 build 1041 is now available. Please upgrade, tell us if you have 
any problem upgrading, and tell us if you find any bugs.

Major changes:
- Major internal changes/refactoring getting ready for opennet. We don't yet 
have the core opennet functionality, but we have all the prerequisites. 
Opennet will run on a separate UDP port, with separate crypto etc. You can 
turn it on but it will not automatically exchange refs yet (you can add them 
manually to openpeers-<opennet port> though, they're a lot like darknet 
refs).
- Fix many bugs relating to containers, FCP direct disk access, connectivity 
when IP addresses change, matching connection drops (internal messaging 
stuff, might have some impact), random number generation, node to node text 
messages and direct F2F file transfer, form data parsing, and more.
- Further work on probe requests to prototype the rabbit hole avoidance 
algorithm.

This build will be mandatory on Tuesday, however it should be possible to 
upgrade even then thanks to Update over Mandatory support; if you have any 
problems, tell us.

Thank you for using and testing Freenet.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070707/688ad8a4/attachment.pgp 

From bbackde at googlemail.com  Sun Jul  8 10:53:30 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Sun, 8 Jul 2007 12:53:30 +0200
Subject: [freenet-dev] TestDDA issue
Message-ID: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>

Hello,

I want to implement the TestDDA functionality, but I will wait until
TestDDA supports DDA from read-only devices (upload of files from
DVD). Is this already possible, did I miss something?


From nextgens at freenetproject.org  Sun Jul  8 11:09:11 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Sun, 8 Jul 2007 13:09:11 +0200
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
Message-ID: <20070708110910.GB5462@freenetproject.org>

* bbackde at googlemail.com <bbackde at googlemail.com> [2007-07-08 12:53:30]:

> Hello,
> 
> I want to implement the TestDDA functionality, but I will wait until
> TestDDA supports DDA from read-only devices (upload of files from
> DVD). 

It's possible but not through TestDDA itself; by design.

> Is this already possible, did I miss something?

It's possible; that's what the FileHash parameter of ClientPut is for...
If you provide the node a correct hash of the the file's content, salt
and FCP session number, it will allow uploads from disk even from RO
medias.

Of course computing that hash twice (on both node and client side) is
expensive and should be avoided if possible... Hence we have TestDDA...
TestDDA allows you though FCP to "whitelist" parts of the filesystem.

That said, "direct uploads" are even more expensive.

I hope it makes sense to you, do not hesitate to ask if it doesn't...
I'm not sure how clear my explanation is :)

Regards,
	NextGen$
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070708/4130300d/attachment.pgp 

From bbackde at googlemail.com  Sun Jul  8 12:14:50 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Sun, 8 Jul 2007 14:14:50 +0200
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <20070708110910.GB5462@freenetproject.org>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
	<20070708110910.GB5462@freenetproject.org>
Message-ID: <d6149a790707080514u1ad5c30dy735d8216857dd3a9@mail.gmail.com>

Wouldn't it be possible to enhance TestDDA for read-only files? The
node could choose a part of a file (or more parts) with some KB of
size and check if the client sends the same hash for the parts as the
node computed.

Client->Node: TestDDA file=/abc mode=ForPUT
Node->Client: Provide Hash for offset 4096,len=4096
Client->Node: Hash=abcdef
(Node compares hash with own computed hash and maybe accepts read access)

Its maybe not well thought, but something like this :)
Does not require to compute the complete hash of big files.

On 7/8/07, Florent Daigni?re <nextgens at freenetproject.org> wrote:
> * bbackde at googlemail.com <bbackde at googlemail.com> [2007-07-08 12:53:30]:
>
> > Hello,
> >
> > I want to implement the TestDDA functionality, but I will wait until
> > TestDDA supports DDA from read-only devices (upload of files from
> > DVD).
>
> It's possible but not through TestDDA itself; by design.
>
> > Is this already possible, did I miss something?
>
> It's possible; that's what the FileHash parameter of ClientPut is for...
> If you provide the node a correct hash of the the file's content, salt
> and FCP session number, it will allow uploads from disk even from RO
> medias.
>
> Of course computing that hash twice (on both node and client side) is
> expensive and should be avoided if possible... Hence we have TestDDA...
> TestDDA allows you though FCP to "whitelist" parts of the filesystem.
>
> That said, "direct uploads" are even more expensive.
>
> I hope it makes sense to you, do not hesitate to ask if it doesn't...
> I'm not sure how clear my explanation is :)
>
> Regards,
>         NextGen$
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGkMXWU/Z/dHFfxtcRAuxbAKC6mG2cdbDFJBvDw9EIK/7P1TV2PACdFCTi
> yRuDm4fxBnKne6WOlFPiegM=
> =bLIW
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________


From nextgens at freenetproject.org  Sun Jul  8 12:32:02 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Sun, 8 Jul 2007 14:32:02 +0200
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <d6149a790707080514u1ad5c30dy735d8216857dd3a9@mail.gmail.com>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
	<20070708110910.GB5462@freenetproject.org>
	<d6149a790707080514u1ad5c30dy735d8216857dd3a9@mail.gmail.com>
Message-ID: <20070708123158.GA9327@freenetproject.org>

* bbackde at googlemail.com <bbackde at googlemail.com> [2007-07-08 14:14:50]:

> Wouldn't it be possible to enhance TestDDA for read-only files?

Enhancements are always possible ;)

> The node could choose a part of a file (or more parts) with some KB of
> size and check if the client sends the same hash for the parts as the
> node computed.

No, that's silly.

> 
> Client->Node: TestDDA file=/abc mode=ForPUT
> Node->Client: Provide Hash for offset 4096,len=4096
> Client->Node: Hash=abcdef
> (Node compares hash with own computed hash and maybe accepts read access)
> 
> Its maybe not well thought, but something like this :)

... would be broken by design.

> Does not require to compute the complete hash of big files.
> 

The whole thing has been  designed to avoid information leak/disclosure;
What  you're  proposing  is  broken  by design  and  defeats  the  whole
purpose...

Let's  take  an  example:  On   most  unix  systems  the  authentication
credentials are  stored in  /etc/passwd and /etc/shadow  ... on  most of
them only a few number of  users are "manually" created ... and manually
created ones have  got home directories... Given that, most  of the file
can  be  "guessed"  by an  attacker  :  It's  not  because I'm  able  to
reconstitute part  of that file  that I can  do it compleetly.  We don't
want the node to  publish that file on freenet on the  basis that an FCP
client has been able to reconstitute part of a secret file and has asked
the  node for  new "challenges"  up  to the  point it's  able to  answer
correctly.

Anyway, sending the file using the "direct" method to the node is *far*
more expensive than computing twice the hash of its content, belive me
:)

NextGen$

> On 7/8/07, Florent Daigni?re <nextgens at freenetproject.org> wrote:
> >* bbackde at googlemail.com <bbackde at googlemail.com> [2007-07-08 12:53:30]:
> >
> >> Hello,
> >>
> >> I want to implement the TestDDA functionality, but I will wait until
> >> TestDDA supports DDA from read-only devices (upload of files from
> >> DVD).
> >
> >It's possible but not through TestDDA itself; by design.
> >
> >> Is this already possible, did I miss something?
> >
> >It's possible; that's what the FileHash parameter of ClientPut is for...
> >If you provide the node a correct hash of the the file's content, salt
> >and FCP session number, it will allow uploads from disk even from RO
> >medias.
> >
> >Of course computing that hash twice (on both node and client side) is
> >expensive and should be avoided if possible... Hence we have TestDDA...
> >TestDDA allows you though FCP to "whitelist" parts of the filesystem.
> >
> >That said, "direct uploads" are even more expensive.
> >
> >I hope it makes sense to you, do not hesitate to ask if it doesn't...
> >I'm not sure how clear my explanation is :)
> >
> >Regards,
> >        NextGen$
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.4.6 (GNU/Linux)
> >
> >iD8DBQFGkMXWU/Z/dHFfxtcRAuxbAKC6mG2cdbDFJBvDw9EIK/7P1TV2PACdFCTi
> >yRuDm4fxBnKne6WOlFPiegM=
> >=bLIW
> >-----END PGP SIGNATURE-----
> >
> >_______________________________________________
> >Devl mailing list
> >Devl at freenetproject.org
> >http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
> >
> 
> 
> -- 
> __________________________________________________
> GnuPG key:   (0x48DBFA8A)
> Keyserver:   pgpkeys.pca.dfn.de
> Fingerprint:
> 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
> __________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070708/c51f3f26/attachment.pgp 

From jargonautti at hotmail.com  Sun Jul  8 17:04:15 2007
From: jargonautti at hotmail.com (Jusa Saari)
Date: Sun, 08 Jul 2007 20:04:15 +0300
Subject: [freenet-dev] Freenet 0.7 build 1041
References: <200707070140.41838.toad@amphibian.dyndns.org>
Message-ID: <pan.2007.07.08.17.04.12.819386@hotmail.com>

On Sat, 07 Jul 2007 01:40:36 +0100, Matthew Toseland wrote:

> Freenet 0.7 build 1041 is now available. Please upgrade, tell us if you
> have any problem upgrading, and tell us if you find any bugs.
> 
> Major changes:
> - Major internal changes/refactoring getting ready for opennet. We don't
> yet have the core opennet functionality, but we have all the
> prerequisites. Opennet will run on a separate UDP port, with separate
> crypto etc. You can turn it on but it will not automatically exchange refs

What does "separate crypto" mean ? Does it use different algorithm or
something ? Why ?

I do assume that all the connections use a different crypto key, right ?

Anyway, does using a separate port give any security advantages ? I would
think it would allow an attacker who can packet-sniff your node to gain
more information by reliably differentiating your darknet and opennet
connections.

> yet (you can add them manually to openpeers-<opennet port> though, they're
> a lot like darknet refs).
> - Fix many bugs relating to containers, FCP direct disk access,
> connectivity when IP addresses change, matching connection drops (internal
> messaging stuff, might have some impact), random number generation, node
> to node text messages and direct F2F file transfer, form data parsing, and
> more. - Further work on probe requests to prototype the rabbit hole
> avoidance algorithm.
> 
> This build will be mandatory on Tuesday, however it should be possible to
> upgrade even then thanks to Update over Mandatory support; if you have any
> problems, tell us.
> 
> Thank you for using and testing Freenet._______________________________________________ Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl




From nextgens at freenetproject.org  Sun Jul  8 21:09:32 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Sun, 8 Jul 2007 23:09:32 +0200
Subject: [freenet-dev] Freenet 0.7 build 1041
In-Reply-To: <pan.2007.07.08.17.04.12.819386@hotmail.com>
References: <200707070140.41838.toad@amphibian.dyndns.org>
	<pan.2007.07.08.17.04.12.819386@hotmail.com>
Message-ID: <20070708210932.GA5553@freenetproject.org>

* Jusa Saari <jargonautti at hotmail.com> [2007-07-08 20:04:15]:

> On Sat, 07 Jul 2007 01:40:36 +0100, Matthew Toseland wrote:
> 
> > Freenet 0.7 build 1041 is now available. Please upgrade, tell us if you
> > have any problem upgrading, and tell us if you find any bugs.
> > 
> > Major changes:
> > - Major internal changes/refactoring getting ready for opennet. We don't
> > yet have the core opennet functionality, but we have all the
> > prerequisites. Opennet will run on a separate UDP port, with separate
> > crypto etc. You can turn it on but it will not automatically exchange refs
> 
> What does "separate crypto" mean ? Does it use different algorithm or
> something ? Why ?

What it means ... No

> I do assume that all the connections use a different crypto key, right ?
> 

It's not clear  on how different they  will be yet... In  any case there
will be  a different  node reference,  meaning that  the keypair  can be
different.

> Anyway, does using a separate port give any security advantages ? I would
> think it would allow an attacker who can packet-sniff your node to gain
> more information by reliably differentiating your darknet and opennet
> connections.

Opennet is harvestable  by design... and will be harvested;  If we don't
want bad  guys to  be able  to cheaply block  most of  the nodes  of the
network, we have to use different port numbers.

NextGen$
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070708/cb67690a/attachment.pgp 

From toad at amphibian.dyndns.org  Mon Jul  9 18:46:45 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Mon, 9 Jul 2007 19:46:45 +0100
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
Message-ID: <200707091946.50153.toad@amphibian.dyndns.org>

On Sunday 08 July 2007 11:53, bbackde at googlemail.com wrote:
> Hello,
>
> I want to implement the TestDDA functionality, but I will wait until
> TestDDA supports DDA from read-only devices (upload of files from
> DVD). Is this already possible, did I miss something?

Is it useful? Most read-only devices are removable disks, do we really want to 
support direct disk access from removable disks? Wouldn't it be better to 
copy the data to a temporary location, so that it will still be inserted if 
the DVD is ejected?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070709/c8445c11/attachment.pgp 

From bbackde at googlemail.com  Tue Jul 10 06:31:10 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Tue, 10 Jul 2007 08:31:10 +0200
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <200707091946.50153.toad@amphibian.dyndns.org>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
	<200707091946.50153.toad@amphibian.dyndns.org>
Message-ID: <d6149a790707092331t12aecdaax105995ec23eecaf2@mail.gmail.com>

Depends on the case. I know of users who want to upload from DVDs
because they don't have enough free space on the hdd. They start the
upload, wait until it is finished and remove the DVD afterwards.

On 7/9/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> On Sunday 08 July 2007 11:53, bbackde at googlemail.com wrote:
> > Hello,
> >
> > I want to implement the TestDDA functionality, but I will wait until
> > TestDDA supports DDA from read-only devices (upload of files from
> > DVD). Is this already possible, did I miss something?
>
> Is it useful? Most read-only devices are removable disks, do we really want to
> support direct disk access from removable disks? Wouldn't it be better to
> copy the data to a temporary location, so that it will still be inserted if
> the DVD is ejected?
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________


From toad at amphibian.dyndns.org  Tue Jul 10 12:18:46 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Tue, 10 Jul 2007 13:18:46 +0100
Subject: [freenet-dev] TestDDA issue
In-Reply-To: <d6149a790707092331t12aecdaax105995ec23eecaf2@mail.gmail.com>
References: <d6149a790707080353x6b722625oa1b860d6be36b0f0@mail.gmail.com>
	<200707091946.50153.toad@amphibian.dyndns.org>
	<d6149a790707092331t12aecdaax105995ec23eecaf2@mail.gmail.com>
Message-ID: <200707101318.47272.toad@amphibian.dyndns.org>

On Tuesday 10 July 2007 07:31, bbackde at googlemail.com wrote:
> Depends on the case. I know of users who want to upload from DVDs
> because they don't have enough free space on the hdd. They start the
> upload, wait until it is finished and remove the DVD afterwards.

Hmmm ok.
>
> On 7/9/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> > On Sunday 08 July 2007 11:53, bbackde at googlemail.com wrote:
> > > Hello,
> > >
> > > I want to implement the TestDDA functionality, but I will wait until
> > > TestDDA supports DDA from read-only devices (upload of files from
> > > DVD). Is this already possible, did I miss something?
> >
> > Is it useful? Most read-only devices are removable disks, do we really
> > want to support direct disk access from removable disks? Wouldn't it be
> > better to copy the data to a temporary location, so that it will still be
> > inserted if the DVD is ejected?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070710/88d63abe/attachment.pgp 

From toad at amphibian.dyndns.org  Tue Jul 10 16:41:35 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Tue, 10 Jul 2007 17:41:35 +0100
Subject: [freenet-dev] Freenet 0.7 build 1042
Message-ID: <200707101741.43354.toad@amphibian.dyndns.org>

Freenet 0.7 build 1042 is now available. Please upgrade. This build fixes 
various mostly relatively minor bugs, and features an improved french 
translation. For the full changelog see the cvs list.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070710/2cf8c70a/attachment.pgp 

From sback at sback.it  Thu Jul 12 12:06:37 2007
From: sback at sback.it (Sback)
Date: Thu, 12 Jul 2007 14:06:37 +0200
Subject: [freenet-dev] BitArray possible (little) bug?
Message-ID: <4696194D.8070205@sback.it>

When I try to set a bit in a place bigger than the BitArray size,
sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
that the problem is present when the BitArray size is not a multiple of
8. IMHO the exception should be raised in each wrong case.

Here you are the test code (you can find it in the trunk too):

    /**
     * Tests setBit(int,boolean) method
     * trying to set a bit out of bounds
     */
    public void testSetBit_OutOfBounds() {
        BitArray methodBitArray = new BitArray(10);
        try {
            methodBitArray.setBit(10,true);
            fail("Expected Exception Error Not Thrown!");}
        catch (ArrayIndexOutOfBoundsException anException) {
            assertNotNull(anException); }
    }

Thank you,

Sback



From bbackde at googlemail.com  Thu Jul 12 12:19:46 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Thu, 12 Jul 2007 14:19:46 +0200
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <4696194D.8070205@sback.it>
References: <4696194D.8070205@sback.it>
Message-ID: <d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>

Slightly off topic question: why don't you use the existing
java.util.BitSet? This seems to work for me in Frost.

On 7/12/07, Sback <sback at sback.it> wrote:
> When I try to set a bit in a place bigger than the BitArray size,
> sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
> that the problem is present when the BitArray size is not a multiple of
> 8. IMHO the exception should be raised in each wrong case.
>
> Here you are the test code (you can find it in the trunk too):
>
>     /**
>      * Tests setBit(int,boolean) method
>      * trying to set a bit out of bounds
>      */
>     public void testSetBit_OutOfBounds() {
>         BitArray methodBitArray = new BitArray(10);
>         try {
>             methodBitArray.setBit(10,true);
>             fail("Expected Exception Error Not Thrown!");}
>         catch (ArrayIndexOutOfBoundsException anException) {
>             assertNotNull(anException); }
>     }
>
> Thank you,
>
> Sback
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________


From toad at amphibian.dyndns.org  Thu Jul 12 13:55:38 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 12 Jul 2007 14:55:38 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
References: <4696194D.8070205@sback.it>
	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
Message-ID: <200707121455.38578.toad@amphibian.dyndns.org>

On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> Slightly off topic question: why don't you use the existing
> java.util.BitSet? This seems to work for me in Frost.

IIRC we needed some extra methods. Somebody should check into this.
>
> On 7/12/07, Sback <sback at sback.it> wrote:
> > When I try to set a bit in a place bigger than the BitArray size,
> > sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
> > that the problem is present when the BitArray size is not a multiple of
> > 8. IMHO the exception should be raised in each wrong case.
> >
> > Here you are the test code (you can find it in the trunk too):
> >
> >     /**
> >      * Tests setBit(int,boolean) method
> >      * trying to set a bit out of bounds
> >      */
> >     public void testSetBit_OutOfBounds() {
> >         BitArray methodBitArray = new BitArray(10);
> >         try {
> >             methodBitArray.setBit(10,true);
> >             fail("Expected Exception Error Not Thrown!");}
> >         catch (ArrayIndexOutOfBoundsException anException) {
> >             assertNotNull(anException); }
> >     }
> >
> > Thank you,
> >
> > Sback
> >
> > _______________________________________________
> > Devl mailing list
> > Devl at freenetproject.org
> > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070712/c1088ca9/attachment.pgp 

From jflesch at freenetproject.org  Wed Jul 11 21:56:18 2007
From: jflesch at freenetproject.org (jflesch at freenetproject.org)
Date: Wed, 11 Jul 2007 21:56:18 +0000 (UTC)
Subject: [freenet-dev] r14039 - tags/Thaw
Message-ID: <20070711215618.6F7C947A239@freenetproject.org>

Author: jflesch
Date: 2007-07-11 21:56:18 +0000 (Wed, 11 Jul 2007)
New Revision: 14039

Added:
   tags/Thaw/0.7.1/
Log:
Thaw 0.7.1

- Obsolete keys in an indexes are now displayed in red
- Add some new themes (liquid and InfoNode)
- Tabs have a new behavior
- Downloads / insertions are now displayed differently : Background color are no more used to show the states
- Add a systray icon (see the plugin list ; require Java 1.6 !)
- A button "details" in the index browser can provide you some stats
- In the configuration, in advanced mode, you can now choose the directory used for temporary files
- 'Remove finished transfers' doens't remove the failed ones anymore
- In advanced mode, you can now choose the language of the interface (English/French)
- the GTK theme is marked as buggy. Please don't use it.
- Insertion date is now included in the indexes
- TransferLogs has been partially rewrited
- The PeerMonitor panel is now retractable
- mDns can now be desactivated : It's a plugin
- Some keyboard shortcuts were added:
  - The key 'Delete' should work almost everywhere
  - 'Alt-B' add the selected index to the blacklist
  - 'Alt-R' refresh the selected index



Copied: tags/Thaw/0.7.1 (from rev 14038, trunk/apps/Thaw)



From toad at amphibian.dyndns.org  Thu Jul 12 15:47:49 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 12 Jul 2007 16:47:49 +0100
Subject: [freenet-dev] Freenet 0.7 build 1043
Message-ID: <200707121647.56140.toad@amphibian.dyndns.org>

Freenet 0.7 build 1043 is now available. The main change is to fix a bug 
introduced a few builds ago (during the opennet-related major refactoring), 
which prevented ARKs from working, which caused nodes not to be able to 
connect after an IP address change. Please upgrade.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070712/1aba05ba/attachment.pgp 

From nogaso at gmail.com  Sat Jul 14 23:46:54 2007
From: nogaso at gmail.com (Nogaso Smith)
Date: Sun, 15 Jul 2007 01:46:54 +0200
Subject: [freenet-dev] Updated norwegian translation
Message-ID: <dfdf77280707141646j38e81578m5c36dffc343aeae0@mail.gmail.com>

Latest changes as of 2007-07-14

Nogaso
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freenet.l10n.no.override.properties
Type: application/octet-stream
Size: 9706 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070715/6e0e3d39/attachment.obj 

From nextgens at freenetproject.org  Sun Jul 15 00:23:02 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Sun, 15 Jul 2007 02:23:02 +0200
Subject: [freenet-dev] Updated norwegian translation
In-Reply-To: <dfdf77280707141646j38e81578m5c36dffc343aeae0@mail.gmail.com>
References: <dfdf77280707141646j38e81578m5c36dffc343aeae0@mail.gmail.com>
Message-ID: <20070715002300.GA6040@freenetproject.org>

* Nogaso Smith <nogaso at gmail.com> [2007-07-15 01:46:54]:

> Latest changes as of 2007-07-14
> 
> Nogaso

Merged in r14132, thanks :)

NextGen$
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070715/9a9a3b56/attachment.pgp 

From nextgens at freenetproject.org  Sun Jul 15 14:27:42 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Sun, 15 Jul 2007 16:27:42 +0200
Subject: [freenet-dev] Freenet 0.7 build 1044
Message-ID: <20070715142732.GA6062@freenetproject.org>

Freenet 0.7 build 1044 is now available; updating will be mandatory on
the 17th of July. 

Here is a sum-up of the changelog:

Core:
	- Path folding (one additional step towards having a working
	  opennet)
	- RRNFs weren't accounted as RNFs whereas they should have been
	- Introduce a new connection failure code (CONN_ERROR)
	- Fix a bug which might have caused heavy backoff
	- Add FCP messages to handle opennet references
	- Some work on the plugin code
	- Some locking changes

L10n:
	- updated norwegian translation
	- various fixes/improvements to the english version

Credits:
	- toad_, Zothar and Nogasso

Please upgrade. 

NextGen$
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070715/60b34f4e/attachment.pgp 

From toad at amphibian.dyndns.org  Mon Jul 16 15:34:16 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Mon, 16 Jul 2007 16:34:16 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
References: <4696194D.8070205@sback.it>
	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
Message-ID: <200707161634.16615.toad@amphibian.dyndns.org>

On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> Slightly off topic question: why don't you use the existing
> java.util.BitSet? This seems to work for me in Frost.

IIRC we needed some extra methods. Somebody should check into this.
>
> On 7/12/07, Sback <sback at sback.it> wrote:
> > When I try to set a bit in a place bigger than the BitArray size,
> > sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
> > that the problem is present when the BitArray size is not a multiple of
> > 8. IMHO the exception should be raised in each wrong case.
> >
> > Here you are the test code (you can find it in the trunk too):
> >
> >     /**
> >      * Tests setBit(int,boolean) method
> >      * trying to set a bit out of bounds
> >      */
> >     public void testSetBit_OutOfBounds() {
> >         BitArray methodBitArray = new BitArray(10);
> >         try {
> >             methodBitArray.setBit(10,true);
> >             fail("Expected Exception Error Not Thrown!");}
> >         catch (ArrayIndexOutOfBoundsException anException) {
> >             assertNotNull(anException); }
> >     }
> >
> > Thank you,
> >
> > Sback
> >
> > _______________________________________________
> > Devl mailing list
> > Devl at freenetproject.org
> > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070716/e84a432d/attachment.pgp 

From toad at amphibian.dyndns.org  Mon Jul 16 15:35:52 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Mon, 16 Jul 2007 16:35:52 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
References: <4696194D.8070205@sback.it>
	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
Message-ID: <200707161635.53172.toad@amphibian.dyndns.org>

On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> Slightly off topic question: why don't you use the existing
> java.util.BitSet? This seems to work for me in Frost.

IIRC we needed some extra methods. Somebody should check into this.
>
> On 7/12/07, Sback <sback at sback.it> wrote:
> > When I try to set a bit in a place bigger than the BitArray size,
> > sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
> > that the problem is present when the BitArray size is not a multiple of
> > 8. IMHO the exception should be raised in each wrong case.
> >
> > Here you are the test code (you can find it in the trunk too):
> >
> >     /**
> >      * Tests setBit(int,boolean) method
> >      * trying to set a bit out of bounds
> >      */
> >     public void testSetBit_OutOfBounds() {
> >         BitArray methodBitArray = new BitArray(10);
> >         try {
> >             methodBitArray.setBit(10,true);
> >             fail("Expected Exception Error Not Thrown!");}
> >         catch (ArrayIndexOutOfBoundsException anException) {
> >             assertNotNull(anException); }
> >     }
> >
> > Thank you,
> >
> > Sback
> >
> > _______________________________________________
> > Devl mailing list
> > Devl at freenetproject.org
> > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070716/2de589b1/attachment.pgp 

From toad at amphibian.dyndns.org  Mon Jul 16 15:34:56 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Mon, 16 Jul 2007 16:34:56 +0100
Subject: [freenet-dev] Freenet 0.7 build 1043
Message-ID: <200707161634.57454.toad@amphibian.dyndns.org>

Freenet 0.7 build 1043 is now available. The main change is to fix a bug 
introduced a few builds ago (during the opennet-related major refactoring), 
which prevented ARKs from working, which caused nodes not to be able to 
connect after an IP address change. Please upgrade.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070716/441133f9/attachment.pgp 

From mailing at edv-fervers.de  Mon Jul 16 19:04:17 2007
From: mailing at edv-fervers.de (Volker Fervers)
Date: Mon, 16 Jul 2007 21:04:17 +0200
Subject: [freenet-dev] Freenet 0.7 build 1043
In-Reply-To: <200707161634.57454.toad@amphibian.dyndns.org>
References: <200707161634.57454.toad@amphibian.dyndns.org>
Message-ID: <200707162104.22635.mailing@edv-fervers.de>

News from the past? ;-)

Am Montag, 16. Juli 2007 17:34 schrieb Matthew Toseland:
> Freenet 0.7 build 1043 is now available. The main change is to fix
> a bug introduced a few builds ago (during the opennet-related major
> refactoring), which prevented ARKs from working, which caused nodes
> not to be able to connect after an IP address change. Please
> upgrade.


From toad at amphibian.dyndns.org  Tue Jul 17 14:25:56 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Tue, 17 Jul 2007 15:25:56 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <200707161635.53172.toad@amphibian.dyndns.org>
References: <4696194D.8070205@sback.it>
	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
	<200707161635.53172.toad@amphibian.dyndns.org>
Message-ID: <200707171525.56745.toad@amphibian.dyndns.org>

Sorry, I had some email problems recently.

On Monday 16 July 2007 16:35, Matthew Toseland wrote:
> On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> > Slightly off topic question: why don't you use the existing
> > java.util.BitSet? This seems to work for me in Frost.
>
> IIRC we needed some extra methods. Somebody should check into this.
>
> > On 7/12/07, Sback <sback at sback.it> wrote:
> > > When I try to set a bit in a place bigger than the BitArray size,
> > > sometimes it does not raise an ArrayIndexOutOfBoundsException. It seems
> > > that the problem is present when the BitArray size is not a multiple of
> > > 8. IMHO the exception should be raised in each wrong case.
> > >
> > > Here you are the test code (you can find it in the trunk too):
> > >
> > >     /**
> > >      * Tests setBit(int,boolean) method
> > >      * trying to set a bit out of bounds
> > >      */
> > >     public void testSetBit_OutOfBounds() {
> > >         BitArray methodBitArray = new BitArray(10);
> > >         try {
> > >             methodBitArray.setBit(10,true);
> > >             fail("Expected Exception Error Not Thrown!");}
> > >         catch (ArrayIndexOutOfBoundsException anException) {
> > >             assertNotNull(anException); }
> > >     }
> > >
> > > Thank you,
> > >
> > > Sback
> > >
> > > _______________________________________________
> > > Devl mailing list
> > > Devl at freenetproject.org
> > > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070717/f7df7931/attachment.pgp 

From toad at amphibian.dyndns.org  Tue Jul 17 15:27:02 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Tue, 17 Jul 2007 16:27:02 +0100
Subject: [freenet-dev] Freenet 0.7 build 1045
Message-ID: <200707171627.09022.toad@amphibian.dyndns.org>

Freenet 0.7 build 1045 is available. It will be mandatory midnight thursday 
(0:00 19 july). Please upgrade ASAP. Tell us if the auto-update doesn't work 
for you. This build includes a major opennet fix, better FCP support for 
opennet (so the refbots will use opennet exclusively soon), translation 
fixes, and improvements to the SoC projects on searching, crypto, and the C++ 
library.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070717/69672fb8/attachment.pgp 

From freenet-devl at osndok.com  Tue Jul 17 19:40:15 2007
From: freenet-devl at osndok.com (Robert Hailey)
Date: Tue, 17 Jul 2007 14:40:15 -0500
Subject: [freenet-dev] Minor Update Deadlock
Message-ID: <7EAD42C7-C4BD-46C7-9697-D87D8C08D3EB@osndok.com>


It would appear that if two nodes are simultaneously updated across a  
'good' version, the 'link' between the two will forever be dead; each  
waiting for the other to get up to speed on the version, and each not  
wanting to connect to the other because it is too old, therefore  
never contacting the presumed-old node to realize that it is, in  
fact, compatible.

--
Robert Hailey



From toad at amphibian.dyndns.org  Wed Jul 18 11:47:03 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 18 Jul 2007 12:47:03 +0100
Subject: [freenet-dev] Minor Update Deadlock
In-Reply-To: <7EAD42C7-C4BD-46C7-9697-D87D8C08D3EB@osndok.com>
References: <7EAD42C7-C4BD-46C7-9697-D87D8C08D3EB@osndok.com>
Message-ID: <200707181247.04275.toad@amphibian.dyndns.org>

On Tuesday 17 July 2007 20:40, Robert Hailey wrote:
> It would appear that if two nodes are simultaneously updated across a
> 'good' version, the 'link' between the two will forever be dead; each
> waiting for the other to get up to speed on the version, and each not
> wanting to connect to the other because it is too old, therefore
> never contacting the presumed-old node to realize that it is, in
> fact, compatible.

Not sure I understand.

We do send handshake attempts even if a node is TOO OLD, we just send them 
less frequently (maybe this is a bad thing). And in fact if we establish a 
connection we can UOM from them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070718/c099ea50/attachment.pgp 

From freenet-devl at osndok.com  Wed Jul 18 18:46:08 2007
From: freenet-devl at osndok.com (Robert Hailey)
Date: Wed, 18 Jul 2007 13:46:08 -0500
Subject: [freenet-dev] Minor Update Deadlock
In-Reply-To: <200707181247.04275.toad@amphibian.dyndns.org>
References: <7EAD42C7-C4BD-46C7-9697-D87D8C08D3EB@osndok.com>
	<200707181247.04275.toad@amphibian.dyndns.org>
Message-ID: <8B21E84B-8116-4E3F-BD28-4D015EA8C3F1@osndok.com>


On Jul 18, 2007, at 6:47 AM, Matthew Toseland wrote:

> On Tuesday 17 July 2007 20:40, Robert Hailey wrote:
>> It would appear that if two nodes are simultaneously updated across a
>> 'good' version, the 'link' between the two will forever be dead; each
>> waiting for the other to get up to speed on the version, and each not
>> wanting to connect to the other because it is too old, therefore
>> never contacting the presumed-old node to realize that it is, in
>> fact, compatible.
>
> Not sure I understand.
>
> We do send handshake attempts even if a node is TOO OLD, we just  
> send them
> less frequently (maybe this is a bad thing). And in fact if we  
> establish a
> connection we can UOM from them.

I'm not sure that the specific problem here is what I said, only that  
is/was my 'best guess'.

I have a few computers running freenet disconnected from the network  
at-large, but connected to each other. All was well and good with  
this test setup, but upon updating the node versions (a big jump,  
from about 1007->1045), they now will not connect to each other. I  
also tried deleting the peers and re-adding the references, but  
without success (they simply went from perpetually 'disconnected' to  
'never connected').

At present the peer status shows "NEVER CONNECTED*" (* = fetching  
ark?), a valid connection address (even port number matching),  
backoff "0/1" and zero entries in the more-detail/message-type table.  
Conventional network communications between the machines are fine.

--
Robert Hailey



From toad at amphibian.dyndns.org  Thu Jul 19 11:16:48 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 19 Jul 2007 12:16:48 +0100
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <20070719001617.139604798FC@freenetproject.org>
References: <20070719001617.139604798FC@freenetproject.org>
Message-ID: <200707191216.48282.toad@amphibian.dyndns.org>

I'm not convinced it should just be a default. Can't we explicitly ask the 
user a yes/no, maybe during the post-setup wizard?

On Thursday 19 July 2007 01:16, you wrote:
> Author: nextgens
> Date: 2007-07-19 00:16:16 +0000 (Thu, 19 Jul 2007)
> New Revision: 14189
>
> Added:
>    trunk/apps/new_installer/res/unix/bin/install_opennet.sh
>    trunk/apps/new_installer/res/windows/bin/install_opennet.cmd
> Modified:
>    trunk/apps/new_installer/ProcessPanel.Spec.xml
>    trunk/apps/new_installer/install.xml
>    trunk/apps/new_installer/langpacks/fra.xml
> Log:
> new_installer: set opennet up by default; maybe the welcome page should say
> something about it as well
>
> Modified: trunk/apps/new_installer/ProcessPanel.Spec.xml
> ===================================================================
> --- trunk/apps/new_installer/ProcessPanel.Spec.xml	2007-07-19 00:13:26 UTC
> (rev 14188) +++ trunk/apps/new_installer/ProcessPanel.Spec.xml	2007-07-19
> 00:16:16 UTC (rev 14189) @@ -26,6 +26,19 @@
>  		<executefile name="$INSTALL_PATH\bin\install_updater.cmd"/>
>  	</job>
>
> +	<job name="Setting Opennet up">
> +		<os family="unix"/>
> +		<executefile name="$INSTALL_PATH/bin/install_opennet.sh"/>
> +	</job>
> +	<job name="Setting the Opennet up">
> +		<os family="mac"/>
> +		<executefile name="$INSTALL_PATH/bin/install_opennet.sh"/>
> +	</job>
> +	<job name="Setting the Opennet up">
> +		<os family="windows"/>
> +		<executefile name="$INSTALL_PATH\bin\install_opennet.cmd"/>
> +	</job>
> +
>  	<job name="Setting MDNS up">
>  		<os family="unix"/>
>  		<executefile name="$INSTALL_PATH/bin/install_mdns.sh"/>
>
> Modified: trunk/apps/new_installer/install.xml
> ===================================================================
> --- trunk/apps/new_installer/install.xml	2007-07-19 00:13:26 UTC (rev
> 14188) +++ trunk/apps/new_installer/install.xml	2007-07-19 00:16:16 UTC
> (rev 14189) @@ -151,6 +151,7 @@
>  			<parsable targetfile="$INSTALL_PATH\bin\install_frost.cmd"/>
>  			<parsable targetfile="$INSTALL_PATH\bin\install_jsite.cmd"/>
>  			<parsable targetfile="$INSTALL_PATH\bin\install_plugins.cmd"/>
> +			<parsable targetfile="$INSTALL_PATH\bin\install_opennet.cmd"/>
>  			<parsable targetfile="$INSTALL_PATH\bin\install_thaw.cmd"/>
>  			<parsable targetfile="$INSTALL_PATH\bin\install_updater.cmd"/>
>  			<parsable targetfile="$INSTALL_PATH\bin\install_wrapper.cmd"/>
> @@ -182,6 +183,7 @@
>  			<parsable targetfile="$INSTALL_PATH/bin/install_jSite.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_librarian.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_mdns.sh"/>
> +			<parsable targetfile="$INSTALL_PATH/bin/install_opennet.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_stun.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_upnp.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_thaw.sh"/>
> @@ -218,6 +220,7 @@
>  			<parsable targetfile="$INSTALL_PATH/bin/install_jSite.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_librarian.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_mdns.sh"/>
> +			<parsable targetfile="$INSTALL_PATH/bin/install_opennet.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_stun.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_upnp.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/install_thaw.sh"/>
> @@ -228,6 +231,11 @@
>  			<parsable targetfile="$INSTALL_PATH/bin/install_startup_hook-mac.sh"/>
>  			<parsable targetfile="$INSTALL_PATH/bin/cleanup.sh"/>
>  		</pack>
> +
> +		<pack name="Opennet" id="opennet" required="no">
> +			<description>Allow the node to establish new connections to strangers
> automaticaly (useful only if you don't know anyone using freenet). Enabling
> this feature presents a SECURITY RISK.</description> +			<singlefile
> src="res/license/LICENSE.Freenet" target="$INSTALL_PATH/opennet"/>
> +		</pack>
>
>  		<pack name="UninstallStuff" id="uninstall" required="no" os="windows">
>  			<description>Create uninstallation hooks in the registry</description>
>
> Modified: trunk/apps/new_installer/langpacks/fra.xml
> ===================================================================
> --- trunk/apps/new_installer/langpacks/fra.xml	2007-07-19 00:13:26 UTC (rev
> 14188) +++ trunk/apps/new_installer/langpacks/fra.xml	2007-07-19 00:16:16
> UTC (rev 14189) @@ -78,6 +78,7 @@
>      <str id="unix.description" txt="Un pack contenant des scripts."/>
>      <str id="uninstall.description" txt="Un pack permettant de configurer
> l'outil de d?sinstallation."/> <str id="autoupdater.description" txt="Un
> pack permettant au noeud de se tenir ? jour automatiquement via freenet.
> Il est conseill? de l'installer."/> +    <str id="opennet.description"
> txt="Un pack configurant le noeud pour qu'il trouve automatiquement des
> amis ? qui se connecter (utile si vous ne connaissez personne qui utilise
> freenet) Attention: activer ce pack pr?sente des risques de SECURITE."/>
> <str id="stun.description" txt="Un pack permettant d'installer le plugin
> STUN pour freenet. STUN est le protocole permettant ? freenet de
> d?couvrir dynamiquement quel est votre type de connexion internet. Ce
> protocole utilise un serveur tiers pour officier, ce qui peut etre
> consid?r? comme un risque de s?curit?. Nous recommandons de l'installer
> car il permet d'am?liorer la connectivit? des noeuds utilisant des
> adresses ip dynamiques (la plupart des noeuds)."/> <str
> id="upnp.description" txt="Un pack permettant d'activer le support UP&P
> pour freenet. Universal Plug aNd Play est le protocole permettant ?
> freenet de d?couvrir dynamiquement quel est votre adresse IP et d'?tablir
> un port-forwarding. Ce protocole ne doit pas ?tre utilis? si vous de
> faites pas confiance au r?seau auquel vous ?tes connect?. Nous
> recommandons tout de m?me de l'installer car il permet d'am?liorer la
> connectivit? des noeuds."/> <str id="mdns.description" txt="Un pack
> permettant d'installer le plugin MDNSDiscovery pour freenet. MDNS est le
> protocole connu sous les noms ZeroConf/Bonjour/Rendez-Vous permettant ?
> freenet de d?couvrir dynamiquement les autres noeuds pr?sents sur le
> r?seau local. Ce protocole permet aussi aux clients compatibles de
> s'auto-configurer."/>
>
> Added: trunk/apps/new_installer/res/unix/bin/install_opennet.sh
> ===================================================================
> --- trunk/apps/new_installer/res/unix/bin/install_opennet.sh	              
>          (rev 0) +++
> trunk/apps/new_installer/res/unix/bin/install_opennet.sh	2007-07-19
> 00:16:16 UTC (rev 14189) @@ -0,0 +1,15 @@
> +#!/bin/bash
> +
> +INSTALL_PATH="${INSTALL_PATH:-$PWD}"
> +
> +cd "$INSTALL_PATH"
> +
> +if test -e opennet
> +then
> +	# Register opennet
> +	echo "Enabling Opennet"
> +	echo "node.opennet.enabled=true" >> freenet.ini
> +
> +	# Cleanup
> +	rm -f opennet
> +fi
>
>
> Property changes on:
> trunk/apps/new_installer/res/unix/bin/install_opennet.sh
> ___________________________________________________________________ Name:
> svn:executable
>    + *
>
> Added: trunk/apps/new_installer/res/windows/bin/install_opennet.cmd
> ===================================================================
> --- trunk/apps/new_installer/res/windows/bin/install_opennet.cmd	          
>              (rev 0) +++
> trunk/apps/new_installer/res/windows/bin/install_opennet.cmd	2007-07-19
> 00:16:16 UTC (rev 14189) @@ -0,0 +1,10 @@
> + at set PATH=%SYSTEMROOT%\System32\;%PATH%
> + at set INSTALL_PATH=$INSTALL_PATH
> + at set JAVA_HOME=$JAVA_HOME
> + at cd /D %INSTALL_PATH%
> +
> + at if not exist opennet goto noopennet
> + at echo Enabling Opennet
> + at echo node.opennet.enabled=true >> freenet.ini
> + at del /F opennet > NUL
> +:noopennet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070719/d719e236/attachment.pgp 

From toad at amphibian.dyndns.org  Thu Jul 19 11:18:52 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 19 Jul 2007 12:18:52 +0100
Subject: [freenet-dev] Minor Update Deadlock
In-Reply-To: <8B21E84B-8116-4E3F-BD28-4D015EA8C3F1@osndok.com>
References: <7EAD42C7-C4BD-46C7-9697-D87D8C08D3EB@osndok.com>
	<200707181247.04275.toad@amphibian.dyndns.org>
	<8B21E84B-8116-4E3F-BD28-4D015EA8C3F1@osndok.com>
Message-ID: <200707191218.52112.toad@amphibian.dyndns.org>

Most likely a LAN problem. You need to go to advanced mode, enable 
includeLocalAddresses, and for each peer on each node, enable 
allowLocalAddresses in the dropdown at the bottom of the darknet peers list.

On Wednesday 18 July 2007 19:46, Robert Hailey wrote:
> On Jul 18, 2007, at 6:47 AM, Matthew Toseland wrote:
> > On Tuesday 17 July 2007 20:40, Robert Hailey wrote:
> >> It would appear that if two nodes are simultaneously updated across a
> >> 'good' version, the 'link' between the two will forever be dead; each
> >> waiting for the other to get up to speed on the version, and each not
> >> wanting to connect to the other because it is too old, therefore
> >> never contacting the presumed-old node to realize that it is, in
> >> fact, compatible.
> >
> > Not sure I understand.
> >
> > We do send handshake attempts even if a node is TOO OLD, we just
> > send them
> > less frequently (maybe this is a bad thing). And in fact if we
> > establish a
> > connection we can UOM from them.
>
> I'm not sure that the specific problem here is what I said, only that
> is/was my 'best guess'.
>
> I have a few computers running freenet disconnected from the network
> at-large, but connected to each other. All was well and good with
> this test setup, but upon updating the node versions (a big jump,
> from about 1007->1045), they now will not connect to each other. I
> also tried deleting the peers and re-adding the references, but
> without success (they simply went from perpetually 'disconnected' to
> 'never connected').
>
> At present the peer status shows "NEVER CONNECTED*" (* = fetching
> ark?), a valid connection address (even port number matching),
> backoff "0/1" and zero entries in the more-detail/message-type table.
> Conventional network communications between the machines are fine.
>
> --
> Robert Hailey
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070719/9f28c890/attachment.pgp 

From toad at amphibian.dyndns.org  Thu Jul 19 11:33:45 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 19 Jul 2007 12:33:45 +0100
Subject: [freenet-dev] Freenet 0.7 build 1047
Message-ID: <200707191233.50594.toad@amphibian.dyndns.org>

Freenet 0.7 build 1047 is available. Please upgrade ASAP. This build includes 
various fixes to opennet and to probe requests, as well as further work on 
unit testing by sback. Thanks to saces, nextgens, sback and me. You might 
want to update your UPnP plugin too. 1046 was skipped because I accidentally 
made it immediately mandatory rather than mandatory in 2 days, which is the 
current policy (1047 will be mandatory at 0:00 21 July).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070719/efbfa638/attachment.pgp 

From nextgens at freenetproject.org  Thu Jul 19 17:16:03 2007
From: nextgens at freenetproject.org (NextGen$)
Date: Thu, 19 Jul 2007 17:16:03 +0000
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <200707191216.48282.toad@amphibian.dyndns.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<200707191216.48282.toad@amphibian.dyndns.org>
Message-ID: <20070719171602.GF25418@freenetproject.org>

* Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 12:16:48]:

> I'm not convinced it should just be a default.

Huh ? isn't opennet useless if it's not the default ? I'm really surprised
that someone (you in particular) objects here :)

> Can't we explicitly ask the user a yes/no, maybe during the post-setup wizard?

Yeah, it could be done in the wizard... shall I revert the changes ? (it has
already been deployed and the current installer is setting up opennet by
default)

> 
> On Thursday 19 July 2007 01:16, you wrote:
> > Author: nextgens
> > Date: 2007-07-19 00:16:16 +0000 (Thu, 19 Jul 2007)
> > New Revision: 14189
> >
> > Added:
> >    trunk/apps/new_installer/res/unix/bin/install_opennet.sh
> >    trunk/apps/new_installer/res/windows/bin/install_opennet.cmd
> > Modified:
> >    trunk/apps/new_installer/ProcessPanel.Spec.xml
> >    trunk/apps/new_installer/install.xml
> >    trunk/apps/new_installer/langpacks/fra.xml
> > Log:
> > new_installer: set opennet up by default; maybe the welcome page should say
> > something about it as well
> >


From toad at amphibian.dyndns.org  Thu Jul 19 20:58:28 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 19 Jul 2007 21:58:28 +0100
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <20070719171602.GF25418@freenetproject.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<200707191216.48282.toad@amphibian.dyndns.org>
	<20070719171602.GF25418@freenetproject.org>
Message-ID: <200707192158.28766.toad@amphibian.dyndns.org>

On Thursday 19 July 2007 18:16, NextGen$ wrote:
> * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 12:16:48]:
> > I'm not convinced it should just be a default.
>
> Huh ? isn't opennet useless if it's not the default ? I'm really surprised
> that someone (you in particular) objects here :)
>
> > Can't we explicitly ask the user a yes/no, maybe during the post-setup
> > wizard?
>
> Yeah, it could be done in the wizard... shall I revert the changes ? (it
> has already been deployed and the current installer is setting up opennet
> by default)

Yes. Opennet is such a hideous security risk that we should definitely ask the 
user, with no obvious default.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070719/d9b19ee3/attachment.pgp 

From nextgens at freenetproject.org  Thu Jul 19 21:18:06 2007
From: nextgens at freenetproject.org (NextGen$)
Date: Thu, 19 Jul 2007 21:18:06 +0000
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <200707192158.28766.toad@amphibian.dyndns.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<200707191216.48282.toad@amphibian.dyndns.org>
	<20070719171602.GF25418@freenetproject.org>
	<200707192158.28766.toad@amphibian.dyndns.org>
Message-ID: <20070719211805.GI25418@freenetproject.org>

* Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 21:58:28]:

> On Thursday 19 July 2007 18:16, NextGen$ wrote:
> > * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 12:16:48]:
> > > I'm not convinced it should just be a default.
> >
> > Huh ? isn't opennet useless if it's not the default ? I'm really surprised
> > that someone (you in particular) objects here :)
> >
> > > Can't we explicitly ask the user a yes/no, maybe during the post-setup
> > > wizard?
> >
> > Yeah, it could be done in the wizard... shall I revert the changes ? (it
> > has already been deployed and the current installer is setting up opennet
> > by default)
> 
> Yes. Opennet is such a hideous security risk that we should definitely ask the 
> user, with no obvious default.

I won't need to be asked to do it twice :) it has been reverted in r14195 and
I'm currently rebuilding the installer.

NextGen$


From ian at locut.us  Thu Jul 19 23:14:21 2007
From: ian at locut.us (Ian Clarke)
Date: Thu, 19 Jul 2007 18:14:21 -0500
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <20070719211805.GI25418@freenetproject.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<200707191216.48282.toad@amphibian.dyndns.org>
	<20070719171602.GF25418@freenetproject.org>
	<200707192158.28766.toad@amphibian.dyndns.org>
	<20070719211805.GI25418@freenetproject.org>
Message-ID: <823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>

I have no objection to asking the user, provided that it is clearly apparent
to users that unless you know people already running Freenet, you need to go
with opennet or Freenet will be useless to you.
I'm all for letting users make an informed choice, but I'm certainly not in
favor of corralling them into choosing darknet only to get completely stuck
because they don't know anyone that currently uses Freenet (this will be the
case for the vast majority of users if we ever experience the growth we hope
for).

Also, are we using the terms "opennet" and "darknet" in the user interface?
 I hope not, because these terms will mean absolutely nothing to users not
already familiar with Freenet.  We must never forget to try to put ourselves
in the shoes of a fresh user, and we must avoid assuming that users will
understand, or want to understand, internal freenet terminology, no matter
how familiar those terms might be to us.

I think the decision to use "friends" and "strangers" in the UI was a good
example of opting for terminology that new users will understand
intuitively.

Ian.

On 7/19/07, NextGen$ <nextgens at freenetproject.org> wrote:
>
> * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 21:58:28]:
>
> > On Thursday 19 July 2007 18:16, NextGen$ wrote:
> > > * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-19 12:16:48]:
> > > > I'm not convinced it should just be a default.
> > >
> > > Huh ? isn't opennet useless if it's not the default ? I'm really
> surprised
> > > that someone (you in particular) objects here :)
> > >
> > > > Can't we explicitly ask the user a yes/no, maybe during the
> post-setup
> > > > wizard?
> > >
> > > Yeah, it could be done in the wizard... shall I revert the changes ?
> (it
> > > has already been deployed and the current installer is setting up
> opennet
> > > by default)
> >
> > Yes. Opennet is such a hideous security risk that we should definitely
> ask the
> > user, with no obvious default.
>
> I won't need to be asked to do it twice :) it has been reverted in r14195
> and
> I'm currently rebuilding the installer.
>
> NextGen$
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>


-- 
Founder and CEO, Thoof Inc
Email: ian at thoof.com
Office: +1 512 524 8934 x 100
Cell: +1 512 422 3588
AIM: ian.clarke at mac.com
Skype: sanity
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://emu.freenetproject.org/pipermail/devl/attachments/20070719/b6796a60/attachment.htm 

From toad at amphibian.dyndns.org  Fri Jul 20 15:34:14 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Fri, 20 Jul 2007 16:34:14 +0100
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>
References: <20070719001617.139604798FC@freenetproject.org>
	<20070719211805.GI25418@freenetproject.org>
	<823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>
Message-ID: <200707201634.21777.toad@amphibian.dyndns.org>

On Friday 20 July 2007 00:14, Ian Clarke wrote:
> I have no objection to asking the user, provided that it is clearly
> apparent to users that unless you know people already running Freenet, you
> need to go with opennet or Freenet will be useless to you.

That's the idea. That's the whole point of opennet.

> I'm all for letting users make an informed choice, but I'm certainly not in
> favor of corralling them into choosing darknet only to get completely stuck
> because they don't know anyone that currently uses Freenet (this will be
> the case for the vast majority of users if we ever experience the growth we
> hope for).

Agreed.
>
> Also, are we using the terms "opennet" and "darknet" in the user interface?
>  I hope not, because these terms will mean absolutely nothing to users not
> already familiar with Freenet.  We must never forget to try to put
> ourselves in the shoes of a fresh user, and we must avoid assuming that
> users will understand, or want to understand, internal freenet terminology,
> no matter how familiar those terms might be to us.
>
> I think the decision to use "friends" and "strangers" in the UI was a good
> example of opting for terminology that new users will understand
> intuitively.

Okay, so what should this question say then exactly? Perhaps:

"Connect to strangers?

Your node can either automatically find untrusted nodes to connect to 
("Strangers"), or you can manually add connections to trusted nodes 
("Friends") run by people you already know. Connecting to total strangers is 
far less secure, but it means your node will start working immediately, 
rather than you having to find some friends to connect to. Even if you do 
enable connecting to untrusted nodes, you should try to get some friend 
connections when your friends start using Freenet.

Button: Connect to strangers

Button: Only connect to friends"

I'm a bit worried about the severely informal language we have to use, but 
it's better than freenet jargon, and the whole friends list thing is pretty 
universal post-AIM anyway.
>
> Ian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070720/1daaecdc/attachment.pgp 

From guido-frn at unknownsite.de  Fri Jul 20 17:13:41 2007
From: guido-frn at unknownsite.de (Guido Winkelmann)
Date: Fri, 20 Jul 2007 19:13:41 +0200
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <200707201634.21777.toad@amphibian.dyndns.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>
	<200707201634.21777.toad@amphibian.dyndns.org>
Message-ID: <200707201913.41509.guido-frn@unknownsite.de>

Hi,

Am Freitag, 20. Juli 2007 17:34:14 schrieb Matthew Toseland:
[...]
> Okay, so what should this question say then exactly? Perhaps:
>
> "Connect to strangers?
>
> Your node can either automatically find untrusted nodes to connect to
> ("Strangers"), or you can manually add connections to trusted nodes
> ("Friends") run by people you already know. Connecting to total strangers
> is far less secure, but it means your node will start working immediately,
> rather than you having to find some friends to connect to. Even if you do
> enable connecting to untrusted nodes, you should try to get some friend
> connections when your friends start using Freenet.
>
> Button: Connect to strangers
>
> Button: Only connect to friends"
>
> I'm a bit worried about the severely informal language we have to use, but
> it's better than freenet jargon, and the whole friends list thing is pretty
> universal post-AIM anyway.

I think it should also be pointed out that the first option means that 
*anybody* can find out that the user is using freenet, while with the second 
option only his or her selected friends will be able to.

	Guido


From ian at locut.us  Fri Jul 20 17:34:42 2007
From: ian at locut.us (Ian Clarke)
Date: Fri, 20 Jul 2007 12:34:42 -0500
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <200707201634.21777.toad@amphibian.dyndns.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<20070719211805.GI25418@freenetproject.org>
	<823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>
	<200707201634.21777.toad@amphibian.dyndns.org>
Message-ID: <823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>

On 7/20/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
>
> Okay, so what should this question say then exactly? Perhaps:
>
> "Connect to strangers?
>
> Your node can either automatically find untrusted nodes to connect to
> ("Strangers"), or you can manually add connections to trusted nodes
> ("Friends") run by people you already know. Connecting to total strangers
> is
> far less secure, but it means your node will start working immediately,
> rather than you having to find some friends to connect to. Even if you do
> enable connecting to untrusted nodes, you should try to get some friend
> connections when your friends start using Freenet.


I think per Guido's suggestion, rather than vaguely saying that connecting
to strangers is "far less secure", we should explain in what way it is
insecure.

Perhaps "If you allow connection to strangers, then you are revealing the
fact that you are running Freenet, although what you are using Freenet for
will still be very difficult for them to determine".


> Button: Connect to strangers


How about a single check box - "[ ] Allow connections to strangers"

Button: Only connect to friends"
>
> I'm a bit worried about the severely informal language we have to use, but
> it's better than freenet jargon, and the whole friends list thing is
> pretty
> universal post-AIM anyway.


We are writing software, not a legal brief.  Who cares if the language is
informal provided that its comprehensible.

Ian.

-- 
Founder and CEO, Thoof Inc
Email: ian at thoof.com
Office: +1 512 524 8934 x 100
Cell: +1 512 422 3588
AIM: ian.clarke at mac.com
Skype: sanity
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://emu.freenetproject.org/pipermail/devl/attachments/20070720/8bb0150a/attachment.htm 

From nextgens at freenetproject.org  Fri Jul 20 18:25:11 2007
From: nextgens at freenetproject.org (Florent =?iso-8859-1?Q?Daigni=E8re?=)
Date: Fri, 20 Jul 2007 20:25:11 +0200
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>
References: <20070719001617.139604798FC@freenetproject.org>
	<20070719211805.GI25418@freenetproject.org>
	<823242bd0707191614j7431af3eyf30d5903abb8f560@mail.gmail.com>
	<200707201634.21777.toad@amphibian.dyndns.org>
	<823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>
Message-ID: <20070720182511.GH5467@freenetproject.org>

* Ian Clarke <ian at locut.us> [2007-07-20 12:34:42]:

> On 7/20/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> >
> >Okay, so what should this question say then exactly? Perhaps:
> >
> >"Connect to strangers?
> >
> >Your node can either automatically find untrusted nodes to connect to
> >("Strangers"), or you can manually add connections to trusted nodes
> >("Friends") run by people you already know. Connecting to total strangers
> >is
> >far less secure, but it means your node will start working immediately,
> >rather than you having to find some friends to connect to. Even if you do
> >enable connecting to untrusted nodes, you should try to get some friend
> >connections when your friends start using Freenet.
> 
> 
> I think per Guido's suggestion, rather than vaguely saying that connecting
> to strangers is "far less secure", we should explain in what way it is
> insecure.
> 
> Perhaps "If you allow connection to strangers, then you are revealing the
> fact that you are running Freenet, although what you are using Freenet for
> will still be very difficult for them to determine".
...
Unless the bad guy uses it as an attack vector and becomes "most" of your
connections to freenet.

If we precise things, we might be to be pedantic.

NextGen$
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070720/01ea85d7/attachment.pgp 

From luke771 at gmail.com  Wed Jul 18 18:26:11 2007
From: luke771 at gmail.com (luke771)
Date: Wed, 18 Jul 2007 20:26:11 +0200
Subject: [freenet-dev] ita. l10n v.18 (#1045 r14163)
Message-ID: <469E5B43.8020001@gmail.com>

Attached.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.it.override.properties_v.18_ph00
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070718/033e991b/attachment.txt 

From toad at amphibian.dyndns.org  Sat Jul 21 15:46:59 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Sat, 21 Jul 2007 16:46:59 +0100
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>
References: <20070719001617.139604798FC@freenetproject.org>
	<200707201634.21777.toad@amphibian.dyndns.org>
	<823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>
Message-ID: <200707211647.05174.toad@amphibian.dyndns.org>

Ok. Implemented something like this in the latest code:

Freenet first time wizard! - Friends and strangers

Connect to strangers?

Your node can either automatically find untrusted nodes to connect to 
("Strangers"), or you can manually add connections to trusted nodes 
("Friends") run by people you already know. Connecting to total strangers 
("promiscuous mode" or "opennet") is far less secure (in particular, your 
node can be found relatively easily, and anyone can connect to it), but it 
means your node will start working immediately, rather than you having to 
find some friends to connect to. Even if you do enable promiscuous mode, you 
should try to get some friend connections when your friends start using 
Freenet.

Automatically connect to untrusted strangers' nodes?
[ ] Yes
[ ] No

On Friday 20 July 2007 18:34, Ian Clarke wrote:
> On 7/20/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> > Okay, so what should this question say then exactly? Perhaps:
> >
> > "Connect to strangers?
> >
> > Your node can either automatically find untrusted nodes to connect to
> > ("Strangers"), or you can manually add connections to trusted nodes
> > ("Friends") run by people you already know. Connecting to total strangers
> > is
> > far less secure, but it means your node will start working immediately,
> > rather than you having to find some friends to connect to. Even if you do
> > enable connecting to untrusted nodes, you should try to get some friend
> > connections when your friends start using Freenet.
>
> I think per Guido's suggestion, rather than vaguely saying that connecting
> to strangers is "far less secure", we should explain in what way it is
> insecure.
>
> Perhaps "If you allow connection to strangers, then you are revealing the
> fact that you are running Freenet, although what you are using Freenet for
> will still be very difficult for them to determine".
>
> > Button: Connect to strangers
>
> How about a single check box - "[ ] Allow connections to strangers"
>
> Button: Only connect to friends"
>
> > I'm a bit worried about the severely informal language we have to use,
> > but it's better than freenet jargon, and the whole friends list thing is
> > pretty
> > universal post-AIM anyway.
>
> We are writing software, not a legal brief.  Who cares if the language is
> informal provided that its comprehensible.
>
> Ian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070721/c02f0336/attachment.pgp 

From guido-frn at unknownsite.de  Sat Jul 21 16:32:15 2007
From: guido-frn at unknownsite.de (Guido Winkelmann)
Date: Sat, 21 Jul 2007 18:32:15 +0200
Subject: [freenet-dev] [freenet-cvs] r14189 - in
	trunk/apps/new_installer: . langpacks res/unix/bin res/windows/bin
In-Reply-To: <200707211647.05174.toad@amphibian.dyndns.org>
References: <20070719001617.139604798FC@freenetproject.org>
	<823242bd0707201034o30366c82q7690a5553c828c2f@mail.gmail.com>
	<200707211647.05174.toad@amphibian.dyndns.org>
Message-ID: <200707211832.15501.guido-frn@unknownsite.de>

Am Samstag, 21. Juli 2007 17:46 schrieb Matthew Toseland:
> Ok. Implemented something like this in the latest code:
>
> Freenet first time wizard! - Friends and strangers
>
> Connect to strangers?
>
> Your node can either automatically find untrusted nodes to connect to
> ("Strangers"), or you can manually add connections to trusted nodes
> ("Friends") run by people you already know. Connecting to total strangers
> ("promiscuous mode" or "opennet") is far less secure (in particular, your
> node can be found relatively easily, and anyone can connect to it), but it
> means your node will start working immediately, rather than you having to
> find some friends to connect to. Even if you do enable promiscuous mode,
> you should try to get some friend connections when your friends start using
> Freenet.
>
> Automatically connect to untrusted strangers' nodes?
> [ ] Yes
> [ ] No

Counter suggestion:

Connect to strangers?

If you let freenet connect to strangers, freenet will be less secure for you 
and everybody can find out that you are using freenet.

If you don't, you will have to manually contact at least three other people 
who are using freenet and connect to them.

Connect to strangers?
[ ] Yes
[ ] No

Keep it simple and to the point. Don't use complicated sentence structures, 
don't use very long sentences, don't throw in stuff in brackets, don't use 
terminology that is not universally understandable. (What is a "node" to 
someone new to networking and P2P?)

	Guido


From juiceman69 at gmail.com  Sat Jul 21 18:33:36 2007
From: juiceman69 at gmail.com (Juiceman)
Date: Sat, 21 Jul 2007 14:33:36 -0400
Subject: [freenet-dev] 1010
Message-ID: <8b525dee0707211133l222dfcabn8e0251e250a28386@mail.gmail.com>

Isn't it about time to start setting the 1010 support options to false
and phasing them out over the next several releases?

-- 
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


From m.rogers at cs.ucl.ac.uk  Sat Jul 21 19:51:21 2007
From: m.rogers at cs.ucl.ac.uk (Michael Rogers)
Date: Sat, 21 Jul 2007 20:51:21 +0100
Subject: [freenet-dev] Should swap identifiers be random?
Message-ID: <46A263B9.9060608@cs.ucl.ac.uk>

Anonymous message reposted from Frost... the attack based on
reconstructing the unique ID from an exposed ref sounds plausible.
Should the identifiers used in swap requests be random instead?

--- Forwarded message ---

It all starts with harvesting refs. On IRC thats doable by just
listening to completly public exchanges or (to get a few more) by
activly querying them from other bots. On Frost it can be done by doing
a few bogus exchanges or exchange requests in this board. Do that
continually and you get a nice set of refs. You won't get all but thats
not needed, its enough if you get a decent number.
Next thing is spying on swap requests. Each swap exchange contains the
locations of the exchanging nodes and their peers. It also contains a
unique identifier for each of them. This identifier was added by the
devs for debugging reasons: They wanted to be able to map the network
topology, reconstructing it from the information gathered by the swap
requests but there is nothing stopping other people from doing it too.
After the reconstruction you have the reconstructed network and know the
identifier, location and number of peers for each node. The only thing
missing is the IP address.
"Luckily" that identifier gets constructed out of parts of the nodes
refs and the last time I read anything about it, it was planned to
create it only out of not changing parts. If that was implemented that
way and reading IRC logs suggests that, you can check for a given
identifier if it was constructed out of a certain ref. That way you can
map your harvested refs to your nodes in your reconstructed network
topology and thus get IPs for them.
Afterwards you have a really nice playground to do statistical attacks,
with much needed info for each node.
This whole attack is only suited to attack random people because if you
want to target a certain person but don't have his ref: bad luck or at
least it will get a whole lot harder. Still, its enough to possibly
cause trouble to random targets and there are enough people who don't
care who they hit, as long as they can cause trouble. See the spambot
operator for (a rather harmless) example.


From alexlehm at myrealbox.com  Sun Jul 22 16:42:43 2007
From: alexlehm at myrealbox.com (Alexander Lehmann)
Date: Sun, 22 Jul 2007 18:42:43 +0200
Subject: [freenet-dev] SubscribeUSK/SubscribedUSKUpdate wiki document
Message-ID: <46A38903.5070605@myrealbox.com>

Hello,

I have added the wiki documents for SubscribeUSK and 
SubscribedUSKUpdate, mostly by reading the source code comments and by 
trying them in a sample program, could someone please check if this corrent?


bye, Alexander




From sback at sback.it  Mon Jul 23 08:05:08 2007
From: sback at sback.it (Alberto Bacchelli)
Date: Mon, 23 Jul 2007 10:05:08 +0200
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <200707121455.38578.toad@amphibian.dyndns.org>
References: <4696194D.8070205@sback.it>	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
	<200707121455.38578.toad@amphibian.dyndns.org>
Message-ID: <46A46134.8020607@sback.it>

I surveyed BitArray class to check whether it is possible to delete it
in favor of BitSet.

IMHO we could dismiss BitArray, but we should extend the existing
java.util.BitSet class to provide some methods missing:
setAllOnes() to set all bits true,
firstOne() to find the first true bit,
writeToDataOutputStream()
hashCode()
unsignedByte() [STATIC method]
I don't think it would be difficult to create them.

On the other hand, maybe it could be knotty to substitute
serializedLength() method which has only one reference.

Matthew Toseland wrote:
> On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
>   
>> Slightly off topic question: why don't you use the existing
>> java.util.BitSet? This seems to work for me in Frost.
>>     
>
> IIRC we needed some extra methods. Somebody should check into this.
>   
>> On 7/12/07, Sback <sback at sback.it> wrote:
>>     
[CUT]


From bbackde at googlemail.com  Mon Jul 23 08:45:04 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Mon, 23 Jul 2007 10:45:04 +0200
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <46A46134.8020607@sback.it>
References: <4696194D.8070205@sback.it>
	<d6149a790707120519s3ddd45dchd6326fd00bc64820@mail.gmail.com>
	<200707121455.38578.toad@amphibian.dyndns.org>
	<46A46134.8020607@sback.it>
Message-ID: <d6149a790707230145p48ed50a8i42b0e006eb601488@mail.gmail.com>

> setAllOnes() to set all bits true,
maybe use BitSet.set(int fromIndex, int toIndex) with fromIndex=0 and
toIndex=BitSet.size()

> firstOne() to find the first true bit,
maybe use BitSet.nextSetBit(0)

> writeToDataOutputStream()
BitSet is already Serializable. But maybe you need to reimplement it
to keep compatability to the current serialization code.

> hashCode()
isn't this implemented already in BitSet.hashCode() ?


On 7/23/07, Alberto Bacchelli <sback at sback.it> wrote:
> I surveyed BitArray class to check whether it is possible to delete it
> in favor of BitSet.
>
> IMHO we could dismiss BitArray, but we should extend the existing
> java.util.BitSet class to provide some methods missing:
> setAllOnes() to set all bits true,
> firstOne() to find the first true bit,
> writeToDataOutputStream()
> hashCode()
> unsignedByte() [STATIC method]
> I don't think it would be difficult to create them.
>
> On the other hand, maybe it could be knotty to substitute
> serializedLength() method which has only one reference.
>
> Matthew Toseland wrote:
> > On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> >
> >> Slightly off topic question: why don't you use the existing
> >> java.util.BitSet? This seems to work for me in Frost.
> >>
> >
> > IIRC we needed some extra methods. Somebody should check into this.
> >
> >> On 7/12/07, Sback <sback at sback.it> wrote:
> >>
> [CUT]
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________


From toad at amphibian.dyndns.org  Tue Jul 24 15:50:42 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Tue, 24 Jul 2007 16:50:42 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <d6149a790707230145p48ed50a8i42b0e006eb601488@mail.gmail.com>
References: <4696194D.8070205@sback.it> <46A46134.8020607@sback.it>
	<d6149a790707230145p48ed50a8i42b0e006eb601488@mail.gmail.com>
Message-ID: <200707241650.47591.toad@amphibian.dyndns.org>

On Monday 23 July 2007 09:45, bbackde at googlemail.com wrote:
> > setAllOnes() to set all bits true,
>
> maybe use BitSet.set(int fromIndex, int toIndex) with fromIndex=0 and
> toIndex=BitSet.size()
>
> > firstOne() to find the first true bit,
>
> maybe use BitSet.nextSetBit(0)
>
> > writeToDataOutputStream()
>
> BitSet is already Serializable. But maybe you need to reimplement it
> to keep compatability to the current serialization code.

We don't want to use java's Serialization for this; we need an efficient 
binary format for Message's, not a universal object stream.
>
> > hashCode()
>
> isn't this implemented already in BitSet.hashCode() ?
>
> On 7/23/07, Alberto Bacchelli <sback at sback.it> wrote:
> > I surveyed BitArray class to check whether it is possible to delete it
> > in favor of BitSet.
> >
> > IMHO we could dismiss BitArray, but we should extend the existing
> > java.util.BitSet class to provide some methods missing:
> > setAllOnes() to set all bits true,
> > firstOne() to find the first true bit,
> > writeToDataOutputStream()
> > hashCode()
> > unsignedByte() [STATIC method]
> > I don't think it would be difficult to create them.
> >
> > On the other hand, maybe it could be knotty to substitute
> > serializedLength() method which has only one reference.
> >
> > Matthew Toseland wrote:
> > > On Thursday 12 July 2007 13:19, bbackde at googlemail.com wrote:
> > >> Slightly off topic question: why don't you use the existing
> > >> java.util.BitSet? This seems to work for me in Frost.
> > >
> > > IIRC we needed some extra methods. Somebody should check into this.
> > >
> > >> On 7/12/07, Sback <sback at sback.it> wrote:
> >
> > [CUT]
> > _______________________________________________
> > Devl mailing list
> > Devl at freenetproject.org
> > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070724/39a57e9c/attachment.pgp 

From sback at sback.it  Wed Jul 25 15:15:24 2007
From: sback at sback.it (Alberto Bacchelli)
Date: Wed, 25 Jul 2007 17:15:24 +0200
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <200707241650.47591.toad@amphibian.dyndns.org>
References: <4696194D.8070205@sback.it>
	<46A46134.8020607@sback.it>	<d6149a790707230145p48ed50a8i42b0e006eb601488@mail.gmail.com>
	<200707241650.47591.toad@amphibian.dyndns.org>
Message-ID: <46A7690C.8040502@sback.it>

Well, now we have a comparison between the two classes :)
What should we do? Move to an extended BitSet or remain using BitArray?
In the latter case: what about the bug?

Thank you!

Sback

Matthew Toseland wrote:
> On Monday 23 July 2007 09:45, bbackde at googlemail.com wrote:
>   
>>> setAllOnes() to set all bits true,
>>>       
>> maybe use BitSet.set(int fromIndex, int toIndex) with fromIndex=0 and
>> toIndex=BitSet.size()
>>     
[CUT]


From toad at amphibian.dyndns.org  Wed Jul 25 15:21:42 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 16:21:42 +0100
Subject: [freenet-dev] BitArray possible (little) bug?
In-Reply-To: <46A7690C.8040502@sback.it>
References: <4696194D.8070205@sback.it>
	<200707241650.47591.toad@amphibian.dyndns.org>
	<46A7690C.8040502@sback.it>
Message-ID: <200707251621.46377.toad@amphibian.dyndns.org>

On Wednesday 25 July 2007 16:15, Alberto Bacchelli wrote:
> Well, now we have a comparison between the two classes :)
> What should we do? Move to an extended BitSet or remain using BitArray?
> In the latter case: what about the bug?

Move to an extended BitSet, assuming that doing so doesn't require any 
post-1.4 functionality. However this can safely be filed as a bug and 
forgotten about for a while as far as I am concerned.
>
> Thank you!
>
> Sback
>
> Matthew Toseland wrote:
> > On Monday 23 July 2007 09:45, bbackde at googlemail.com wrote:
> >>> setAllOnes() to set all bits true,
> >>
> >> maybe use BitSet.set(int fromIndex, int toIndex) with fromIndex=0 and
> >> toIndex=BitSet.size()
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/0a704b09/attachment.pgp 

From toad at amphibian.dyndns.org  Wed Jul 25 15:23:54 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 16:23:54 +0100
Subject: [freenet-dev] SubscribeUSK/SubscribedUSKUpdate wiki document
In-Reply-To: <46A38903.5070605@myrealbox.com>
References: <46A38903.5070605@myrealbox.com>
Message-ID: <200707251623.55098.toad@amphibian.dyndns.org>

On Sunday 22 July 2007 17:42, Alexander Lehmann wrote:
> Hello,
>
> I have added the wiki documents for SubscribeUSK and
> SubscribedUSKUpdate, mostly by reading the source code comments and by
> trying them in a sample program, could someone please check if this
> corrent?

It's URI= not USK= (caught by mkolar). Looks fine to me otherwise, I slightly 
improved the wording.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/bf7f8a3e/attachment.pgp 

From toad at amphibian.dyndns.org  Wed Jul 25 15:40:53 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 16:40:53 +0100
Subject: [freenet-dev] Should swap identifiers be random?
In-Reply-To: <46A263B9.9060608@cs.ucl.ac.uk>
References: <46A263B9.9060608@cs.ucl.ac.uk>
Message-ID: <200707251640.59607.toad@amphibian.dyndns.org>

I'm not sure what we can do about this. If we are to include UIDs for our 
peers then we must know them. Is it necessary that we only know them if we've 
actually connected to them rather than deriving them from the (fixed) 
identity in the noderef? The attack is viable - if you have all the noderefs, 
then watching the swaps you can reconstruct which node is connecting to 
which. What can you do with that? Probably some fun things - but details 
would be nice.

On Saturday 21 July 2007 20:51, Michael Rogers wrote:
> Anonymous message reposted from Frost... the attack based on
> reconstructing the unique ID from an exposed ref sounds plausible.
> Should the identifiers used in swap requests be random instead?
>
> --- Forwarded message ---
>
> It all starts with harvesting refs. On IRC thats doable by just
> listening to completly public exchanges or (to get a few more) by
> activly querying them from other bots. On Frost it can be done by doing
> a few bogus exchanges or exchange requests in this board. Do that
> continually and you get a nice set of refs. You won't get all but thats
> not needed, its enough if you get a decent number.
> Next thing is spying on swap requests. Each swap exchange contains the
> locations of the exchanging nodes and their peers. It also contains a
> unique identifier for each of them. This identifier was added by the
> devs for debugging reasons: They wanted to be able to map the network
> topology, reconstructing it from the information gathered by the swap
> requests but there is nothing stopping other people from doing it too.
> After the reconstruction you have the reconstructed network and know the
> identifier, location and number of peers for each node. The only thing
> missing is the IP address.
> "Luckily" that identifier gets constructed out of parts of the nodes
> refs and the last time I read anything about it, it was planned to
> create it only out of not changing parts. If that was implemented that
> way and reading IRC logs suggests that, you can check for a given
> identifier if it was constructed out of a certain ref. That way you can
> map your harvested refs to your nodes in your reconstructed network
> topology and thus get IPs for them.
> Afterwards you have a really nice playground to do statistical attacks,
> with much needed info for each node.
> This whole attack is only suited to attack random people because if you
> want to target a certain person but don't have his ref: bad luck or at
> least it will get a whole lot harder. Still, its enough to possibly
> cause trouble to random targets and there are enough people who don't
> care who they hit, as long as they can cause trouble. See the spambot
> operator for (a rather harmless) example.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/2e807417/attachment.pgp 

From NEOatNHNG at users.sourceforge.net  Tue Jul 24 16:29:43 2007
From: NEOatNHNG at users.sourceforge.net (=?ISO-8859-15?Q?Michael_T=E4nzer?=)
Date: Tue, 24 Jul 2007 18:29:43 +0200
Subject: [freenet-dev] [Fwd: German Translation (de.l10n.v1)]
Message-ID: <46A628F7.1030201@users.sourceforge.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry, sent that mail without being subscribed to the list.

- -------- Original-Nachricht --------
Betreff: German Translation (de.l10n.v1)
Datum: Tue, 24 Jul 2007 06:17:29 +0200
Von: Michael T?nzer <NEOatNHNG at users.sourceforge.net>
An: devl at freenetproject.org

Hi folks,

I've just finished the German translation of Freenet (attached).

By the way, the "Key:" right on the homepage of FProxy in the box "Fetch
a Key" is not translatable. Looks a bit odd because it's the first thing
you see, could someone fix that?

Best regards,
Michael T?nzer
aka Thomas Anderson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGpij3PUBAMhFf+J4RAg88AJ0fI/B3RTCO7zdZfGQ2L5lAg93wBgCgqn4h
0OCTz9Nees+Nv15S+PS4edA=
=Gk92
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.unlisted.override.properties
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070724/a7bc363a/attachment.txt 

From toad at amphibian.dyndns.org  Wed Jul 25 16:43:22 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 17:43:22 +0100
Subject: [freenet-dev] [Fwd: German Translation (de.l10n.v1)]
In-Reply-To: <46A628F7.1030201@users.sourceforge.net>
References: <46A628F7.1030201@users.sourceforge.net>
Message-ID: <200707251743.28314.toad@amphibian.dyndns.org>

Thanks! Is this related to the partial german translation that saces 
committed? Also you should have a look at the changes to the strings when 
1048 comes out (there are often changes to existing strings as well as adding 
new strings).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/6793956b/attachment.pgp 

From toad at amphibian.dyndns.org  Wed Jul 25 16:54:46 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 17:54:46 +0100
Subject: [freenet-dev] Freenet 0.7 build 1048
Message-ID: <200707251754.52197.toad@amphibian.dyndns.org>

Freenet 0.7 build 1048 is now available. Please upgrade; this will be 
mandatory at 0:00 GMT on Friday. Major changes:
- German translation of the node interface
- The first-time wizard asks the user whether they want to enable opennet
- Major opennet fixes
- Significant memory usage improvements
- Fix Internal Error: data != returnBucket and remove the arbitrary limit of 
256 completed requests per client in FCP.

Please tell us if you have any problems either upgrading (hopefully the 
auto-update will work) or using the build. Use the bug tracker at 
https://bugs.freenetproject.org , the mailing lists or the freenet board on 
Frost.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/0243f7c4/attachment.pgp 

From NEOatNHNG at users.sourceforge.net  Wed Jul 25 17:27:25 2007
From: NEOatNHNG at users.sourceforge.net (=?ISO-8859-15?Q?Michael_T=E4nzer?=)
Date: Wed, 25 Jul 2007 19:27:25 +0200
Subject: [freenet-dev] [Fwd: German Translation (de.l10n.v1)]
In-Reply-To: <200707251743.28314.toad@amphibian.dyndns.org>
References: <46A628F7.1030201@users.sourceforge.net>
	<200707251743.28314.toad@amphibian.dyndns.org>
Message-ID: <46A787FD.4040601@users.sourceforge.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Toseland schrieb:
> Thanks! Is this related to the partial german translation that saces 
> committed? Also you should have a look at the changes to the strings when 
> 1048 comes out (there are often changes to existing strings as well as adding 
> new strings).

I didn't know about any partial translation already available, so I
guess it's not. I also have to admit, that I'm not so confident with
SVN, so I don't know what saces' translation looked like (If it's the
one currently available through the Web-Interface of the repository it's
exactly the one I contributed).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGp4f9PUBAMhFf+J4RAkl9AKCFP0B9lvpHlb5kfA7echQX4tg2FACfRkmA
x6ZEQTW9OvPWINfUTK5axlc=
=eICi
-----END PGP SIGNATURE-----


From toad at amphibian.dyndns.org  Wed Jul 25 17:39:11 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Wed, 25 Jul 2007 18:39:11 +0100
Subject: [freenet-dev] Propagating opennet refs through darknet nodes
Message-ID: <200707251839.16584.toad@amphibian.dyndns.org>

I propose that darknet nodes be allowed to forward announcements and path 
folding messages (ConnectDestination etc), without including their own 
noderefs.

Any objections?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070725/1ea7d616/attachment.pgp 

From luke771 at gmail.com  Wed Jul 25 20:34:45 2007
From: luke771 at gmail.com (luke771)
Date: Wed, 25 Jul 2007 22:34:45 +0200
Subject: [freenet-dev] l10n ita v20
Message-ID: <1185395685.24604.3.camel@u32.fastwebnet.it>

updated to Build 1048 r14339
-------------- next part --------------
BookmarkEditorToadlet.invalidKey=La chiave Freenet non ? valida.
BookmarkEditorToadlet.urlDecodeError=URL Decode Error
FileOffer.acceptTransferButton=Accetta Trasferimento
FileOffer.askUserTitle=Trasferimento file diretto.
FileOffer.commentLabel=Commenti:
FileOffer.failedReceiveHeader=Non ? stato possibile completare il trasferimento del file ${filename} da ${node}.
FileOffer.failedReceiveTitle=Trasferimento fallito
FileOffer.fileLabel=File:
FileOffer.mimeLabel=MIME Type:
FileOffer.offeredFileHeader=Il nodo ${name} offre il file:
FileOffer.rejectTransferButton=Rifiuta trasferimento
FileOffer.senderLabel=Mittente:
FileOffer.sizeLabel=Dimensioni:
FileOffer.succeededReceiveHeader=Il trasferimento del file ${filename} da ${node} ? stato completato.
FileOffer.succeededReceiveTitle=Trasferimento file completato
FirstTimeWizardToadlet.chooseNodeName=Il nome del nodo ? obbligatorio!
FirstTimeWizardToadlet.chooseNodeNameLong=Inserire un nome per il nodo nello spazio sottostante. Tale nome sara visibile soltanto ai peer ai quali il nodo ? connesso e a nessun altro. Si consiglia di usare il proprio nickname IRC possibilmente con qualche contatto in modo da essere reperibili in caso di problemi ("Mario Rossi nessuno at niente.com").
FirstTimeWizardToadlet.congratz=Benvenuto a bordo!
FirstTimeWizardToadlet.congratzLong=Congratulazioni, la configurazione di base del nodo Freenet ? completa. E' possibile cambiare e modificare ognuno dei parametri appena impostati usando la pagina "configurazione" che ? raggiungibile attraverso il menu sulla sinistra dell'interfaccia. Vi auguriamo una piacevole esperienza con Freenet.
FirstTimeWizardToadlet.connectToStrangers=Connetti con sconosciuti?
FirstTimeWizardToadlet.connectToStrangersLong=Permettendo connessioni con sconosciuti, questo nodo Freenet sar? meno sicuro; chiunque port? determinare che un nodo sta girando sul tuo computer e qualsiasi malintenzionato portebbe connettersi ad esso. per non permettere che Freenet si connetta a chiunque, bisogner? contattare almeno altre tre persone conosciute e fidate che gi? stiano usando Freenet e conettersi a loro manualmente.
FirstTimeWizardToadlet.continue=Continua
FirstTimeWizardToadlet.enableOpennet=Connettersi automaticamente a nodi gestiti da sconosciuti?
FirstTimeWizardToadlet.iDoTrust=Possiamo fidarci degli utenti connessi a ${interface} (${ip}) ?
FirstTimeWizardToadlet.isNetworkTrusted=La rete locale ? affidabile?
FirstTimeWizardToadlet.isNetworkTrustedLong=Possiamo fidarci della rete locale? Rispondendo di si a questa domanda, tutti i servizii forniti dal nodo Freenet saranno pienamente accessibili da chiunque sul network suddetto. E' possibile configurare un accesso pi? selettivo attraverso la pagina "configurazione" dopo aver completato questo wizard.
FirstTimeWizardToadlet.noNetworkIF=Non ? stata trovata nessuna interfaccia di rete addizionale
FirstTimeWizardToadlet.noNetworkIFLong=Freenet non ha trovato altre interfacce di rete, quindi dar? per scontato che l'utente si connetter? dal computer locale e solo da quello.
FirstTimeWizardToadlet.skipWizard=Non sono un novellino, lascia perdere il wizard.
FirstTimeWizardToadlet.step4Title=Freenet first time wizard! - Configurazione di rete
FirstTimeWizardToadlet.step5Title=Freenet first time wizard! - Congratulazioni, il nodo ? ora configurato.
FirstTimeWizardToadlet.step6Title=Configurazione automatica di Freenet - Congratulazioni, il tuo nodo ? ora configurato.
InsertException.longError.12=Binary blob format error
InsertException.shortError.12=Binary blob format error
N2NTMToadlet.noSuchFileOrCannotRead=Trasferimento fallito:File inesistente o illegibile.
OpennetUserAlert.warning=Il modo promiscuo ? attualmente attivato. Ci? significa che esso si connetter? con Sconosiuti, e quindi che chiunque potr? facilmente determinare che l'utente titolare del tale abbonamento sta usando Freenet. Molti attacchi vengono facilitati da questa modalit?, bloccare il nodo (per esempio a un firewall nazionale) diventa molto pi? facile, ed intoltre l'utente non ha controllo su chi si connette al suo nodo. Si raccomanda vivamente di procurarsi qualce connessione ad Amici (nodi fidati, gestiti da persone conosciute); il modo promiscuo va considerato una misura temporanea da utilizzarsi finch? non ci si potr? connettere ad Amici. Connettendosi esclusivamente a nodi gestiti da persone conosciute, pur non essendo impossibli degli attacchi da parte loro, risulter? comunque meno probabile l'esposizione ad agenzie governative (tipo servizi segreti o che so io) o altri "cattivi". Noa che aggiungendo un peer alla sezione Amici non cambia molto la situazione a meno che tale nodo non sia gestito da qualcuno di consciuto e di cui ci si fida (per ragioni sia di routing [instradamento] che di sicurezza)!
OpennetUserAlert.warningTitle=Avvertenza: Modo Promiscuo Attivato: Il nodo si connetter? a degli sconosciuti
PeersSayKeyBlownAlert.connectedSayBlownLabel=I seguenti nodi hanno rilevato un problema con la chiave  (si cerca attualmente di ottenere il certificato di revoca da loro):
PeersSayKeyBlownAlert.disconnectedSayBlownLabel=I seguenti nodi si sono disconnessi dopo aver comunicato che la chiave ? saltata, quindi non ? stato possibile richiamare il certificato di revoca:
PeersSayKeyBlownAlert.failedFetch=Non ? stato possibile scaricare il certificato di revoca. Le possibili cause di tale evento includono la possibilit? di un attacco sul nodo locale volto a fargli scaricare ed installare un aggiornamento nonostante la chiave sia saltata, o la possibilit? che dei nodi stiano "mentendo" circa la chiave di revoca. Si prega di contattare gli sviluppatori di Freenet per cercare di mettere ordine in questo casino.
PeersSayKeyBlownAlert.failedTransferSayBlownLabel=Questi nodi hanno comunicato che la chiave di revoca ? saltata ma poi non hanno completato il trasferimento del certificato di revoca:
PeersSayKeyBlownAlert.fetching=Il nodo sta scaricando il certificato di revoca contentnte spiegazioni pi? dettagliate.
PeersSayKeyBlownAlert.intro=Uno o pi? peers ci comunicano che la chiave di revoca per l'aggiornamento automatico ? saltata. Questo significa che qualcuno potrebbe essere venuto a conoscenza della chiave privata del sistema di autoaggiornamento, cosa che potrebbe far eseguire al nodo il codice che l'attaccante volesse fargli eseguire (se l'aggiornamento venisse eseguito): per prevenire tale eventualit?, il sistema di autoaggiornamento ? stato disabilitato. E' anche possibile che dei peers stiano deliberatamente mentendo a proposito della chiave di revoca.
PeersSayKeyBlownAlert.titleWithCount=chiave di Auto-aggiornamento saltata, evento confermato da ${count} peer!
QueueToadlet.remove=Elimina
SimpleToadletServer.doRobots=Escludere robots via robots.txt?
SimpleToadletServer.doRobotsLong=Pubblica /robots.txt che dice a persone, Google, spiders, wget, ecc. di lasciarci in pace.
TimeSkewDetectedUserAlert.text=Una discepanza temporale ? stata rilevata dal nodo. Questo ? un inconveniente grave, il nodo non potr? funzionare correttamente finch? non vi si sar? ovviato. Tra le cause pi? comuni, la modalit? powersafe mal configurata, cattiva sincronizzazione tra i clients del network, hardware bugs.
TimeSkewDetectedUserAlert.title=Discrepanza temporale!
Toadlet.no=No
Toadlet.ok=Ok
Toadlet.yes=S?
End

From nextgens at freenetproject.org  Thu Jul 26 03:14:06 2007
From: nextgens at freenetproject.org (NextGen$)
Date: Thu, 26 Jul 2007 03:14:06 +0000
Subject: [freenet-dev] Propagating opennet refs through darknet nodes
In-Reply-To: <200707251839.16584.toad@amphibian.dyndns.org>
References: <200707251839.16584.toad@amphibian.dyndns.org>
Message-ID: <20070726031405.GB23461@freenetproject.org>

* Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-25 18:39:11]:

> I propose that darknet nodes be allowed to forward announcements and path 
> folding messages (ConnectDestination etc), without including their own 
> noderefs.
> 
> Any objections?

_o/
It's a bad idea.
Be informed that my node wont behave that way...


From NEOatNHNG at users.sourceforge.net  Thu Jul 26 12:36:52 2007
From: NEOatNHNG at users.sourceforge.net (=?ISO-8859-15?Q?Michael_T=E4nzer?=)
Date: Thu, 26 Jul 2007 14:36:52 +0200
Subject: [freenet-dev] German Translation (freenet.l10n.de.v1048)
Message-ID: <46A89564.6010501@users.sourceforge.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here's the updated German translation (for node version 1048).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqJVkPUBAMhFf+J4RAjVSAJ0ey8SuXXdD7DnBA+qvSpXdy75HrQCgnVqv
a2Lc7Wctq/6aobaGulAoxyI=
=P7r+
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.de.override.properties
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070726/6d38bb65/attachment.txt 

From toad at amphibian.dyndns.org  Thu Jul 26 19:01:34 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 26 Jul 2007 20:01:34 +0100
Subject: [freenet-dev] Propagating opennet refs through darknet nodes
In-Reply-To: <20070726031405.GB23461@freenetproject.org>
References: <200707251839.16584.toad@amphibian.dyndns.org>
	<20070726031405.GB23461@freenetproject.org>
Message-ID: <200707262001.35110.toad@amphibian.dyndns.org>

On Thursday 26 July 2007 04:14, NextGen$ wrote:
> * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-25 18:39:11]:
> > I propose that darknet nodes be allowed to forward announcements and path
> > folding messages (ConnectDestination etc), without including their own
> > noderefs.
> >
> > Any objections?
>
> _o/
> It's a bad idea.
> Be informed that my node wont behave that way...

Why, precisely, is it a bad idea? As far as I can tell it doesn't compromise 
the nodes which only relay and never send their own noderef?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070726/7ea59778/attachment.pgp 

From toad at amphibian.dyndns.org  Thu Jul 26 19:05:19 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 26 Jul 2007 20:05:19 +0100
Subject: [freenet-dev] Propagating opennet refs through darknet nodes
In-Reply-To: <200707262001.35110.toad@amphibian.dyndns.org>
References: <200707251839.16584.toad@amphibian.dyndns.org>
	<20070726031405.GB23461@freenetproject.org>
	<200707262001.35110.toad@amphibian.dyndns.org>
Message-ID: <200707262005.19639.toad@amphibian.dyndns.org>

On Thursday 26 July 2007 20:01, Matthew Toseland wrote:
> On Thursday 26 July 2007 04:14, NextGen$ wrote:
> > * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-25 18:39:11]:
> > > I propose that darknet nodes be allowed to forward announcements and
> > > path folding messages (ConnectDestination etc), without including their
> > > own noderefs.
> > >
> > > Any objections?
> >
> > _o/
> > It's a bad idea.
> > Be informed that my node wont behave that way...
>
> Why, precisely, is it a bad idea? As far as I can tell it doesn't
> compromise the nodes which only relay and never send their own noderef?

Another advantage is it provides an excellent reason to get darknet peers, 
since they can reseed your opennet connections... although maybe it would 
result in people connecting to people they don't know?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070726/a0727eb1/attachment.pgp 

From toad at amphibian.dyndns.org  Thu Jul 26 19:06:37 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 26 Jul 2007 20:06:37 +0100
Subject: [freenet-dev] l10n ita v20
In-Reply-To: <1185395685.24604.3.camel@u32.fastwebnet.it>
References: <1185395685.24604.3.camel@u32.fastwebnet.it>
Message-ID: <200707262006.37623.toad@amphibian.dyndns.org>

On Wednesday 25 July 2007 21:34, luke771 wrote:
> updated to Build 1048 r14339

Applied, thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070726/a5d6f43d/attachment.pgp 

From toad at amphibian.dyndns.org  Thu Jul 26 19:09:09 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Thu, 26 Jul 2007 20:09:09 +0100
Subject: [freenet-dev] German Translation (freenet.l10n.de.v1048)
In-Reply-To: <46A89564.6010501@users.sourceforge.net>
References: <46A89564.6010501@users.sourceforge.net>
Message-ID: <200707262009.10144.toad@amphibian.dyndns.org>

On Thursday 26 July 2007 13:36, Michael T?nzer wrote:
> Here's the updated German translation (for node version 1048).

Applied.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070726/62ecbd34/attachment.pgp 

From batosai at batosai.net  Thu Jul 26 19:22:41 2007
From: batosai at batosai.net (batosai)
Date: Thu, 26 Jul 2007 21:22:41 +0200
Subject: [freenet-dev] French Translation (1048)
Message-ID: <46A8F481.2040003@batosai.net>

Hi,

Here's an updated French translation.

Regards
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.fr.override.properties
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070726/44552176/attachment.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3355 bytes
Desc: S/MIME Cryptographic Signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070726/44552176/attachment.bin 

From toad at amphibian.dyndns.org  Fri Jul 27 11:54:50 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Fri, 27 Jul 2007 12:54:50 +0100
Subject: [freenet-dev] Freenet 0.7 build 1049
Message-ID: <200707271254.50889.toad@amphibian.dyndns.org>

Freenet 0.7 build 1049 is now available. Please upgrade. This build fixes a 
major bug with temporary files which was introduced in the previous version, 
which was causing "Bucket is read-only" errors on completing a request. 
Thanks to everyone who reported this bug or helped to debug it. There is also 
a change to the startup process to fix a plugins NPE, and updated 
translations in Italian, German and French.

Please upgrade, and if you have any problems, report bugs, ideally via the bug 
tracker ( https://bugs.freenetproject.org/ ) but alternatively through IRC, 
the mailing lists or Frost.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070727/e69f86ae/attachment.pgp 

From NEOatNHNG at users.sourceforge.net  Fri Jul 27 14:27:33 2007
From: NEOatNHNG at users.sourceforge.net (=?ISO-8859-15?Q?Michael_T=E4nzer?=)
Date: Fri, 27 Jul 2007 16:27:33 +0200
Subject: [freenet-dev] German Translation (freenet.l10n.de.v1049)
Message-ID: <46AA00D5.20502@users.sourceforge.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here's the current translation. The file looks a little too big to me, I
changed just a few things (should be about 11 strings) but the
override-file gives 34 lines and it looks to me as if the things I
changed in last version are also included. I'm not sure whether it's a
bug or just dumbness of my own, do I have to remove translation
overrides I made in a previous version manually? If so it would be
probably a good Idea to have a button "Remove all translation overrides"
(combined with ten questions whether you're sure or completely insane)
to make this process much easier. But I completely understand if you
have more important things to do.

Definitely a bug is this issue:
https://bugs.freenetproject.org/view.php?id=1576
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqgDVPUBAMhFf+J4RAk+lAJ0Udl7nw2GV7Fa/shMBuNsRAsJSdQCfdDFd
CzlyW1W1ElZtADMJsjD6I6o=
=OOeS
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.de.override.properties
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070727/d8b0f8c3/attachment.txt 

From toad at amphibian.dyndns.org  Fri Jul 27 18:19:58 2007
From: toad at amphibian.dyndns.org (Matthew Toseland)
Date: Fri, 27 Jul 2007 19:19:58 +0100
Subject: [freenet-dev] Freenet 0.7 build 1050
Message-ID: <200707271920.03908.toad@amphibian.dyndns.org>

Freenet 0.7 build 1050 is now available. The main change is to fix insert 
resuming and a NullPointerException on startup if FCP, Fproxy or TMCI was 
disabled. Please upgrade, and report any bugs you find.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070727/0976fe52/attachment.pgp 

From bbackde at googlemail.com  Sat Jul 28 05:28:54 2007
From: bbackde at googlemail.com (bbackde at googlemail.com)
Date: Sat, 28 Jul 2007 07:28:54 +0200
Subject: [freenet-dev] Propagating opennet refs through darknet nodes
In-Reply-To: <200707262005.19639.toad@amphibian.dyndns.org>
References: <200707251839.16584.toad@amphibian.dyndns.org>
	<20070726031405.GB23461@freenetproject.org>
	<200707262001.35110.toad@amphibian.dyndns.org>
	<200707262005.19639.toad@amphibian.dyndns.org>
Message-ID: <d6149a790707272228g2a2b4033lc21f66a240ce137c@mail.gmail.com>

I like it.

On 7/26/07, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> On Thursday 26 July 2007 20:01, Matthew Toseland wrote:
> > On Thursday 26 July 2007 04:14, NextGen$ wrote:
> > > * Matthew Toseland <toad at amphibian.dyndns.org> [2007-07-25 18:39:11]:
> > > > I propose that darknet nodes be allowed to forward announcements and
> > > > path folding messages (ConnectDestination etc), without including their
> > > > own noderefs.
> > > >
> > > > Any objections?
> > >
> > > _o/
> > > It's a bad idea.
> > > Be informed that my node wont behave that way...
> >
> > Why, precisely, is it a bad idea? As far as I can tell it doesn't
> > compromise the nodes which only relay and never send their own noderef?
>
> Another advantage is it provides an excellent reason to get darknet peers,
> since they can reseed your opennet connections... although maybe it would
> result in people connecting to people they don't know?
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________


From m.rogers at cs.ucl.ac.uk  Mon Jul 30 21:57:30 2007
From: m.rogers at cs.ucl.ac.uk (Michael Rogers)
Date: Mon, 30 Jul 2007 22:57:30 +0100
Subject: [freenet-dev] Should swap identifiers be random?
In-Reply-To: <200707251640.59607.toad@amphibian.dyndns.org>
References: <46A263B9.9060608@cs.ucl.ac.uk>
	<200707251640.59607.toad@amphibian.dyndns.org>
Message-ID: <46AE5ECA.3080908@cs.ucl.ac.uk>

Matthew Toseland wrote:
> If we are to include UIDs for our 
> peers then we must know them.

Are peers we've never connected to included in the list of peers used
for swapping?

Actually, come to think of it, why do swap requests need to include a
long-term node identifier at all? Why not just the node's location and
its peers' locations? (Sorry if I'm missing something obvious.)

> What can you do with that? Probably some fun things - but details 
> would be nice.

To be honest I can't think of any specific attacks, but a map of the
network still seems like a useful thing for an attacker to have.
Removing the routing location from the noderef and making swap
identifiers random would make it harder to map the network - it is worth
making those changes just in case, or is that just my usual paranoia
talking? ;-)

Cheers,
Michael


From cornuwel at gmail.com  Fri Jul 27 16:10:52 2007
From: cornuwel at gmail.com (Julien Cornuwel)
Date: Fri, 27 Jul 2007 18:10:52 +0200
Subject: [freenet-dev] French Translation (1049)
Message-ID: <46AA190C.5020700@gmail.com>

Updated file...

Did you notice the left menu was displayed in english since 1049 ?

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freenet.l10n.fr.override.properties
Url: http://emu.freenetproject.org/pipermail/devl/attachments/20070727/df67f6f6/attachment.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070727/df67f6f6/attachment.pgp