|
Home > Archive > Anonymous Servers > December 2005 > Attn Panta-Admin Panta-Reliable-Mod-2005-11-26
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Attn Panta-Admin Panta-Reliable-Mod-2005-11-26
|
|
| Thrasher Remailer 2005-12-08, 2:46 am |
| A while back I posted about an anomaly with recent versions of
Panta's Reliable mod. The 'make stats' function would not
generate stats every two hours even though 'Minimum Ping Time'
was set to 2hours. Instead it would take anywhere from three to
eight hours regardless of my settings.
Recently I have been doing an experiment with a new installation
of Reliable and a fresh install of the latest Panta Mod.
I kept track of how often pings were generated. 'minimum ping
time' is set to 2 hours. I ran for a while with no panta mods
enabled other than the defaults. Then one by one I enabled each
one and waited to make sure 'make stats' was performing
correctly. Nothing caused any change untill I changed 'Minimum
Pool Size' from the default zero to 45.
Immediately the anomaly appeared, pings that were being
generated every two hours suddenly took over seven hours. When
'Minimum Pool Size' is set to anything other than zero, stats
generation timing is affected.
Would you please look into this? I really appreciate the
'Minimum Pool Size' function, but I cannot use it if it's going
to affect 'make stats' like this.
Thanks for your time.
Here is some trials data that should be possible to duplicate:
Dec 01... Installed original RProcess Reliable 1.05 on Win98SE
installed Panta-Reliable-Mod-2005-11-26
Started operation with default settings.
1:43:26 AM
3:46:16 AM
5:47:55 AM
09:55am... enabled adminkey
0958am... manual makestats.. leave on auto
10:01:59 AM
12:04:07 PM
105pm... auto makestats off
527pm... manual makestats, auto on...
5:29:58 PM
7:31:37 PM
929pm... automakestats off
12:36am... manual makestats, auto left on
12:38:51 AM
2:42:09 AM
4:44:52 AM
6:46:59 AM
03:52pm 12/2/05 enable dest block ... auto makestats on
...(some sessions scrolled off)
3:58:08 PM
6:00:05 PM
8:01:30 PM
10:03:21 PM
12:05:32 AM
2:07:21 AM
4:08:56 AM
6:10:25 AM
8:12:37 AM
10:14:10 AM
11:12am 12/03... enable delete non-remailer
12:16:35 PM
2:18:07 PM
4:19:57 PM
6:21:36 PM
6:30pm(?)12/03...auto makestats off
22:02 12/03... manual auto makestats, left on
10:07:52 PM
10:24am 12/04... restart...
...recover from system crash... down 5 hours or so
10:31:05 AM
10:52am 12/04... mail2news enabled, mail2news log enabled
12:32:25 PM
2:34:39 PM
4:36:09 PM
6:37:31 PM
8:39:18 PM
10:17pm 12/04... auto makestats off
...secure random number enabled
12:06am 12/05... stats refresh time changed to 4 hours, auto
makestats on
12:21:01 AM
2:22:44 AM
4:25:04 AM
6:27:38 AM
7:34am 12/05... auto makestats off
9:31pm 12/05... Dest-Block blocks From enabled, auto makestats
on
9:35:05 PM
11:37:54 PM
1:39:55 AM
3:41:39 AM
5:45:47 AM
6:35am 12/06...auto makestats off
8:34am 12/06 Minimum Pool Size = 45, auto makestats on
8:37:44 AM
3:59:59 PM
about 5pm...auto makestats off
12:31am 12/07...auto makestats on
12:39:47 AM
7:21am 12/07...Minimum Pool Size = zero, auto makestats on
7:27:45 AM
9:30:04 AM
11:32:28 AM
01:12pm 12/07...auto makestats off
theory: minimum pool size is affecting frequency of auto
makestats
when it was set to 45, makestats took roughly 7 1/2 hrs
between.
01:17pm 12/07...Minimum pool size = 20, auto makestats on
1:34:56 PM
5:56:07 PM
9:54:45 PM
~~~~~~~~~~~~~~~~~~~~~
This message was posted via one or more anonymous remailing services.
The original sender is unknown. Any address shown in the From header
is unverified. You need a valid hashcash token to post to groups other
than alt.test and alt.anonymous.messages. Visit www.panta-rhei.dyndns.org
for abuse and hashcash info.
| |
| panta-admin 2005-12-08, 7:46 am |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi !
>I kept track of how often pings were generated. 'minimum ping
>time' is set to 2 hours. I ran for a while with no panta mods
>enabled other than the defaults. Then one by one I enabled each
>one and waited to make sure 'make stats' was performing
>correctly. Nothing caused any change untill I changed 'Minimum
>Pool Size' from the default zero to 45.
>
>Immediately the anomaly appeared, pings that were being
>generated every two hours suddenly took over seven hours. When
>'Minimum Pool Size' is set to anything other than zero, stats
>generation timing is affected.
>
>Would you please look into this? I really appreciate the
>'Minimum Pool Size' function, but I cannot use it if it's going
>to affect 'make stats' like this.
Sure, I will have a look at it as soon as I have time.
It will not be before Christmas though.
Thanks for analyzing the problem.
Cheers,
panta-admin
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQA/AwUBQ5gNQdcrLUqmoDLIEQJE/QCgwOFWEzcK5+ZY/8ae6a/Wsxb02c0AoNRF
N6h2Slvnx5xkq+PYrRvbYjwq
=iAH/
-----END PGP SIGNATURE-----
~~~~~~~~~~~~~~~~~~~~~
This message was posted via one or more anonymous remailing services.
The original sender is unknown. Any address shown in the From header
is unverified. You need a valid hashcash token to post to groups other
than alt.test and alt.anonymous.messages. Visit www.panta-rhei.dyndns.org
for abuse and hashcash info.
| |
| BiKiKii Admin 2005-12-08, 7:46 am |
| -----BEGIN PGP SIGNED MESSAGE-----
On 8 Dec 2005, Thrasher Remailer wrote:
>A while back I posted about an anomaly with recent versions of
>Panta's Reliable mod. The 'make stats' function would not
>generate stats every two hours even though 'Minimum Ping Time'
>was set to 2hours. Instead it would take anywhere from three to
>eight hours regardless of my settings.
>
>Recently I have been doing an experiment with a new installation
>of Reliable and a fresh install of the latest Panta Mod.
>
>I kept track of how often pings were generated. 'minimum ping
>time' is set to 2 hours. I ran for a while with no panta mods
>enabled other than the defaults. Then one by one I enabled each
>one and waited to make sure 'make stats' was performing
>correctly. Nothing caused any change untill I changed 'Minimum
>Pool Size' from the default zero to 45.
>
>Immediately the anomaly appeared, pings that were being
>generated every two hours suddenly took over seven hours. When
>'Minimum Pool Size' is set to anything other than zero, stats
>generation timing is affected.
>
Hello,
Did you not notice that NO messages were being sent?
Your system did never exceed the pool threshold.
>Would you please look into this? I really appreciate the
>'Minimum Pool Size' function, but I cannot use it if it's going
>to affect 'make stats' like this.
>
Are you running a Remailer which would have benefit of the 'Minimum Pool Size' function?
Seems as if your system would not. The function is working as was designed, for a public Remailer.
Reliable MUST do a Send, flush the pool, just prior to making stats.
(See the first Note under "Make Stats Session" in the Reliable Operator's Manual.)
Additionally the pool threshold should not exceed the total number of pings generated
(else their sending will be delayed).
Ciao!
BiKiKii
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBQ5d3gfRwi/ QFFzi5AQEtXwf+LT6W+L0igeJauoE6PVHdQN3W3R
Ugl9H5
15NxDrstDLI2Y5D0EmtgYtQndqJxw3iwQCh5wom/fZtExUEf/ppYkVcVkjTXW0h3
01ccifaE8+3AWVygF1d8vLq330tXoIp+DNvL4Od4
mSwhtiEdiR4CDLMg3gKILP4R
bKVADpHl1osKrG07Y1JS0VhBBX/y1GxHwksl38ZkdxDcV/nfhCJEeAV5DLYjQ4Pf
LYmoL3wapK4TGmRcOkZJnAqkFEEI5UvuQnzAatpe
Wz0bu8llpabcmRrdCNkWSY0x
GAYFNxD94uGSsJr9I0y8rw6BD1IGvL7/8JssATtW68bsoEIydk9joA==
=JERN
-----END PGP SIGNATURE-----
| |
| George Orwell 2005-12-08, 5:47 pm |
| > Hello,
>
> Did you not notice that NO messages were being sent?
> Your system did never exceed the pool threshold.
>
>
> Are you running a Remailer which would have benefit of the 'Minimum Pool Size' function?
> Seems as if your system would not. The function is working as was designed, for a public Remailer.
His remailer is public, it is Eelbash. He gets a very low number of
messages passing through though which may explain why he takes a while
to exceed the pool threshold.
Does setting the minimum pool size to 0 like he has to do hurt the
anonymity of the system?
| |
| BiKiKii Admin 2005-12-08, 5:47 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
On Thu, 8 Dec 2005, George Orwell wrote:
>
>His remailer is public, it is Eelbash. He gets a very low number of
>messages passing through though which may explain why he takes a while
>to exceed the pool threshold.
>
>Does setting the minimum pool size to 0 like he has to do hurt the
>anonymity of the system?
>
The motivation for the original modification:
Background:
Reliable is based on the Stop-and-Go (SG Mix) mix.
It has been shown that, under low traffic conditions, the
anonymity provided by the SG Mix decreases to very low value.
In a effort to thwart a passive attacker, we implement a
pool mix similar to that employed by Mixmaster.
Reference:
"Comparison between two practical mix designs" (ESORICS 2004)
C.Diaz. L.Sassaman E.Dewitte
"Minimum Pool Size" function <http://xthost.info/bikikii/docs/modify/BA-005.txt>
Find the referenced publication at: <http://www.freehaven.net/anonbib/>
Ciao!
BiKiKii
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBQ5d3gfRwi/QFFzi5AQF4pgf/SsbvVgC4Nxtt/t9B7qd4TiOXPg3cgU0p
QGrFs7X/ LIyxMiPDSnZSkCxP0nj8Knuw7Em6dMJ7gc7xdBmi
TPfgZWZNEroiQrVv
ZJ5nLd9S2YGoGhW5eqhDqFRB3//ZQrUV09tHLg15RQBAF12BV4mdU45AGLsRoEWX
WxAD1dSgYy6MuVmfUCcfb8cs2aHGa4QL72OpnUtO
XPyp7EFk959cScDDrwAwGWsi
N3qXumHIGl0SXYb/ XJHA3egNh72WQ3skz6Gtd2yxpHDrfUYTybsXo97P
jVeUC6qt
RvnLrLz+Nu/MnWlwfpeOELac3eVuWrisXq5bJJ5TQ2OOX//0S2tiEg==
=2/EL
-----END PGP SIGNATURE-----
| |
| BiKiKii Admin 2005-12-08, 8:46 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
On Thu, 8 Dec 2005, George Orwell wrote:
Addtional comments after re-reading post:
>His remailer is public, it is Eelbash. He gets a very low number of
>messages passing through though which may explain why he takes a while
>to exceed the pool threshold.
>
Perhaps, initial impression is/was of private user with desire of own pinger.
>Does setting the minimum pool size to 0 like he has to do hurt the
>anonymity of the system?
>
Was this a "set-up" query? Matches motivation for modification so well.
Ciao!
BiKiKii
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBQ5d3gfRwi/QFFzi5AQHPrAf/RV1QOYAwWjylBF7Df/ua9visFYu3Imsb
p1LstPTo2x/ 3AW7B37+G9MmXPsa+eGzkhf7JJ8h17UY0IWxmo+f
mNhWZuIMSj9cn
e01GtUsn3OitWaEmSsdDz5r2SE9k1+bTV6lhf5GB
pfJ0eTiNddHvTMWuhBlkRoVX
3wqudWaIAp9VT0uYO0ECg5tGXbdWe8BVN8CORFKj
KAPZhLxVM0W/mAyMhVPVwz7C
+aKr2IN51oWEbfAdsRMe+OiIhY1uCzLQd5DoAmWy
RT5xOBQxUFJ+lp0EUP8Cm/Ab
NBktqp96T6O7XY3GmBbqeNGtOqeT2xWWjoFe0/zwhMPqCAaisKIHKw==
=g58r
-----END PGP SIGNATURE-----
| |
| Thrasher Remailer 2005-12-09, 2:47 am |
| In article < 4992ac3280ac24c518e01f66f0033ee5@mixmast
er.it>
George Orwell <nobody@mixmaster.it> wrote:
>
>
> His remailer is public, it is Eelbash. He gets a very low number of
I am not now, nor have I ever been Eelbash. I'm just a nobody
trying to generate my own stats and learn a remailer from the
inside with an eye to opening one public someday If I can get
more cpu and bandwidth to do it with.
Eelbash is listed in my reliable's "Random Exclusion" entries
and it is barred from Random or Auto selection in both JBN and
QS.
~~~~~~~~~~~~~~~~~~~~~
This message was posted via one or more anonymous remailing services.
The original sender is unknown. Any address shown in the From header
is unverified. You need a valid hashcash token to post to groups other
than alt.test and alt.anonymous.messages. Visit www.panta-rhei.dyndns.org
for abuse and hashcash info.
| |
| Thrasher Remailer 2005-12-09, 7:47 am |
| In article <E6F79A7577@bikikii.ath.cx>
BiKiKii Admin <Use-Author-Supplied-Address-Header@[127.1]> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On 8 Dec 2005, Thrasher Remailer wrote:
>
> Hello,
>
> Did you not notice that NO messages were being sent?
> Your system did never exceed the pool threshold.
Messages were being sent: 'Messages Received Last Week:
5830'. It's not a lot, I know, but my remailer is currently in
private testing use only. My main use for it now is to have
private stats generation, I also run a few batch files to
generate dummy traffic for testing purposes. If I had a little
more horsepower on my home network, I'd open it up to the
public, but as it is I cannot do so at this time.
>
> Are you running a Remailer which would have benefit of the 'Minimum Pool Size' function?
> Seems as if your system would not. The function is working as was designed, for a public Remailer.
> Reliable MUST do a Send, flush the pool, just prior to making stats.
I know, It happens all the time. for example, when I set
"Minimum Pool Size" to 45 there was 64 messages in the pool, It
had been nearly 3 hours since the last "Make Stats Session"
because of my disabling it temporarily (clicking 'make stats' to
the "out" position), I made the change to "Minimum Pool Size"
and then clicked "Make stats".
Reliable DID do a send where 47 messages were sent. Then, when
it should have started the "make stats", It simply sat there.
It sat there in fact for a few minutes before creating pings.
It then sat there from 8:37:44 AM receiving, processing, and
sending messages untill 3:59:59 PM when it finally started
generating pings again.
> (See the first Note under "Make Stats Session" in the Reliable Operator's Manual.)
> Additionally the pool threshold should not exceed the total number of pings generated
> (else their sending will be delayed).
Pool size was set to 45 on one test, and 20 on another, pings
create 63 messages per batch and in addition to this there are
the batch files I run to generate dummy traffic. My problem is
not with sending messages, but rather how often the "Make Stats
Session" occurs. I have "Minimum Ping Time" set to 2 hours and
that is how often I want the "Make Stats Session" to generate
pings. What I do not see is why setting "Minimum Pool Size" to
a non-zero value would cause the "Make Stats Session" to take
longer than 2 hours between runs.
~~~~~~~~~~~~~~~~~~~~~
This message was posted via one or more anonymous remailing services.
The original sender is unknown. Any address shown in the From header
is unverified. You need a valid hashcash token to post to groups other
than alt.test and alt.anonymous.messages. Visit www.panta-rhei.dyndns.org
for abuse and hashcash info.
| |
| BiKiKii Admin 2005-12-09, 5:49 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
On 9 Dec 2005, Thrasher Remailer wrote:
>In article <E6F79A7577@bikikii.ath.cx> BiKiKii Admin wrote:
>
>Messages were being sent: 'Messages Received Last Week:
>5830'. It's not a lot, I know, but my remailer is currently in
>private testing use only. My main use for it now is to have
>private stats generation, I also run a few batch files to
>generate dummy traffic for testing purposes. If I had a little
>more horsepower on my home network, I'd open it up to the
>public, but as it is I cannot do so at this time.
>
>
>I know, It happens all the time. for example, when I set
>"Minimum Pool Size" to 45 there was 64 messages in the pool, It
>had been nearly 3 hours since the last "Make Stats Session"
>because of my disabling it temporarily (clicking 'make stats' to
>the "out" position), I made the change to "Minimum Pool Size"
>and then clicked "Make stats".
>
>Reliable DID do a send where 47 messages were sent. Then, when
>it should have started the "make stats", It simply sat there.
>It sat there in fact for a few minutes before creating pings.
>It then sat there from 8:37:44 AM receiving, processing, and
>sending messages untill 3:59:59 PM when it finally started
>generating pings again.
>
>
>Pool size was set to 45 on one test, and 20 on another, pings
>create 63 messages per batch and in addition to this there are
>the batch files I run to generate dummy traffic. My problem is
>not with sending messages, but rather how often the "Make Stats
>Session" occurs. I have "Minimum Ping Time" set to 2 hours and
>that is how often I want the "Make Stats Session" to generate
>pings. What I do not see is why setting "Minimum Pool Size" to
>a non-zero value would cause the "Make Stats Session" to take
>longer than 2 hours between runs.
>
Hello,
Looked at Panta's code, much the same as originally published "BA-005".
Found that published "BA-005" is NOT the same as code in BiKiKii source tree.
Clue - did not see code that yields verbose output:
HH:MM No Messages sent. MinPoolSize not exceeded
Total [###] / MinPoolSize [##] / Ready [##]
Some unpublished revisions were made and implemented September 2004.
Inclusion of the line with Sess(0, 1) = Sess(0, 1) .... : SessUp (0)
may be causing the condition.
"BA-005" republished <http://xthost.info/bikikii/docs/modify/BA-005.txt>
Oh well... apologies.
Ciao!
BiKiKii
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBQ5jJAfRwi/QFFzi5AQHVegf/YvIaMXcavUx6/Bkn8hDp6VoDxBT/ow8Q
TSxN5pQEeyCiOdV238r05+nC+wVRZBy3oDy1hH/+m2biLC8TVMeos3hT5QkQxh6w
HEbn3r/ lE7zKL7tMSxL7b7TFZqDLkAkGDyXJdy5JPEy984u
hJSjc1w0GpPvfEetM
acihUJRG+6pfsE7beSjTeLf1vYBktnI6Ze4upOLP
nMe0adlS1SKwmOdo9AHeMi3b
e8hO/0C1abYTBMibp/ txbe93pfrQYMznJUfuJDD4fuhIwTbmtZFsgTLPlX
Z4IXOO
rHdO3YS9ep2xRE1lgXIeaxPae+1mG0N1hMFYd2fu
LKC16uPyRZxNlw==
=/KGq
-----END PGP SIGNATURE-----
|
|
|
|
|