Opened 14 years ago

Closed 6 months ago

#215 closed defect (wontfix)

mixminion creates path shorter than 3 nodes

Reported by: simono Owned by:
Priority: Low Milestone:
Component: Mixminion-Client Version:
Severity: Normal Keywords:
Cc: simono Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

I was testing the new 0.0.8alpha1 server on laforge. To my
understanding a message should pass at least three nodes to ensure my
anonymity. I wanted to test the laforge node, so I sent the messages
with -P laforge,~2 ( send the message through laforge and about two
other nodes). As you can see in the output below the mixminion client
selected to send my message through laforge and use laforge a a swap
point. So the message will only go through 1 node. In my opinion the
~<number> option should calculate a minimum number of nodes so a
message will go through at least three nodes. I have verified the bug on windows and FreeBSD, and I assume that the bug exists on all platforms.

D:\mixminion\Mixminion->mixminion.exe send -t -
i data -P laforge,~2
Mixminion version
This software is for testing purposes only. Anonymity is not guaranteed.
Dec 04 19:39:37.789 +0100 [INFO] Downloading directory from
Dec 04 19:39:44.579 +0100 [INFO] Validating directory
Dec 04 19:39:45.139 +0100 [WARN] This software is newer than any version on the
recommended list.
Dec 04 19:39:45.139 +0100 [INFO] Generating payload(s)...
Dec 04 19:39:45.149 +0100 [INFO] Selected path is laforge:laforge
Dec 04 19:39:45.229 +0100 [INFO] Packet queued
Dec 04 19:39:45.229 +0100 [INFO] Connecting...
Dec 04 19:39:47.743 +0100 [INFO] ... 1 sent

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 14 years ago by nickm

See response to email at

I'm thinking this is not-a-bug on the ~2-can-be-one front. If you want at least 3 nodes, you
should presumably ask for at least 3 nodes, right?

I'm leaving this bug open because of the laforge:laforge problem and the ~0 => 1 problem.

comment:2 Changed 19 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:3 Changed 6 months ago by arma

Description: modified (diff)
Resolution: Nonewontfix
Status: newclosed

mixminion is dead; long live mixminion

Note: See TracTickets for help on using tickets.