Jep :
Jep :
Matthew Toseland :
Freenet 0.7.5 build 1319 is now available. This includes further
critical fixes to the new packet format, particularly affecting NATed
nodes or nodes connecting to them. Please upgrade ASAP! Thanks.
Freenet 0.7.5 Build #1319 build01320
Freenet-ext Build #26
Jep:
Jep :
Jep :
Matthew Toseland :
Freenet 0.7.5 build 1319 is now available. This includes further
critical fixes to the new packet format, particularly affecting
NATed nodes or nodes connecting to them. Please upgrade ASAP! Thanks.
Freenet 0.7.5 Build #1319 build01320
Freenet-ext
Freenet 0.7.5 build 1321 is now available. It makes 1319 mandatory as of
tomorrow. The real changes were in 1320, but unfortunately I made a mistake
resulting in 1320 describing itself as 1319 yet making 1320 mandatory. Sorry
folks, the aftermath of the new packet format merge has been rather
When the new packet format was merged last week it caused chaos. There were
severe bugs resulting in connectivity problems, too much retransmission, and so
on, and then to fix this we had multiple mandatory builds - not mandatory
immediately but still disruptive.
All this inevitably messes up
On Wednesday 05 January 2011 14:01:31 Jan wrote:
Jep:
Jep :
Jep :
Matthew Toseland :
Freenet 0.7.5 build 1319 is now available. This includes further
critical fixes to the new packet format, particularly affecting
NATed nodes or nodes connecting to them. Please upgrade ASAP! Thanks.
On Monday 03 January 2011 21:29:34 Dsoslglece wrote:
Le 02/01/11 23:08, Matthew Toseland a écrit :
Freenet 0.7.5 build 1319 is now available. This includes further critical
fixes to the new packet format, particularly affecting NATed nodes or nodes
connecting to them. Please upgrade ASAP!
On Sunday 02 January 2011 09:57:18 Jep wrote:
Matthew Toseland :
On Friday 31 December 2010 20:39:13 Jan wrote:
Jep :
[nothing connects]
1317/1318 may help.
Doesn't look that way.
Disconnected for 20 hours now and manual update an hour ago to 1318 has
changed only the number at
On Sunday 02 January 2011 21:22:49 Jep wrote:
Jep :
Matthew Toseland :
On Friday 31 December 2010 20:39:13 Jan wrote:
Jep :
[nothing connects]
1317/1318 may help.
Doesn't look that way.
Disconnected for 20 hours now and manual update an hour ago to 1318 has
changed only
On Saturday 01 January 2011 19:08:05 Fabio Spelta wrote:
We do, but it's not very prominent because most users don't use it. Reread
the download page.
I would rather suggest you to put that directly into the install
instructions here.
http://freenetproject.org/install.html
I didn't
On Tuesday 04 January 2011 16:22:20 Daxter wrote:
On Jan 1, 2011, at 11:57 AM, Matthew Toseland wrote:
On Saturday 01 January 2011 17:51:41 Fabio Spelta wrote:
Glad to know it. Where are they published?
I'd suggest you to publish the instructions and the links to do so right
into the
On Tuesday 04 January 2011 16:56:14 Fabio Spelta wrote:
Am I doing something wrong?
You have to install the signer's public key.
I strongly agree, this should be documented step by step because it's very
important.
To get mr. Toseland's latest key run this:
gpg --recv-keys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks for the info.
I was already wondering what was wrong with my node. Since it complained
that my version is to old, but did not update...
Using Freenet over the last days has been difficult, with all the
problems. I know that those things
Which means that if somebody is attacking you he will substitute both the
signature file and my key when you download it. So you gain very little,
unless you have some other trust path.
Well, they should also hijack the connection with the keyserver site. While
being the man in the middle in
On Wednesday 05 January 2011 19:49:36 Fabio Spelta wrote:
Which means that if somebody is attacking you he will substitute both the
signature file and my key when you download it. So you gain very little,
unless you have some other trust path.
Well, they should also hijack the
On Wednesday 05 January 2011 19:49:36 Fabio Spelta wrote:
Which means that if somebody is attacking you he will substitute both the
signature file and my key when you download it. So you gain very little,
unless you have some other trust path.
Well, they should also hijack the
Hi,
I got the mentioned exception here: http://127.0.0.1:/downloads/
Before that I had a OutOfMemoryError and tried a ./run.sh stop but i
didn't help.
Here is the exception log:
http://www.mxchange.org/downloads/freenet/concurrent.txt
Regards,
Roland
signature.asc
Description: This is a
Matthew Toseland :
On Sunday 02 January 2011 21:22:49 Jep wrote:
Jep :
[...]
Because it sometimes works better, I start Freenet using 'services.msc'.
Trying that, I noticed name and location of 'freenetwrapper.exe' as well
as the location of 'wrapper.conf' have changed but not the registry
Hi all,
I have watched this strange behavior for some days and I think it is
related to something really strange. I have security level NORMAL HIGH
HIGH so I need to enter my password to decrypt the node.db4o.crypt.
While I do not enter the password, the memory usage remains at around
100-200 MB
18 matches
Mail list logo
