How OMNIMIX find my message on alt.anonymous.messages?
� Does it try every messages one by one until it find the mine?
� Does it search only a message based on the subject?

In article <085ea5f79db1986d90d171245b4dd2c6@dizum.com>
Nomen Nescio <nobody@dizum.com> wrote:
>
> How OMNIMIX find my message on alt.anonymous.messages?
> � Does it try every messages one by one until it find the mine?
> � Does it search only a message based on the subject?

"-----BEGIN PGP MESSAGE-----
Version: Mixmaster 3.1 (OpenPGP module)"

>
> "-----BEGIN PGP MESSAGE-----
> Version: Mixmaster 3.1 (OpenPGP module)"

Thank You for the tip, but I don't understand.
All the messages in AAM start wiith these two strings.
I think it is difficult that OMNIMIX try to decrypt all the messages
until it find the mine.
Or maybe it do exactly this?
Or it is the subject of the message in AAM that contain the signal?

Anonymous <nobody@remailer.paranoici.org> wrote:

>>
>> "-----BEGIN PGP MESSAGE-----
>> Version: Mixmaster 3.1 (OpenPGP module)"
>
>Thank You for the tip, but I don't understand.
>All the messages in AAM start wiith these two strings.
>I think it is difficult that OMNIMIX try to decrypt all the messages
>until it find the mine.
>Or maybe it do exactly this?
>Or it is the subject of the message in AAM that contain the signal?

OM downloads all messages into its Hamster repository in intervals
specified at Hamster|Config. When a user requests his nyms' incoming
mail, OM scans all messages since the nyms' last request
(NymConfigurator|NymAccounts|NewsgroupPointer) for matching encoded
subject (NymConfigurator|NymAccounts|Subject), decodes the postings it
finds and hands over the results to the requesting mail client.

> OM downloads all messages into its Hamster repository in intervals
> specified at Hamster|Config. When a user requests his nyms' incoming
> mail, OM scans all messages since the nyms' last request
> (NymConfigurator|NymAccounts|NewsgroupPointer) for matching encoded
> subject (NymConfigurator|NymAccounts|Subject), decodes the postings it
> finds and hands over the results to the requesting mail client.

Thank You for your answer.
I try to understand. For example if a message on AAM has this
subject:
Subject: 6721c8c1f8d2c7e312d3300f963247c36177b34e11126cab

No one of my (NymConfigurator|NymAccounts|Subject) matches this
subject.
The subject in AAM is encrypted? and how?

> The subject in AAM is encrypted? and how?

http://www.is-not-my.name/hsub.html

Anonymous <nobody@remailer.paranoici.org> wrote:

>> OM downloads all messages into its Hamster repository in intervals
>> specified at Hamster|Config. When a user requests his nyms' incoming
>> mail, OM scans all messages since the nyms' last request
>> (NymConfigurator|NymAccounts|NewsgroupPointer) for matching encoded
>> subject (NymConfigurator|NymAccounts|Subject), decodes the postings it
>> finds and hands over the results to the requesting mail client.
>
>Thank You for your answer.
>I try to understand. For example if a message on AAM has this
>subject:
>Subject: 6721c8c1f8d2c7e312d3300f963247c36177b34e11126cab
>
>No one of my (NymConfigurator|NymAccounts|Subject) matches this
>subject.
>The subject in AAM is encrypted? and how?

8 bytes of random data plus the appended subject are hashed
(IDEA/Blowfish/SHA256), the hash is added to those 8 random
bytes and the result finally truncated at choice:

<https://sourceforge.net/p/mixmaster/mailman/message/22705507/>
<http://www.is-not-my.name/hsub.html>

On 2023-01-29 19:49, Fritz Wuehler wrote:

>> The subject in AAM is encrypted? and how?

> 8 bytes of random data plus the appended subject are hashed
> (IDEA/Blowfish/SHA256), the hash is added to those 8 random
> bytes and the result finally truncated at choice:
>
> <https://sourceforge.net/p/mixmaster/mailman/message/22705507/>
> <http://www.is-not-my.name/hsub.html>

There are 2 types of nym servers. Ghio and Zax-type. At present only
Ghio nymservers are available. Ironic since Ghio is the older of the two
types.

Ghio nymservers rely on Type 1 remailers. If the nym user wishes to
encrypt her subject line she must rely on only those Type 1 remailers
that support Esub. Like Paranoia remailer for example.

These remailers use a Mixmaster binary that was compiled with a bit of
code called Esub. Esub creates encrypted subject lines using the IDEA
algorithm and MD5. Alternatively, Blowfish algorithm is used in place of
IDEA (esubbf).

Zax-type nym servers (sometimes refered to as Hsub nym servers) use a
bit of code called Hsub to encrypt the subject line. Hsub uses SHA-256
and some randomly generate bits.

Hsub is supported by some remailers. But Ghio-style nymservers will not
use it. They will use only Esub for encrypting subjects.

--
SEC3

YAMN Help Tutorial - https://www.sec3.net/yamnhelp/

SEC3 <admin@sec3.net> wrote:

>On 2023-01-29 19:49, Fritz Wuehler wrote:
>
>>> The subject in AAM is encrypted? and how?
>
>> 8 bytes of random data plus the appended subject are hashed
>> (IDEA/Blowfish/SHA256), the hash is added to those 8 random
>> bytes and the result finally truncated at choice:
>>
>> <https://sourceforge.net/p/mixmaster/mailman/message/22705507/>
>> <http://www.is-not-my.name/hsub.html>
>
>There are 2 types of nym servers. Ghio and Zax-type. At present only
>Ghio nymservers are available. Ironic since Ghio is the older of the two
>types.

And the more versatile one.

>
>Ghio nymservers rely on Type 1 remailers. If the nym user wishes to
>encrypt her subject line she must rely on only those Type 1 remailers
>that support Esub. Like Paranoia remailer for example.

nym.mixmin.net uses Blowfish instead of IDEA, so when you setup a mixmin
nym with an empty reply block, which means doing without further Type 1
remailers, the mixmin nymserver's integrated Type 1 remailer posts
directly to the (a.a.m) newsgroup using that Blowfish algorithm.

Fortunately OmniMix scans for all subject encoding algorithms in use
(MD5/IDEA, MD5/Blowfish, SHA256).

>
>These remailers use a Mixmaster binary that was compiled with a bit of
>code called Esub. Esub creates encrypted subject lines using the IDEA
>algorithm and MD5. Alternatively, Blowfish algorithm is used in place of
>IDEA (esubbf).
>
>Zax-type nym servers (sometimes refered to as Hsub nym servers) use a
>bit of code called Hsub to encrypt the subject line. Hsub uses SHA-256
>and some randomly generate bits.
>
>Hsub is supported by some remailers. But Ghio-style nymservers will not
>use it. They will use only Esub for encrypting subjects.

In article <20230130.025727.1a2ac599@erienetworks.net>
Yamn Remailer <remailer@domain.invalid> wrote:
>
> SEC3 <admin@sec3.net> wrote:
>
> >On 2023-01-29 19:49, Fritz Wuehler wrote:
> >
> >>> The subject in AAM is encrypted? and how?
> >
> >> 8 bytes of random data plus the appended subject are hashed
> >> (IDEA/Blowfish/SHA256), the hash is added to those 8 random
> >> bytes and the result finally truncated at choice:
> >>
> >> <https://sourceforge.net/p/mixmaster/mailman/message/22705507/>
> >> <http://www.is-not-my.name/hsub.html>
> >
> >There are 2 types of nym servers. Ghio and Zax-type. At present only
> >Ghio nymservers are available. Ironic since Ghio is the older of the two
> >types.
>
> And the more versatile one.
>
> >
> >Ghio nymservers rely on Type 1 remailers. If the nym user wishes to
> >encrypt her subject line she must rely on only those Type 1 remailers
> >that support Esub. Like Paranoia remailer for example.
>
> nym.mixmin.net uses Blowfish instead of IDEA, so when you setup a mixmin
> nym with an empty reply block, which means doing without further Type 1
> remailers, the mixmin nymserver's integrated Type 1 remailer posts
> directly to the (a.a.m) newsgroup using that Blowfish algorithm.
>
> Fortunately OmniMix scans for all subject encoding algorithms in use
> (MD5/IDEA, MD5/Blowfish, SHA256).
>
> >
> >These remailers use a Mixmaster binary that was compiled with a bit of
> >code called Esub. Esub creates encrypted subject lines using the IDEA
> >algorithm and MD5. Alternatively, Blowfish algorithm is used in place of
> >IDEA (esubbf).
> >
> >Zax-type nym servers (sometimes refered to as Hsub nym servers) use a
> >bit of code called Hsub to encrypt the subject line. Hsub uses SHA-256
> >and some randomly generate bits.
> >
> >Hsub is supported by some remailers. But Ghio-style nymservers will not
> >use it. They will use only Esub for encrypting subjects.

OmniMix is cool as shit for all the capability it brings to the
table as a package, and enables through other served pass-thru
resource options. Extremely reliable as well. I've had an
instance running for 7 months on a 2008 R2 VM without a restart.