#215: mixminion creates path shorter than 3 nodes
------------------------------+-------------------------
Reporter: simono | Owner: (none)
Type: defect | Status: closed
Priority: Low | Milestone:
Component: Mixminion-Client | Version: 0.0.7.1
Severity: Normal | Resolution: wontfix
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------------+-------------------------
Changes (by arma):
* status: new => closed
* resolution: None => wontfix
Old description:
> 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-0.0.7.1>mixminion.exe send -t
> smtp:sim...@ostengaard.dk -
> i data -P laforge,~2
> Mixminion version 0.0.7.1
> This software is for testing purposes only. Anonymity is not guaranteed.
> Dec 04 19:39:37.789 +0100 [INFO] Downloading directory from
> http://mixminion.net
> /directory/Directory.gz
> 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]
New description:
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-0.0.7.1>mixminion.exe send -t
smtp:sim...@ostengaard.dk -
i data -P laforge,~2
Mixminion version 0.0.7.1
This software is for testing purposes only. Anonymity is not guaranteed.
Dec 04 19:39:37.789 +0100 [INFO] Downloading directory from
http://mixminion.net
/directory/Directory.gz
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]
--
Comment:
mixminion is dead; long live mixminion
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/215#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
