|
Home > Archive > Anonymous Servers > June 2006 > Mixmaster 2.9.1 and Nyms
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Mixmaster 2.9.1 and Nyms
|
|
| TwistyCreek 2006-06-26, 1:12 pm |
| I'm experimenting with mixmaster 2.9.1 and nym creation and I have some
questions.
I use the mix menu n)ym item to create a nym. as part of the
process, mix creates a pgp key for the nym. I see that the secret key
ends up in nymsec.pgp, but where is the local copy of the public key
stored? How do I get mix to export these keys (public and private) so
that I can keep backup copies or move them into a gpg keyring?
I have a pre-existing nym from my windows days, since I can't use
JBN anymore and it's been long enough since the nym was used that it's
been deleted by now, How can I get mix to import the keys for that nym
so that I can use mix to issue a new nym-create message with the
existing keys?
Can I convince mix to use my gpg keyrings instead of nymsec.pgp and
whatever file holds the public keys? If I can, can I get mix to create
a create-nym request using a pre-existing key instead of creating one?
What is needed for mix to recognize and use newnym2 in nymserver
capstrings?
After checking several pingers, I find that so far only panta's stats
contain the info needed for mixmaster to be able to use the n)ym menu.
The problem is that While I know pantanym to be very reliable for nyms
with DSA keys, panta's own stats do not list pantanym niether does any
other stats page I've looked at yet.
If mix is just looking for '$remailer{"nymserver"}=' capstring entries,
can I get away with creating a text file with those entries for nymservers
and have my stats script tack it onto the beginnig of rlist.txt and have
it work? (I'm gonna try that after I send this, just now thought of it)
On a related note, I tried to compile 3.0b2 with NYMSUPPORT defined,
once in a header and once on the compiler command line (by adding it to
the Makefile) and both times the compile puked all over the place. Does
anyone know how to get nymsupport working correctly in 3.0b2 and are you
willing to share that information?
Thanks for any helps
| |
| TwistyCreek 2006-06-27, 1:12 am |
| TwistyCreek <anon@comments.header> wrote:
> If mix is just looking for '$remailer{"nymserver"}=' capstring entries,
> can I get away with creating a text file with those entries for nymservers
> and have my stats script tack it onto the beginnig of rlist.txt and have
> it work? (I'm gonna try that after I send this, just now thought of it)
addendum:
I tried it and found that adding nymserver capstrings to the beginning of
rlist.txt allows mix to use the n)ym menu regardless of stats source.
Related question:
Which of these nym servers is still operating and are these capstrings
correct?
$remailer{"at"} = "<config@nym.at> newnym2 pgp klen1024 DH/DSS";
$remailer{"blackhol"} = "<config@blackhole.riot.eu.org> newnym pgp klen1024";
$remailer{"cfnym"} = "<config@nym.cryptofortress.com> newnym pgp klen1024";
$remailer{"hod"} = "<config@hod.aarg.net> newnym2 pgp klen1024 DH/DSS TESTING";
$remailer{"nym"} = "<config@nym.alias.net> newnym pgp klen1024";
$remailer{"nymph"} = "<config@nymph.paranoici.org> newnym2 pgp klen1024 DH/DSS TESTING";
$remailer{"komite"} = "<config@nym.komite.net> newnym2 pgp klen1024 DH/DSS";
$remailer{"pantanym"} = "<config@nym.panta-rhei.eu.org> newnym newnym2 pgp klen1024";
Thanks again.
|
|
|
|
|