In article <6ff3f3cdfe4e392393a112f63d2e7021@remailer.paranoici.org>
Anonymous <nobody@remailer.paranoici.org> wrote:

>In article <slrnsji7l0.fqr.admin@fleegle.mixmin.net>
>Zax <admin@mixmin.net> wrote:
>>
>> The main problem is deciding how to behave when the remailers available
>> (and their stats) cannot fulfil the user's configuration requirements.
>> Mixmaster fails in these circumstances with "No remailers available".
>> Yamn has a plethora of error messages that attempt to explain the
>> problem and (in some instances) will relax stats requirements to try and
>> find more remailers meeting the desired criteria.
>>
>> > *,*,*,* is the chain that I would suggest you use.
>> This is good advise but I'd still like Yamn to behave as well as
>> possible to reasonable user configurations. I'll try and take a look at
>> it. Moving the whole chain creation process to a dedicated package and
>> adding some tests would be a good start.
>
>Hi,
>
>also picking up some randoms remailer always only the first remailer changes.
>Only the dummy is using diverent remailer.

The Yamn version that comes with OM 2.6.1 finally got it right!

Anonymous Remailer <remailer@domain.invalid> wrote:

>In article <slrnsji7l0.fqr.admin@fleegle.mixmin.net>
>Zax <admin@mixmin.net> wrote:
>>
>> Moving the whole chain creation process to a dedicated package and
>> adding some tests would be a good start.
>
>Thank you for fixing the bug.

Nothing fixed yet. I guess Zax is on vacation taking a looong trip.

Chains right-aligned for illustrative reasons.

YAMN code from https://github.com/crooks/yamn (patched for 10 copies)

| >yamn -m -c 10 -l *,*,*,*,*,* msg.txt
| Info: 2021/10/30 09:52:35 chain.go:36: Stats updated and reimported
| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@remailer.privacy.at,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: nyam@remailer.frell.eu.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net

And here the results with the patches from
https://www.sec3.net/misc/Christian.Danner.patches.for.YAMN/index.html

| >yamn -m -c 10 -l *,*,*,*,*,* msg.txt
| Info: 2021/10/30 09:54:15 chain.go:36: Stats updated and reimported
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@mix2.remailer.xyz,yamn@mix1.remailer.xyz,yamn@virebent.art,yamn@remailer.privacy.at,yamn2@mixmin.net,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@tnetconsulting.net,yamn@yamn.paranoici.org,yamn@remailer.privacy.at,yamn@mixmin.net,yamn@mix2.remailer.xyz,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@virebent.art,nyam@remailer.frell.eu.org,yamn@yamn.paranoici.org,yamn2@mixmin.net,yamn@mix1.remailer.xyz,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@mixharbor.xyz,yamn@middleman.remailer.online,nyam@remailer.frell.eu.org,yamn@mix1.remailer.xyz,yamn@virebent.art,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@tnetconsulting.net,yamn2@mixmin.net,yamn@mixmin.net,yamn@middleman.remailer.online,yamn@mix2.remailer.xyz,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@remailer.privacy.at,yamn@virebent.art,yamn4@mixmin.net,yamn@mixharbor.xyz,yamn@mix1.remailer.xyz,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn@tnetconsulting.net,yamn@mix1.remailer.xyz,yamn@mixmin.net,yamn@mix2.remailer.xyz,yamn2@mixmin.net,yamn3@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: yamn4@mixmin.net,yamn2@mixmin.net,yamn@mix2.remailer.xyz,yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn3@mixmin.net
| Info: 2021/10/30 09:54:16 client.go:174: Chain: yamn@mix1.remailer.xyz,yamn@yamn.paranoici.org,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@middleman.remailer.online,yamn3@mixmin.net
| Info: 2021/10/30 09:54:16 client.go:174: Chain: yamn2@mixmin.net,yamn@yamn.paranoici.org,yamn@remailer.privacy.at,yamn4@mixmin.net,yamn@mixharbor.xyz,yamn3@mixmin.net

>| >yamn -m -c 10 -l *,*,*,*,*,* msg.txt
>| Info: 2021/10/30 09:52:35 chain.go:36: Stats updated and reimported
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@remailer.privacy.at,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: nyam@remailer.frell.eu.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net

Years of development and Zax, the client programmers, none of these experts had a look at the resulting chains, while it's blindingly obvious, that apart from the entry remailer all of them are identical? I still don't get it. What next?

On 2021-10-31 4:41 a.m., Anonymous wrote:
>> | >yamn -m -c 10 -l *,*,*,*,*,* msg.txt
>> | Info: 2021/10/30 09:52:35 chain.go:36: Stats updated and reimported
>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@remailer.privacy.at,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: nyam@remailer.frell.eu.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>
>
> Years of development and Zax, the client programmers, none of these experts had a look at the resulting chains, while it's blindingly obvious, that apart from the entry remailer all of them are identical? I still don't get it. What next?
>

First, request a refund.

Then stop playing the victim, get off your ass and seek out a solution
that does a better job than YAMN.

--
SEC3

YAMN Tutorials - https:/www.sec3.net/yamnhelp/

SEC3 <admin@sec3.net> wrote:

>On 2021-10-31 4:41 a.m., Anonymous wrote:
>>> | >yamn -m -c 10 -l *,*,*,*,*,* msg.txt
>>> | Info: 2021/10/30 09:52:35 chain.go:36: Stats updated and reimported
>>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:35 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn4@mixmin.net,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@remailer.privacy.at,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: nyam@remailer.frell.eu.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>> | Info: 2021/10/30 09:52:36 client.go:172: Chain: yamn@yamn.paranoici.org,yamn@middleman.remailer.online,yamn@tnetconsulting.net,yamn@mix2.remailer.xyz,yamn@mixharbor.xyz,yamn2@mixmin.net
>>
>>
>> Years of development and Zax, the client programmers, none of these experts had a look at the resulting chains, while it's blindingly obvious, that apart from the entry remailer all of them are identical? I still don't get it. What next?
>>
>
>First, request a refund.
>
>Then stop playing the victim, get off your ass and seek out a solution
>that does a better job than YAMN.

Why seek? We have Mixmaster.

No reason to praise YAMN as if it were the Holy Grail.

A little more objectivity and wariness, which are essential in this
business, and you with your friends would have seen the obvious

MID <086319e2f9bb747e72f49b8a36539dc4@remailer.paranoici.org>
| Chain: yamn@cloaked.pw,yamn2@mixmin.net,yamn3@mixmin.net
| Chain: yamn@sec3.net,yamn2@mixmin.net,yamn3@mixmin.net
| Chain: yamn@cloaked.pw,yamn2@mixmin.net,yamn3@mixmin.net

or MID <5fd8b87dd8937cfaeea85c0876bf1da3@remailer.privacy.at>
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > yamn@remailer.privacy.at,yamn@mixport.xyz,yamn3@mixmin.net
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > yamn@mixharbor.xyz,yamn@mixport.xyz,yamn3@mixmin.net
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > yamn@mixharbor.xyz,yamn@mixport.xyz,yamn3@mixmin.net
....
| Info: 2021/05/02 20:12:52 chain.go:35: Stats updated and
| reimported
| Info: 2021/05/02 20:12:52 client.go:171: Chain:
| yamn@mixport.xyz,yamn@middleman.remailer.online,yamn3@mixmin.net
| Info: 2021/05/02 20:12:52 client.go:171: Chain:
| yamn4@mixmin.net,yamn@middleman.remailer.online,yamn3@mixmin.net
| Info: 2021/05/02 20:12:52 client.go:171: Chain:
| yamn@mixmin.net,yamn@middleman.remailer.online,yamn3@mixmin.net
| Message sent!

instead of promoting YAMN wherever possible

MID <20200313163118.00007027@300baud.de>
| > Any suggestions?
| > Thanks!
|
| *flame on*
|
| switch to modern YAMN ...
|
| https://sec3.net/yamnhelp/

or MID <ltvQI.774385$HdJ9.739352@fx09.ams1>
| > Not willing to add to this dispute, but my problem is mixmaster
| > works very well for me as a longstanding omnimix user, and now I
| > see its infrastructure undermined by yamn. The same goes with
| > two additional incompatible nymxyz servers instead of the
| > traditional one. No benefit for us users, just confusion.
|
| Sadly Mixmaster 3.0 is abandonware. And Mixmaster 4096 is fast
| approaching that status. Witness, for example, that every new remailer
| coming online is a YAMN remailer.
|
| "You better start swimming
| Or you'll sink like a stone
| For the times they are a-changin" -Bob Dylan

or MID <eCKZI.9460$ZXL.5520@fx09.ams1>
| Why not use the YAMN network then? One of the reasons YAMN's creator Zax
| wrote YAMN was to eliminate the possibility of tagging attacks in the
| Mixmaster network.

BTW, this wasn't the first time the chain problem has been reported.

You remember

MID <33bf4db4ae6bcbba9ca11af161b3d2bd@mail.zip2.in>
<https://groups.google.com/g/alt.privacy.anon-server/c/oP1aUEH4LNo/m/6J6hwr8KBgAJ>

which shows how bug reports are talked down in this group without
further examination? Not one of your best days, I guess. ;-)