--- Matthew Toseland <[EMAIL PROTECTED]> wrote:
> On Tuesday 12 February 2008 17:08, Matthew Toseland wrote:
> > AFAICS this is the way forward. Since Java attempts to use POSIX priorities
> > and they don't do anything on Linux, and since thread priorities work on
> > Linux (and presumably on Sol
--- Matthew Toseland wrote:
> On Tuesday 12 February 2008 17:08, Matthew Toseland wrote:
> > AFAICS this is the way forward. Since Java attempts to use POSIX priorities
> > and they don't do anything on Linux, and since thread priorities work on
> > Linux (and presumably on Solaris), it shouldn't
Matthew Toseland <[EMAIL PROTECTED]> wrote:
> Beyond that, the only realistic option appears to be an external daemon
> running at a lower nice level to do CPU-intensive jobs and FEC encoding and
> decoding in particular.
Thread.yield() comes to mind. But this is ugly.
Wouldn't it be sufficient
Matthew Toseland wrote:
> Beyond that, the only realistic option appears to be an external daemon
> running at a lower nice level to do CPU-intensive jobs and FEC encoding and
> decoding in particular.
Thread.yield() comes to mind. But this is ugly.
Wouldn't it be sufficient if the java thread
--- Matthew Toseland <[EMAIL PROTECTED]> wrote:
> Hmmm I still don't understand - show an error message if the user
> types in a domain?
There are fraudsters out there who set up sites which look exactly like
some legitimate site. If you try to log on, they grab your credentials
and perform action
--- Matthew Toseland wrote:
> Hmmm I still don't understand - show an error message if the user
> types in a domain?
There are fraudsters out there who set up sites which look exactly like
some legitimate site. If you try to log on, they grab your credentials
and perform actions on the legitimate
--- Matthew Toseland <[EMAIL PROTECTED]> wrote:
> is a major problem, but I'm not sure what we can do about it. It's
> mentioned in the README (well the 0.5 readme at least), but who
> reads it?
The web interface of 0.5 has a prominent link to the README in the Node
Information box on the left. Th
--- Matthew Toseland wrote:
> is a major problem, but I'm not sure what we can do about it. It's
> mentioned in the README (well the 0.5 readme at least), but who
> reads it?
The web interface of 0.5 has a prominent link to the README in the Node
Information box on the left. That should sufficien
--- Florent Daignière <[EMAIL PROTECTED]> wrote:
> There is at least a fourth one we are immune to in .7... The "If I
> read anything looking like a RSS feed, I decide to ignore the
> mime-type" one.
Thanks for this information. I take it this is true for ATOM feeds to?
Jack
--- Florent Daigni?re wrote:
> There is at least a fourth one we are immune to in .7... The "If I
> read anything looking like a RSS feed, I decide to ignore the
> mime-type" one.
Thanks for this information. I take it this is true for ATOM feeds to?
Jack
___
Hi,
I'm in the process of updating the README of 0.5 and found the section
on securing Mozilla in need of a rewrite. I haven't found a similar
section in the 0.7 README, so the follwing information might be of
interest for 0.7, too.
I know of three Mozilla features potentially destroying your ano
Hi,
I'm in the process of updating the README of 0.5 and found the section
on securing Mozilla in need of a rewrite. I haven't found a similar
section in the 0.7 README, so the follwing information might be of
interest for 0.7, too.
I know of three Mozilla features potentially destroying your ano
--- Matthew Toseland <[EMAIL PROTECTED]> wrote:
> Are you planning on maintaining the unstable branch (0.6) ? If so,
> why? We deprecated it, is there any good reason to revive it?
The differences between stable and unstable are very small (try diff
-ruwB -x .svn stable/ unstable/, that returns on
--- Matthew Toseland wrote:
> Are you planning on maintaining the unstable branch (0.6) ? If so,
> why? We deprecated it, is there any good reason to revive it?
The differences between stable and unstable are very small (try diff
-ruwB -x .svn stable/ unstable/, that returns only few dozen K of
d
Hi,
I've applied the Diffie-Hellman patch to unstable now. Could Nextgens
or a different site admin apply the same patch to the unstable
build.xml that was applied to the stable one in revs 16002/16003/16113,
please? Thank you!
Jack
___
Hi,
I've applied the Diffie-Hellman patch to unstable now. Could Nextgens
or a different site admin apply the same patch to the unstable
build.xml that was applied to the stable one in revs 16002/16003/16113,
please? Thank you!
Jack
___
My reply to this message appears to have gone lost, so I'll try again:
--- Florent Daignière <[EMAIL PROTECTED]> wrote:
> I've commited something in r16002.
Thanks! But the auto-generated
http://downloads.freenetproject.org/freenet-stable-latest.tgz still
contains jars from build 5107. The timest
My reply to this message appears to have gone lost, so I'll try again:
--- Florent Daigni?re wrote:
> I've commited something in r16002.
Thanks! But the auto-generated
http://downloads.freenetproject.org/freenet-stable-latest.tgz still
contains jars from build 5107. The timestamps are from May 1
--- Florent Daignière <[EMAIL PROTECTED]>
wrote:
> * Jack O'Lantern <[EMAIL PROTECTED]> [2007-11-25
> 05:33:22]:
>
> > Hi,
> >
> > currently, the official public freenet repository
is
> > svn://freenet.googlecode.com/svn, while the
> &
--- Florent Daigni?re
wrote:
> * Jack O'Lantern [2007-11-25
> 05:33:22]:
>
> > Hi,
> >
> > currently, the official public freenet repository
is
> > svn://freenet.googlecode.com/svn, while the
> > sourceforge CVS repository is obsolete. I propos
Hi,
currently, the official public freenet repository is
svn://freenet.googlecode.com/svn, while the
sourceforge CVS repository is obsolete. I propose to
change the legacy build.xml file to reflect this
situation. The proposed new file and its diff to
r15948 are attached to this message.
Here is
Hi,
currently, the official public freenet repository is
svn://freenet.googlecode.com/svn, while the
sourceforge CVS repository is obsolete. I propose to
change the legacy build.xml file to reflect this
situation. The proposed new file and its diff to
r15948 are attached to this message.
Here is
--- Juiceman <[EMAIL PROTECTED]> wrote:
> On Nov 24, 2007 2:45 PM, Thomas <[EMAIL PROTECTED]>
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > freenet.googlecode.com is only synced once a day,
r15947 and r15948 are commits from today, so they
> > should be in the google-repo
--- Juiceman wrote:
> On Nov 24, 2007 2:45 PM, Thomas
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > freenet.googlecode.com is only synced once a day,
r15947 and r15948 are commits from today, so they
> > should be in the google-repo tomorrow.
>
> The auto-builder uses
Hi,
there is something strange going on with the automated
freenet 0.5 builds.
http://downloads.freenetproject.org/freenet-stable-latest.src.tbz
contains the latest (build 5108) source code. But the
jars in the dist/ directory are still the from the old
5107 build.
http://downloads.freenetproject.
Hi,
there is something strange going on with the automated
freenet 0.5 builds.
http://downloads.freenetproject.org/freenet-stable-latest.src.tbz
contains the latest (build 5108) source code. But the
jars in the dist/ directory are still the from the old
5107 build.
http://downloads.freenetproject.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --- Florent Daignière <[EMAIL PROTECTED]>
wrote:
> Needless to say that it has broken the auto-builder.
> I have fixed the svn permissions on the buildfile.
auto-builder? Tell me more! In any case, it does build
now with "ant dist".
One question co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --- Florent Daigni?re
wrote:
> Needless to say that it has broken the auto-builder.
> I have fixed the svn permissions on the buildfile.
auto-builder? Tell me more! In any case, it does build
now with "ant dist".
One question concerning repositori
Hi,
it took me some time but I managed to subscribe to
this list through TOR. I've sent and canceled a
previous message, sorry for the confusion.
I've attached a patch for freenet 0.5. It fixes the
Diffie-Hellman exponential weakness. I hope I caught
every instance of this weakness in the code. P
Hi,
it took me some time but I managed to subscribe to
this list through TOR. I've sent and canceled a
previous message, sorry for the confusion.
I've attached a patch for freenet 0.5. It fixes the
Diffie-Hellman exponential weakness. I hope I caught
every instance of this weakness in the code. P
30 matches
Mail list logo
