| 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 destinationblock() where a buffer |
Fix a problem in blockrequest() where a buffer |
| 362 |
could have been used after it was free()d which |
could have been used after it was free()d which |
| 363 |
resulted in segfaults. |
resulted in segfaults. |
| 364 |
Install script tweaks |
Install script tweaks |
| 365 |
|
Check that feedback buffer is not null before |
| 366 |
|
operating on it in chain_select(). |
| 367 |
|
Closes #631353, thanks Sami Farin. |
| 368 |
|
In order to serve help files in different languages |
| 369 |
|
we need a way to reply to requests like |
| 370 |
|
remailer-help-it. In order to not have to modify |
| 371 |
|
the code for each and every new ressource, |
| 372 |
|
Mixmaster now sends the file |
| 373 |
|
requests/remailer-<something> to |
| 374 |
|
remailer-<something> requests. |
| 375 |
|
remailer-{help,key, stats,conf,adminkey} still are |
| 376 |
|
special cases tho. |
| 377 |
|
In the curses interface chain selection it was not |
| 378 |
|
possible to select a random last hop with a usenet |
| 379 |
|
post message. Fixed (closes: #719165). |
| 380 |
|
If remix was enabled and we had a Type-I Anon-Post-To |
| 381 |
|
request we accidently randhoped it via the |
| 382 |
|
configured default remailing chain (default: |
| 383 |
|
*,*,*,*). |
| 384 |
|
Fixed (closes: #729494). |
| 385 |
|
In client mode (REMAIL n) the pool is flushed every |
| 386 |
|
time mixmaster is run unless CLIENTAUTOFLUSH is |
| 387 |
|
set to n. (closes: #676794: Rate implementation |
| 388 |
|
doubled) |
| 389 |
|
Found that weird bug that weird bug that sometimes |
| 390 |
|
led to "Unknown remailer version!" errors: In |
| 391 |
|
chain_randfinal() we selected a random value |
| 392 |
|
between 0 and maxrem instead of 0 and maxrem - 1. |
| 393 |
|
Mixmaster now uses broken-chain info from stats. I |
| 394 |
|
hope this doesn't break any Nym functionality. |
| 395 |
|
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. |