Commit 4d2d9719 authored by putro's avatar putro

initial release

parent b2f0487c
This diff is collapsed.
THIS SOFWARE IS BETA
nymhelper is a script that helps in creating and using a nym
nymhelper has been developed starting from nymgrind (http://www.banana.mixmin.net/svn/nymgrind/)
REQUIREMENTS:
gnupg (http://www.gnupg.org)
mixmaster (http://mixmaster.sourceforge.net
INSTALLATION:
simply copy the script in a directory
gnupg.py, random_binary_data and test_gnupg.py come from the python-gnupg module (http://code.google.com/p/python-gnupg)
you can keep this files locally in the same dir of the nymhelper.py script,
or you can install the python-gnupg on your system and delete these files from the script directory.
USAGE:
first, edit file config.ini and change settings where required.
There are different config section:
"options" - miscellaneous config options
"1" - first (and required) nym data
"2" - second (optional) nym data
you can add other sections for each nym you have
for every nym follow the same syntax of section "1", pwd can be left empy (unless you keep the config file encrypted you should NEVER write password here, and anyway writing password is always a bad idea).
to start simply type ./nymhelper.py and follow the on screen menu:
MENU:
1 to choose/select active nym
select the active nym (if you have more than one defined in config.ini)
2 to write a message (as active nym)
write a message and prepare it to be sent to send@nym-server-address
the message is saved in file defined in config.py (message-out).
You will be asked to choose a subject and the text
3 to send the message created via local mixmaster
send the message you prepared through a local mixmaster to send|config@nym-server-address
You will be asked to choose a recipient (default should be fine), a subject (it's the subject
of the encrypted message that the nym server will receive, not the subject of the message that
will be received by the recipient), and a remailer chain (used to send the message to the nym server).
4 to download fresh remailer stats
download fresh stats from pinger defined in config.py
5 to choose remailer chain,
this is optional, you will prompted for remailer chain if needed
6 to create or update a nym
create or update (i.e. with a new reply block) a nym (the nym has to be already defined in config.ini and selected with menu choice "1")
you will be asked for a remailer chain if not yet choosed, this will be the chain of the reply-block for your nym.
7 to delete a nym
to be implemented
8 to create a new secret key
to create a gnupg RSA key in your personal gnupg keyring (to be improved)
9 to delete a secret key from your personal keyring
10 to send msg via smtp
same as menu "3", but messages are sent through a local or remote SMTP server.
Useful just for test, messages are not anonymized.
q to quit
it's possible to specify a different config file (default config.ini)
nymhelper.py -C configfile
it's possible to send a message from a certain nym directly via command line with this syntax:
nymhelper.py -n 2 -s "subject" -r recipient -t "text of the message" -c "remailer1,remailer2"
-n is the nym number in config file
-s subject
-r recipient
-t text of the message
-c remailer chain to be used to send the message (through your local mixmaster client)
for nyms rarely used, you can put this on crontab to keep the nym alive (nyms are disabled if not used),
or to quickly check if the nym is working well.
for help type:
nymhelper.py -h
NOTES:
nyms pointing to newsgroups as final destination will have the subject (defined in config.ini)
encrypted in hsub format,
to recognize them you have to use a software like news2mail (http://www.is-not-my.name/news2mail/)
or aam2mail (http://www.banana.mixmin.net/aam2mail.tar.gz)
TODO:
possibility to send a message from a nym encrypting it with the recipient gpg key
(with a check that a key for that address exists)
encrypt key
multiple reply block
create dsa keys
choice between remailer post or explicit mail2news.
pseudorandom subject using a dict
TROUBLESHOOTING:
be sure to have the right keys in your keyring
TO BE VERIFIED: ** position...
[options]
# define the directory that contains the keyrings you want to use
keyring = /home/user/.gnupg
#define the location of the mixmaster binary
mixmaster = /usr/bin/mixmaster
# subject to be converted to hsub for nyms pointing to newsgroups
subj = mysubject
#latency to be applied for each remailer used
latency = +1:00r
# set parameters for remailer stats
# see stats.mixmin.net for a list of pingers
stats_url = http://remailer.paranoici.org/stats/
stats_rlist = rlist2.txt
stats_mlist = mlist2.txt
keys_file = pgp-all.asc
remailer_min_uptime = 90
# where to save messages to be sent
message_out = /tmp/message-out.txt
# news config
mail_to_news = mail2news@m2n.mixmin.net
# Mail config, useful just for tests, otherwise ignore it
smtp_sender = my@address.org
smtp_password = 123
smtp_server = localhost
smtp_port = 25
#smtp_sender = 'my@address.org'
#smtp_password = 'password_here'
#smtp_server = 'smtp.autistici.org'
#smtp_port = '587'
logfile = /tmp/nymhelper.log
# first nym data (mandatory, and the section has to be named [1])
[1]
id = 1
name = test1
server = nymph.paranoici.org
pwd =
final_dest = alt.anonymous.messages
acksend = 1
signsend = 0
cryptrecv = 1
# second nym data (optional)
[2]
id = 2
name = test2
server = nymph.paranoici.org
pwd = test2
final_dest = myself@my.address.org
acksend = 1
signsend = 0
cryptrecv = 1
# you can add other sections, one for every nym you have, just follow the syntax of the previous
# pwd can be left empty, you will be prompted for it
# in the above example, the first nym will be test1@nymph.paranoici.org, and will point to newsgroup alt.anonymous.messages, pwd is not stored here.
Copyright (c) 2008-2013 by Vinay Sajip.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
* The name(s) of the copyright holder(s) may not be used to endorse or
promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S) "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment