Re: Running Mixminion for Testing

[Florian Rüchel <florian.ruechel@xxxxxxxxxxxxxx>]

Hi Tom,

From what I could gather: Yes, a server would publish their descriptor
automatically to the directory but Nick hat to manually approve it
before it would be distributed. The thing that's not working is this
automatic publishing because the server-side is missing this class.

I'll drop Nick a mail, thank you.

Regards,
Florian

On 13.03.2015 13:39, Tom Ritter wrote:
> Hi Florian,
>
> Unfortunately I don't know the answer to this question.  You could try
> to email Nick and see if he is able to help.  For what it's worth, I
> think that mixminion doesn't/didn't support auto-publishing to the
> directory, and that new nodes needed to be added manually.
>
> -tom
>
> On 13 March 2015 at 05:39, Florian Rüchel
> <florian.ruechel@xxxxxxxxxxxxxx> wrote:
>> Hi,
>>
>> I have been able to figure most of the directory stuff out (i.e. the
>> download and publish URLs and the server itself). However, upon trying to
>> run by own instance, I get the following traceback:
>>
>> Traceback (most recent call last):
>>   File
>> "/home/javex/mnt/laptop/Studium/master-thesis/src/mixminion/minion-cgi/publish",
>> line 5, in &lt;module&gt;
>>     run()
>>   File
>> "/home/javex/mnt/laptop/.shadow/lib/python2.7/site-packages/mixminion/directory/DirCGI.py",
>> line 44, in run
>>     inbox = d.getInbox()
>>   File
>> "/home/javex/mnt/laptop/.shadow/lib/python2.7/site-packages/mixminion/directory/Directory.py",
>> line 139, in getInbox
>>     self.inbox = ServerInbox(self.inboxBase, self.getIDCache())
>>   File
>> "/home/javex/mnt/laptop/.shadow/lib/python2.7/site-packages/mixminion/directory/Directory.py",
>> line 111, in getIDCache
>>     self.cache = IDCache(self.cacheFile,self._setCacheMode)
>> NameError: global name 'IDCache' is not defined
>>
>> Some investigation showed that Nick removed the IDCache class in in 2005 (I
>> know, this is 10 years ago...):
>> commit 8ba0158c973f23e2e196a5673d0b58def83271b2
>> Author: Nick Mathewson <nickm@xxxxxxxxxxxxx>
>> Date:   Tue May 3 03:26:50 2005 +0000
>>
>>     Most of the back-end for the Great Mixminion Directory Rewrite.  Still
>> needs more testing and more glue code
>>
>> I am now unsure if I should just re-add the class or take my directory code
>> back to before this commit or whether there is something to fix here. I know
>> there is a directory running, but I don't know if the publishing part even
>> works today (I don't know what to send there and I get Error 500 if I call
>> it without a valid descriptor). If there is a directory server running
>> nowadays which version is it using?
>>
>> Regards and many thanks for your time,
>> Florian
>>
>>
>> On 18.02.2015 16:08, Tom Ritter wrote:
>>
>> It is hardcoded, and I don't think it's documented.  If you look at
>> [0] you can find where it pulls the directory from.  Read all the
>> relevant code to understand what's happening, make liberal use of
>> 'pdb.set_trace()', and you ought to be able to figure out how to run
>> your own.  When you do, we'd all appreciate a blog post about it and
>> you putting your edits in a github fork. =)
>>
>> -tom
>>
>> https://github.com/mixminion/mixminion/blob/master/lib/mixminion/ClientDirectory.py#L44
>>
>> On 18 February 2015 at 05:03, Florian Rüchel
>> <florian.ruechel@xxxxxxxxxxxxxx> wrote:
>>
>> Hi there,
>>
>> I want to perform research on Mixminion. Specifically, I am interested
>> to study whether Tor could offer a high-latency service similar to what
>> Mixminion offers. For this I'd like to run Mixminion in a development
>> mode where I run the whole network myself (using Shadow for the
>> simulation). That is, I want to run the directory servers, all other
>> servers and some clients.
>>
>> However, the docuemtnation & configuration file do not state how to
>> operate such a network by myself. Is there a hardcoded part somewhere
>> for the directory servers?
>>
>> Any help would be greatly appreciated.
>>
>> Regards,
>> Florian
>>
>>