| 351 |
being chosen as random hops. |
being chosen as random hops. |
| 352 |
Have stats on intermediate vs. final hop count |
Have stats on intermediate vs. final hop count |
| 353 |
(closes: #649900). |
(closes: #649900). |
| 354 |
Handle a pool we cannot read correctly: don't close |
|
| 355 |
|
2003-05-03 3.0a4 Handle a pool we cannot read correctly: don't close |
| 356 |
the NULL dir handle (segfaults on *bsd). We also |
the NULL dir handle (segfaults on *bsd). We also |
| 357 |
print a warning in that case now. |
print a warning in that case now. |
| 358 |
|
Add max capability for Type I. |
|
2003-02-15 Add max capability for Type I. |
|
| 359 |
Make sure DH/DSA param file is actually opened before |
Make sure DH/DSA param file is actually opened before |
| 360 |
writing to it. Fixes a segfault in case it is not. |
writing to it. Fixes a segfault in case it is not. |
| 361 |
Fix a problem in blockrequest() where a buffer |
Fix a problem in blockrequest() where a buffer |
| 386 |
time mixmaster is run unless CLIENTAUTOFLUSH is |
time mixmaster is run unless CLIENTAUTOFLUSH is |
| 387 |
set to n. (closes: #676794: Rate implementation |
set to n. (closes: #676794: Rate implementation |
| 388 |
doubled) |
doubled) |
| 389 |
Found that weird bug that weird bug that sometimes |
Found that weird bug that sometimes led to "Unknown |
| 390 |
led to "Unknown remailer version!" errors: In |
remailer version!" errors: In chain_randfinal() we |
| 391 |
chain_randfinal() we selected a random value |
selected a random value between 0 and maxrem instead |
| 392 |
between 0 and maxrem instead of 0 and maxrem - 1. |
of 0 and maxrem - 1. Mixmaster now uses |
| 393 |
Mixmaster now uses broken-chain info from stats. I |
broken-chain info from stats. I hope this doesn't |
| 394 |
hope this doesn't break any Nym functionality. |
break any Nym functionality. |
| 395 |
Warn if remailer stats are older than a day. |
Warn if remailer stats are older than a day. |
| 396 |
|
|
| 397 |
|
2003-05-08 3.0a5 Experimental feature: --redirect -l <chain>. |
| 398 |
|
If you have a mixmaster message with a |
| 399 |
|
chain starting with hop1 (you cannot know any |
| 400 |
|
more because it already is encrypted) then |
| 401 |
|
mix --redirect -l foo,bar < file |
| 402 |
|
redirect the message so the chain is actually |
| 403 |
|
foo,bar,hop1,... and places it in your pool. |
| 404 |
|
If the total number of hops (which cannot be |
| 405 |
|
known) exceeds 20 the message is damanged |
| 406 |
|
and will fail at the 20th node. |
| 407 |
|
|
| 408 |
|
|
| 409 |
|
2003-06-27 3.0a6 Don't send messages to ourselves via the mailsystem |
| 410 |
|
but instead place them in the pool as incoming |
| 411 |
|
messages so that they will get processed with the |
| 412 |
|
next pool run. |
| 413 |
|
Hopefully fix a bug with pool stats. |
| 414 |
|
|
| 415 |
|
2003-06-29 3.0a7 Two minor fixes for bugs introduced in 3.0a6 and |
| 416 |
|
3.0a4. |
| 417 |
|
|
| 418 |
|
2003-06-30 3.0a8 Minor stats fix. The date in remailer-stats was |
| 419 |
|
sometimes wrong. |