Please note that if you have a ~/.mailFredStatus file, you
need to delete the DIAGNOSTICS= line in order to use the
new default. --writedefaults will put the new defaults into
the file.
changelog:
Added more diagnostics. Print the time of accumulation in
human-readable form. Needed temp files
What if the time delay is proportional to how far away from your
specialization the requested key is? That way, if you really are unlikely to
have the key then you hide it more but requests for keys that you really
ought to have need not be penalized.
-- jeek
- Original Message -
From:
Damn, this got too long. If My Solution (see below) has been
discussed before, please point me to the topic so I can read what was said.
The problem:
First, the number of QR:s should be reduced since they degrade the
efficiency of the network. After all, it would be better if
Ok, now I know I must be missing something here
;-)
"But then the attacker just needs to
account for the fact that you will try to fake it by fake-route to one other
node. So, he discounts the time he thinks it would take you to
real-route (he can measure this by sending you requests on
--- Newsbyte [EMAIL PROTECTED] wrote:
As for the question at hand; I'm no coder, but as far as I've understood, there is
an estimator
of how much time it would cost to retrieve something from a node(?)
Can't you make something that
1)checks if the requested item is in it's store
2)if
Newsbyte wrote:
Ok, now I know I must be missing something here ;-)
But then the attacker just needs to account for the fact that you will
try to fake it by fake-route to one other node. So, he discounts the
time he thinks it would take you to real-route (he can measure this by
sending you
Why isn't an initial routing table specialization for an announcee done?
Wasn't it so before.. The announcement contained a key that everyone
that received the announcement used as initial specialization (and
thereby they all agreed about the initial specialization for a given
node).
As it is now
- Original Message -
From: Newsbyte
To: Newsbyte
Sent: Friday, November 07, 2003 12:31 PM
Subject: Re: A really easy way to defeat datastore probingtiming
attacks?
"Did I understand you correctly?
Before we continue, I gotta make sure we are talking about the same
thing."
Update of /cvsroot/freenet/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv2788
Modified Files:
Makefile
Log Message:
updated to reflect changes in java tree
Index: Makefile
===
RCS file: /cvsroot/freenet/freenet/Makefile,v
We need to set LD_ASSUME_KERNEL on Linux 2.6, as well as on redhat etc.
I have some bash code to do this, but for start-freenet.sh it needs to
be cross platform, so I hoped somebody here might be able to help. My
current code is:
#!/bin/bash
if ([ `uname` == 'Linux' ]); then
echo Linux detected;
On Fri, Nov 07, 2003 at 12:00:40PM +0100, Niklas Bergh wrote:
Why isn't an initial routing table specialization for an announcee done?
Wasn't it so before.. The announcement contained a key that everyone
that received the announcement used as initial specialization (and
thereby they all agreed
Newsbyte wrote:
- Original Message -
*From:* Newsbyte mailto:[EMAIL PROTECTED]
*To:* Newsbyte mailto:[EMAIL PROTECTED]
*Sent:* Friday, November 07, 2003 12:31 PM
*Subject:* Re: A really easy way to defeat datastore probingtiming attacks?
Did I understand you correctly? Before we
I have no idea if this is coincidence, but just in case somebody else
notices it?
For the last 6 or so unstable releases my node here has been QRing nearly
exclusively for the relatively good (?) reason of bandwidth limit
saturation. With the update to 6316 it's now consistently QRing due to
On Fri, 2003-11-07 at 11:02, Toad wrote:
We need to set LD_ASSUME_KERNEL on Linux 2.6, as well as on redhat etc.
I have some bash code to do this, but for start-freenet.sh it needs to
be cross platform, so I hoped somebody here might be able to help. My
current code is:
#!/bin/bash
if ([
Tom Kaitchuck wrote:
The problem with this is that it doesn't really work. For the sake of
argument, lets say that the time it takes your node to return some data is T,
and the time it would take it to get it from the next node is T + 100.
Right now if we return is less than T+100, they can
--- Martin Stone Davis [EMAIL PROTECTED] wrote:
Explain how your system works in a network of all new nodes, where all
nodes' estimates of time-delays is initially very bad (since they're
newbies). How does the first query and data retrieval work?
Well they could pretty quickly learn
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv18179/src/freenet
Modified Files:
Version.java PeerHandler.java
Log Message:
6317:
Make most xfer rates bytes/sec, fix conversion errors leading to crazy estimates,
change transferSucceeded arguments.
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv18179/src/freenet/node
Modified Files:
Main.java
Log Message:
6317:
Make most xfer rates bytes/sec, fix conversion errors leading to crazy estimates,
change transferSucceeded arguments.
Add min/max
Update of /cvsroot/freenet/freenet/src/freenet/node/rt
In directory sc8-pr-cvs1:/tmp/cvs-serv18179/src/freenet/node/rt
Modified Files:
NGRouting.java NodeEstimatorFactory.java NGRoutingTable.java
StandardNodeEstimator.java NodeEstimator.java
Log Message:
6317:
Make most xfer
Update of /cvsroot/freenet/freenet/src/freenet/client/http
In directory sc8-pr-cvs1:/tmp/cvs-serv18179/src/freenet/client/http
Modified Files:
NodeStatusServlet.java
Log Message:
6317:
Make most xfer rates bytes/sec, fix conversion errors leading to crazy estimates,
change
On Fri, 07 Nov 2003, Edward J. Huff wrote:
#! /bin/ksh
Well, that's pretty useless right there.
/bin/sh is pretty standard. ksh is optional and fairly rare
in my experience.
--Dan
pgp0.pgp
Description: PGP signature
___
Devl mailing list
Well, I picked up a 10 meg circuit (yes, really 10 meg. It's delivered
over ethernet) to the internet, and stuck my freenet node on it.
* Smoothed local mean traffic (queries per hour): 118767.081
* Smoothing half life (lsHalfLifeHours): 1.200 hour.
* That is, the rate decays
Update of /cvsroot/freenet/freenet/src/freenet/node/states/announcement
In directory sc8-pr-cvs1:/tmp/cvs-serv20608/src/freenet/node/states/announcement
Modified Files:
NewAnnouncement.java
Log Message:
6318:
Probabilistic rejection, based on Benny Amorsen's patch to devl ages ago.
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv20608/src/freenet/node
Modified Files:
Node.java
Log Message:
6318:
Probabilistic rejection, based on Benny Amorsen's patch to devl ages ago.
Should be more suitable than binary rejection on
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv20608/src/freenet
Modified Files:
Version.java Core.java
Log Message:
6318:
Probabilistic rejection, based on Benny Amorsen's patch to devl ages ago.
Should be more suitable than binary rejection on
Turned out to be an NPTL LD_ASSUME_KERNEL problem after all. Fixed now
afaics, although hot code substitution doesn't work.
On Fri, Nov 07, 2003 at 10:24:26PM +0100, Thomas Themel wrote:
Hi,
Toad ([EMAIL PROTECTED]) wrote on 2003-11-07:
It has worked flawlessly for me on a variety of
On Fri, Nov 07, 2003 at 06:23:17PM +0100, Some Guy wrote:
As I said earlier this kind of delaying is unnessesary. Private Cache + Premix
removes any need
to do this.
Does it? I thought that the list was collectively very concerned about
some widely ignored legal idea called entrapment ? :)
Update of /cvsroot/freenet/freenet/src/freenet/node/states/FNP
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/node/states/FNP
Modified Files:
NewRequest.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between rejecting
Update of /cvsroot/freenet/freenet/src/freenet/client
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/client
Modified Files:
VirtualClient.java InternalClient.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between
Update of /cvsroot/freenet/freenet/src/freenet/node/states/announcement
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/node/states/announcement
Modified Files:
NewAnnouncement.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet
Modified Files:
Version.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between rejecting nearly all requests, and rejecting
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/node
Modified Files:
Node.java FailureTable.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between rejecting nearly
This has been applied in 6219; I suspect it will be a better fit with
NGRouting than the old reject everything or reject nothing technique.
- Forwarded message from Benny Amorsen [EMAIL PROTECTED] -
From: Benny Amorsen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [freenet-dev]
Update of /cvsroot/freenet/freenet/src/freenet/node/http/infolets
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/node/http/infolets
Modified Files:
GeneralInfolet.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between
Update of /cvsroot/freenet/freenet/src/freenet/client/http
In directory sc8-pr-cvs1:/tmp/cvs-serv26517/src/freenet/client/http
Modified Files:
NodeStatusServlet.java
Log Message:
6319:
Probabilistic rejection, based on work by Benny Amorsen.
Make a distinction in stats between rejecting
--- Toad [EMAIL PROTECTED] wrote:
On Fri, Nov 07, 2003 at 06:23:17PM +0100, Some Guy wrote:
As I said earlier this kind of delaying is unnessesary. Private Cache + Premix
removes any
need
to do this.
Does it?
Sure, what's in your public store will have nothing to do with what you
Currently the situation, even with the recently integrated probabilistic
rejection, is as follows:
We start off with no load
We accept some queries
Eventually we use up our outbound bandwidth, and due to either
messageSendTimeRequest or the output bandwidth limit, we reject queries
until our
One radical solution:
Remove the code to reject queries when the bandwidth limit is exceeded!
NGRouting can figure out when nodes are slow due to long term overload a
lot more easily and less alchemically than it can deal with query
rejections. Or so the theory goes. Am I smoking crack here?
Update of /cvsroot/freenet/freenet/src/freenet/node/states/FNP
In directory sc8-pr-cvs1:/tmp/cvs-serv21521/src/freenet/node/states/FNP
Modified Files:
NewRequest.java
Log Message:
6320:
Set a proper timeout on QueryRejected messages from NewRequest - these account for the
vast majority
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv21521/src/freenet
Modified Files:
Version.java PeerPacketMessage.java
Log Message:
6320:
Set a proper timeout on QueryRejected messages from NewRequest - these account for the
vast majority of messages,
Update of /cvsroot/freenet/freenet/src/freenet/node/rt
In directory sc8-pr-cvs1:/tmp/cvs-serv21521/src/freenet/node/rt
Modified Files:
StandardNodeEstimator.java
Log Message:
6320:
Set a proper timeout on QueryRejected messages from NewRequest - these account for the
vast majority of
Update of /cvsroot/freenet/freenet/src/freenet/client
In directory sc8-pr-cvs1:/tmp/cvs-serv23905/src/freenet/client
Modified Files:
AutoRequester.java
Log Message:
6321:
Logging.
Index: AutoRequester.java
===
RCS file:
Update of /cvsroot/freenet/freenet/src/freenet/node/rt
In directory sc8-pr-cvs1:/tmp/cvs-serv23905/src/freenet/node/rt
Modified Files:
NGRouting.java
Log Message:
6321:
Logging.
Index: NGRouting.java
===
RCS file:
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv23905/src/freenet
Modified Files:
Version.java
Log Message:
6321:
Logging.
Index: Version.java
===
RCS file:
I need a few details for a Freenet paper I'm working on at the moment...
Does Fred do probabilistic caching now? If so, what is the algorithm?
thanks,
theo
___
Devl mailing list
[EMAIL PROTECTED]
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv25218/src/freenet/node
Modified Files:
Node.java
Log Message:
6322: Make bandwidth limiting related QRing smoother.
Index: Node.java
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv25218/src/freenet
Modified Files:
Version.java
Log Message:
6322: Make bandwidth limiting related QRing smoother.
Index: Version.java
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The way I'm reading the code (admittedly, I'm not entirely familiar with
it), when we have a search eventually succeed after receiving one or more
QRs, only the time it took to succeed on the last node is fed to
globalEstimator. So, globalEstimator
One radical solution:
Remove the code to reject queries when the bandwidth limit is exceeded!
which returns us in the state 5010-5018 where the node has accepted
umpteen transfers, each going at snail speed. Making that prevalent
accross the network will be catastrophic.
Another possibility is
49 matches
Mail list logo
