Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2018-12-04T19:32:34Zhttps://gitlab.torproject.org/legacy/trac/-/issues/505mixminion flush: option -n not recognized2018-12-04T19:32:34ZTracmixminion flush: option -n not recognizedminor issue: with "mixminion flush" the short name "-n <n>" does
not seem to work instead of "--count=<n>".
##### Beginn
$ mixminion flush -n 1
Mixminion version 0.0.8alpha3
This software is for testing purposes only. Anonymity is not...minor issue: with "mixminion flush" the short name "-n <n>" does
not seem to work instead of "--count=<n>".
##### Beginn
$ mixminion flush -n 1
Mixminion version 0.0.8alpha3
This software is for testing purposes only. Anonymity is not guaranteed.
option -n not recognized
Usage: mixminion flush [options] [servername] ...
-h, --help Print this usage message and exit.
-v, --verbose Display extra debugging messages.
-f <file>, --config=<file> Use a configuration file other than ~/.mixminionrc
(You can also use MIXMINIONRC=FILE)
-n <n>, --count=<n> Send no more than <n> packets from the queue.
EXAMPLES:
Try to send all currently queued packets.
mixminion flush
Try to send at most 10 currently queued packets, chosen at random.
mixminion flush -n 10
Try to send all currently queued packets for the server named 'Example1', or
for the server whose hostname is 'minion.example.com'.
mixminion flush Example1 minion.example.com
$ mixminion flush --count=1
Mixminion version 0.0.8alpha3
This software is for testing purposes only. Anonymity is not guaranteed.
Sep 18 10:20:49.455 +0200 [INFO] Flushing packet queue
Sep 18 10:20:49.502 +0200 [INFO] Found 1 pending packets
Sep 18 10:20:49.588 +0200 [INFO] Sending 1 packets to server at [...]...
Sep 18 10:20:49.590 +0200 [INFO] Connecting...
Sep 18 10:20:50.032 +0200 [INFO] ... 1 sent
Sep 18 10:20:50.633 +0200 [INFO] Queue flushed
##### Ende
BTW: there's no option to report for version 0.0.8alpha3
[Automatically added by flyspray2trac: Operating System: Linux]
**Trac**:
**Username**: tcrhttps://gitlab.torproject.org/legacy/trac/-/issues/502Encrypt identity keys2019-06-17T19:06:58ZTracEncrypt identity keysAt the moment, each node's "identity.key" is not protected at
all, so a server seizure might easily compromise it.
For my own node I've toyed around a bit with encrypting (gnupg)
the key, asking for the passphrase at startup and only dec...At the moment, each node's "identity.key" is not protected at
all, so a server seizure might easily compromise it.
For my own node I've toyed around a bit with encrypting (gnupg)
the key, asking for the passphrase at startup and only decrypting
to a random-key-encrypted temporary storage (cryptfs). In this
setup the key would never be lying around unencrypted.
I suppose, the SURB keyring is already encrypted, so maybe some
kind of built-in identity key encryption might be feasible with
not too much additional effort.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcrhttps://gitlab.torproject.org/legacy/trac/-/issues/498Proof-of-work for exit remailers2019-06-17T19:06:58ZTracProof-of-work for exit remailersTo prevent spam and/or floods originating from the mixminion network it might be
sensible to require (adjustable by the exit remailer operator) some proof-of-work,
e.g. hashcash before relaying the message. Dummy messages would not be af...To prevent spam and/or floods originating from the mixminion network it might be
sensible to require (adjustable by the exit remailer operator) some proof-of-work,
e.g. hashcash before relaying the message. Dummy messages would not be affected
because those don't leave the network anyway.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcrhttps://gitlab.torproject.org/legacy/trac/-/issues/492Generation of dummy messages2019-06-17T19:06:58ZTracGeneration of dummy messagesFor an increase in cover traffic mixminion should automatically generate
dummy messages, similar to mixmaster's INDUMMYP and OUTDUMMYP.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcrFor an increase in cover traffic mixminion should automatically generate
dummy messages, similar to mixmaster's INDUMMYP and OUTDUMMYP.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcrhttps://gitlab.torproject.org/legacy/trac/-/issues/491Remove "BEGIN TYPE III" wrapping2019-06-17T19:06:58ZTracRemove "BEGIN TYPE III" wrappingFor increasing user acceptance outgoing mixminion messages should not be wrapped
with the "-----BEGIN TYPE III ANONYMOUS MESSAGE-----" type disclaimer, especially
as it munges PGP messages.
In my opinion this should definitely go away wi...For increasing user acceptance outgoing mixminion messages should not be wrapped
with the "-----BEGIN TYPE III ANONYMOUS MESSAGE-----" type disclaimer, especially
as it munges PGP messages.
In my opinion this should definitely go away with the next version and not wait
until mixminion leaves alpha.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcrhttps://gitlab.torproject.org/legacy/trac/-/issues/490Additional headers for outgoing messages2019-06-17T19:06:58ZTracAdditional headers for outgoing messagesFor better acceptance with users mixminion should allow arbitrary headers in
outgoing messages, e.g. "Newsgroups" or "X-Hashcash" for posting to Newsgroups.
Exit remailer operators could then allow an arbitrary subset of those headers
an...For better acceptance with users mixminion should allow arbitrary headers in
outgoing messages, e.g. "Newsgroups" or "X-Hashcash" for posting to Newsgroups.
Exit remailer operators could then allow an arbitrary subset of those headers
and discard the others.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tcr