Re: [tor-dev] Experimenting with private tor setup

[teor <teor2345@xxxxxxxxx>]

Date: Wed, 22 Apr 2015 23:14:07 -0400

From: CJ Ess <zxcvbn4038@xxxxxxxxx>

â

I think that just leaves a couple questions for now:

- I know the directory authority's certificate needs to be
renewed periodically (looks like 12 months default). Since it asked for a
password that is something I need to do manually then send a HUP, correct?
Later on I'll try to hack generating a cert with days or hours of time just
to see what happens, but would like to know what the correct way to handle
it is.

Yes, you will need to generate new authority certificates when they expire.

Look at "man tor-gencert" for more details - you may be able to enter a blank password, or generate a new certificate and send a HUP on a cron job. Alternately, look at the chutney source code for how it's done there. (This isn't my area of expertise.)

- All of my routers have done the bandwidth tests, but I see this warning
on the DAs with each vote:

Apr 22 22:39:41.000 [warn] Consensus with empty bandwidth: G=0 M=5 E=0
D=243 T=248

Is this something that will fill out as the uptime of the instances
increase? Or is this something I should look into?

I think you need to run a separate bandwidth authority to get bandwidths in your consensus. This probably isn't necessary for your purposes, as your instances are all on the same host.

It's also not something that chutney does, and chutney networks function fine.

teor

teor2345 at gmail dot com
pgp 0xABFED1AC
https://gist.github.com/teor2345/d033b8ce0a99adbc89c5

teor at blah dot im
OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7

_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev