| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 26 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:01:48 |
| Calls: | 632 |
| Files: | 1,187 |
| D/L today: |
27 files (19,977K bytes) |
| Messages: | 178,944 |
Messages comming from an Onion Courier client, regardless
of size, will be automatically padded with a multiple of
4096 bytes and with 33 percent base64 overhead. I will
integrate adaptive padding, which varies for each message,
in the Onion Courier Mix client, so that third parties do not
know the real message size and do not know, when inspecting
encrypted Tor network pakets that the message is for the
Onion Courier Mixnet, which one can guess with fixed client
payload approx. 30 KB, with Mixmaster and YAMN. The adpative
padding from the client will be removed, when messages
are saved in the pool so that they always have the same size
(from a mulitple of 4096 bytes), as you can see above.
Regarding the 1.1.1970 date, I think it is cool when an (or
an anonymous) operator starts his own Onion Courier Mixnode,
either publicity or anonymously, he will only see all relevant
Mixnode files have this date, so in case third parties would
gain access to the Tor Hidden Service Onion Courier Mixnode
they only see file creation dates from this date. :-)
Re-worked the design. Now the Onion Courier Tor Hidden Service
Mix Server holds the pool in RAM (not a RAM-Disk) and messages
are saved in binary format to get rid of the base64 overhead.
Therefore no filenames with the date 1.1.1970 are needed.
All binary messages in the pool have three encrypted headers in
json format. The headers are: OnionAddress, Message, CreatedAt,
so in case forensic techniques would be used to access the RAM,
then there is not much to see, only encrypted blobs.
Each message sits in the pool between 5 to 20 minutes. Messages
are shuffled and picked randomly. The pool size is 100 messages.
If the pool gets flooded 33% of the pool messages will be send.
If script kiddies use some techniques to create loops, this will
be detected too and deleted. Messages addressed to abcde123.dummy
instead of abcde123.onion are dummy messages, the client can send.
They stay in the pool also between 5 to 20 minutes prior they get
deleted.
When onion addresses are not reachable, messages will be deleted,
instead of re-trying, so that this is not another attack vector.
CLI client is done. :-) Next comes a GUI client version and finally
an email gateway.
Stefan Claas wrote:
CLI client is done. :-) Next comes a GUI client version and finally
an email gateway.
A message send to an Onion Courier home server does not have a From:
header so that anonymous Onion Courier Mix nodes stay anonymous. :-)
Example received message:
To: vztrzrdafvnjegctrltkv6azyrjqawqmrwnhe7kvaqnj5vvnwhoiq7id.onion:8080
Hello World! :-)
Regards
Stefan
As you can see MIME headers, like in classic emails, are no longer needed, because Go handles UTF-8, but users can still include additional headers.
Stefan Claas wrote:
Stefan Claas wrote:
CLI client is done. :-) Next comes a GUI client version and finally
an email gateway.
A message send to an Onion Courier home server does not have a From:
header so that anonymous Onion Courier Mix nodes stay anonymous. :-)
Example received message:
To: vztrzrdafvnjegctrltkv6azyrjqawqmrwnhe7kvaqnj5vvnwhoiq7id.onion:8080
Hello World! :-)
Regards
Stefan
As you can see MIME headers, like in classic emails, are no longer needed, because Go handles UTF-8, but users can still include additional headers.
Brilliant !!!
+1000
On 21 Sep 2025, Underground Railroad <underground@railroad.invalid>
posted some news:10aq8cd$b5ch$1@paganini.bofh.team:
Do you prefer to feel swell rather than swollen? Tired of being
battered by the Mix Masters?
Escape the Mix Master plantation. Find your underground railroad to
digital freedom with Bitmessage.
How many groups can you post to at once with bitmessage?
If it has the same stupid 3 group 2 hierarchy limit like the server you posted from it is not worth shit. Other usenet server users can shit all over groups and anonymous users can't reply because of blocked groups or group limits. Pretty stupid in this day and age to still do that.
Gabx wrote:
Stefan Claas wrote:
Stefan Claas wrote:
CLI client is done. :-) Next comes a GUI client version and finally
an email gateway.
A message send to an Onion Courier home server does not have a From: header so that anonymous Onion Courier Mix nodes stay anonymous. :-)
Example received message:
To: vztrzrdafvnjegctrltkv6azyrjqawqmrwnhe7kvaqnj5vvnwhoiq7id.onion:8080
Hello World! :-)
Regards
Stefan
As you can see MIME headers, like in classic emails, are no longer needed,
because Go handles UTF-8, but users can still include additional headers.
Brilliant !!!
+1000
Thank you very much, Gabx!
You morons using the anonymous remailers have never had anythingintelligent or worthwhile to say. Having access to great anonymity
Add to killfile: 'mixmin' 'noreply' 'nobody'.
So I won't see any more of your nameless raving and profanity.