From Newsgroup: sci.crypt

Hi all,

comming soon.

https://github.com/Ch1ffr3punk/oc

Regards
Stefan
--
https://tilde.club/~pollux/
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Stefan Claas wrote:

Hi all,

comming soon.

https://github.com/Ch1ffr3punk/oc

It sounds amazing !!!

Gabx
--
0745 074D FEAA 9CB7 62E9 D89D 3E54 F490 F2CC 5A82
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Gabx wrote:

Stefan Claas wrote:

Hi all,

comming soon.

https://github.com/Ch1ffr3punk/oc

It sounds amazing !!!

Thank you! The Onion Courier Mixnet client and server
is very easy to use. An Onion Courier mixnode operator
has only to set-up a Tor Hidden Service (on his smartphone
for example... :-)), generate a key pair with the server
and then only start the mixnode server. No Web server or
postfix etc., or own Domain is needed. A mixnode operator
has also not to worry about middleman or exit remailers,
because this is handled by non-mixnode endpoint servers,
like for Usenet or email etc, or delivery to an Onion
Courier home server for users. People can run their own
anonymous Onion Courier Mixnet with family and friends
and can use public available mixnodes too, for building
chains.

Message flow is like this. A user creates his message
with the Onion Courier Mix client (CLI or GUI). When
the message is send it has adaptive padding for the
first mixnode in the chain applied and not fixed packet
size, like Mixmaster or YAMN has. So in case the encrypted
Tor Network payload is examined with Wireshark etc. there
is no fixed size payload. Once the message arrives at the
first hop the padding will be removed and then the message
will be stored encrypted, by the servers memguard protected
and automatically generated password, and padded to a fixed
size again. Each node does this fixed padding in the pool.

All encrypted blobs in the RAM pool (not a RAM disk) have
encrypted headers, along the encrypted payload. The encrypted
Onion Address header, Message header and created at time header.

The pool is checked every minute and each message is picked
randomly and send between 5 to 20 minutes. So, a maximum of
five hops would then have a maximum latency of 100 minutes,
which I think is more than enough. 5 hops maximum is IMHO
also more than enough, because the Nym Mixnet has 3 mixnode
hops.

Best regards
Stefan
--
https://tilde.club/~pollux/
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Stefan Claas wrote:

Hi all,

comming soon.

https://github.com/Ch1ffr3punk/oc

Re-worked the README.

Comparison of Mixnet Architectures:

Onion Courier vs. Mixmaster:

rLa Modern Cryptography (NaCl/Curve25519 vs. legacy RSA)
rLa Forward Secrecy (automatic pool key rotation every 24 hours)
rLa Tor Integration (hidden services vs. clearnet smtp network)
rLa Easier Deployment (HTTP/Tor vs. Domain registration, postfix set-up)
rLa External Cover Traffic Generator (systematic dummy messages)
rLa Production Ready Code (vs. aging codebase)

Onion Courier vs. Nym:

rLa More Hops (1-5 flexible hops vs. fixed 3-hop circuit)
rLa Longer Delays (5-20 minutes vs. low-latency)
rLa Better for Non-Realtime Communication (email, messaging)
rLa Decentralized Model (anyone can run mixnodes)
rLa Simpler Integration (HTTP-based vs. complex Nym protocol)
rLa Tor Compatibility (works with existing Tor infrastructure)

Regards
Stefan
--
https://tilde.club/~pollux/
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Stefan Claas wrote:

Stefan Claas wrote:

Hi all,

comming soon.

https://github.com/Ch1ffr3punk/oc

Re-worked the README.

Comparison of Mixnet Architectures:

Onion Courier vs. Mixmaster:

rLa Modern Cryptography (NaCl/Curve25519 vs. legacy RSA)
rLa Forward Secrecy (automatic pool key rotation every 24 hours)
rLa Tor Integration (hidden services vs. clearnet smtp network)
rLa Easier Deployment (HTTP/Tor vs. Domain registration, postfix set-up)
rLa External Cover Traffic Generator (systematic dummy messages)
rLa Production Ready Code (vs. aging codebase)

Onion Courier vs. Nym:

rLa More Hops (1-5 flexible hops vs. fixed 3-hop circuit)
rLa Longer Delays (5-20 minutes vs. low-latency)
rLa Better for Non-Realtime Communication (email, messaging)
rLa Decentralized Model (anyone can run mixnodes)
rLa Simpler Integration (HTTP-based vs. complex Nym protocol)
rLa Tor Compatibility (works with existing Tor infrastructure)

Added ping support to the CLI client, so that users know what
nodes are online, prior selecting a random chain or own chain.

C:\Users\xxxxxxxxxxxx\Desktop>ocmix
Usage:
ocmix -i Download configuration files
ocmix -r < infile Send through 2-5 random mixnodes
ocmix node1,node2,node3 < infile Send through specific mixnodes
ocmix -c Send cover traffic
ocmix -p Check status of all mixnodes

C:\Users\xxxxxxxxxxxx\Desktop>ocmix -p
Checking mixnode status via Tor...

bob OK
hal OK
len OK
ulf OK
wau OK

Regards
Stefan
--
https://tilde.club/~pollux/
--- Synchronet 3.21a-Linux NewsLink 1.2