info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
YAMN: How to prevent such a chain
42 views
Skip to first unread message
Anonymous Remailer (austria)
Aug 29, 2021, 6:08:51 PM8/29/21
to
# Chain:
ya...@remailer.privacy.at,ya...@remailer.privacy.at,ya...@mixmin.net
The 1st hope was specified by me, the 2nd one was chosen by YAMN.
yamn.cfg:
[Stats]
Minrel=98.5
Relfinal=98.5
Distance=3
SEC3
Aug 29, 2021, 7:51:11 PM8/29/21
to
My experience with YAMN has taught me that it doesn't behave well when
you try and hardcode your chains.
Just let it pick some randoms for you and it will. It will also pick an
exit for your last remailer, so you don't have to concern yourself with
that.
*,*,*,* is the chain that I would suggest you use.
--
SEC3
YAMN Tutorials - https://sec3.net/yamnhelp
Nomen Nescio
Aug 29, 2021, 9:08:27 PM8/29/21
to
In article <N3VWI.966062$Jv1.5...@fx07.ams1> SEC3 <ad...@sec3.net>
wrote:
Does Yamn like Mixmaster use a starex strategy to avoid chains of
remailers that are all run by a single entity or organization?
wrote:
remailers that are all run by a single entity or organization?
Anonymous
Aug 30, 2021, 4:20:37 AM8/30/21
to
In article <587e60b693622bb7...@dizum.com>
Nope.
But you can manually hardcode chains as long as you don't get
too stupid about it.
Chain: yamn3,inwtx,hal works, but sometimes you get the below
when you do. The post DOES go through.
mail.go:329: SMTP Connection Error: Server=127.0.0.1:3048,
Error=EOF
mail.go:258: SMTP relay failed
pool.go:76: Pool mailing failed: EOF
As the OP advised, *,*,*,* is good or *,*,*,yamn2 if you need
name support.
But you can manually hardcode chains as long as you don't get
too stupid about it.
Chain: yamn3,inwtx,hal works, but sometimes you get the below
when you do. The post DOES go through.
mail.go:329: SMTP Connection Error: Server=127.0.0.1:3048,
Error=EOF
mail.go:258: SMTP relay failed
pool.go:76: Pool mailing failed: EOF
As the OP advised, *,*,*,* is good or *,*,*,yamn2 if you need
name support.
Nomen Nescio
Aug 30, 2021, 7:47:37 AM8/30/21
to
Anonymous <nob...@remailer.paranoici.org> wrote:
>In article <587e60b693622bb7...@dizum.com>
>Nomen Nescio <nob...@dizum.com> wrote:
>> Does Yamn like Mixmaster use a starex strategy to avoid chains of
>> remailers that are all run by a single entity or organization?
>
>Nope.
>
>But you can manually hardcode chains as long as you don't get
>too stupid about it.
But by doing so you can't send multiple copies, which is important for a
>In article <587e60b693622bb7...@dizum.com>
>Nomen Nescio <nob...@dizum.com> wrote:
>> Does Yamn like Mixmaster use a starex strategy to avoid chains of
>> remailers that are all run by a single entity or organization?
>
>Nope.
>
>But you can manually hardcode chains as long as you don't get
>too stupid about it.
reliable delivery.
>
>As the OP advised, *,*,*,* is good or *,*,*,yamn2 if you need
>name support.
| Generated: Mon 30 Aug 2021 10:30:02 GMT
| Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
| ------------------------------------------------------------------------
| austria ???????10111 :33 ???????+++++ 100.0% D
| hal ?????0000000 :09 ?????+++++++ 100.0%
| inwtx 001011000100 :18 ++++++++++++ 100.0% D
| lambton ?11111111111 :29 ?+++++++++++ 100.0% D
| len ????10000000 :09 ????++++++++ 100.0%
| middleman 101111111101 :31 ++++++++++++ 100.0% D
| paranoyamn 011000000000 :13 ++++++++++++ 100.0%
| tncmm 101111111110 :25 ++++++++++++ 100.0% D
| victor ??????111112 :36 ??????++++++ 100.0% D
| wig ???110111111 :24 ???+++++++++ 100.0% D
| yamn ????11000000 :14 ????++++++++ 100.0%
| yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
| yamn4 ???????10111 :26 ???????+++++ 100.0% D
| yamn2 100100000000 :12 +++++++++++9 99.7%
Be honest, which of those YAMN remailers are in one hand?
Missing starex, as long as there's no strict one-remailer-per-operator
rule it's much too dangerous for me to participate in YAMN and get
compromised.
Stefan Claas
Aug 30, 2021, 11:39:53 AM8/30/21
to
> Missing starex, as long as there's no strict one-remailer-per-operator
> rule it's much too dangerous for me to participate in YAMN and get
> compromised.
Do you know if third parties are theoretically and technically able to append
long lifetime secret key files from each Mixmaster to one Mixmaster secret
key file, in case third parties would like to mount something like an eclipse
attack? Or why Zax invented short living YAMN keys (14 days)?
Regards
Stefan
Nomen Nescio
Aug 30, 2021, 2:30:03 PM8/30/21
to
Stefan Claas wrote:
>On Monday, August 30, 2021 at 1:47:37 PM UTC+2, Nomen Nescio wrote:
>> | Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
>> | ------------------------------------------------------------------------
>> | austria ???????10111 :33 ???????+++++ 100.0% D
>> | hal ?????0000000 :09 ?????+++++++ 100.0%
>> | inwtx 001011000100 :18 ++++++++++++ 100.0% D
>> | lambton ?11111111111 :29 ?+++++++++++ 100.0% D
>> | len ????10000000 :09 ????++++++++ 100.0%
>> | middleman 101111111101 :31 ++++++++++++ 100.0% D
>> | paranoyamn 011000000000 :13 ++++++++++++ 100.0%
>> | tncmm 101111111110 :25 ++++++++++++ 100.0% D
>> | victor ??????111112 :36 ??????++++++ 100.0% D
>> | wig ???110111111 :24 ???+++++++++ 100.0% D
>> | yamn ????11000000 :14 ????++++++++ 100.0%
>> | yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
>> | yamn4 ???????10111 :26 ???????+++++ 100.0% D
>> | yamn2 100100000000 :12 +++++++++++9 99.7%
>>
>> Be honest, which of those YAMN remailers are in one hand?
>
>I run hal and len.
How about inwtx? And finally there are yamn ... yamn4, held by Zax.
>On Monday, August 30, 2021 at 1:47:37 PM UTC+2, Nomen Nescio wrote:
>> | Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
>> | ------------------------------------------------------------------------
>> | austria ???????10111 :33 ???????+++++ 100.0% D
>> | hal ?????0000000 :09 ?????+++++++ 100.0%
>> | inwtx 001011000100 :18 ++++++++++++ 100.0% D
>> | lambton ?11111111111 :29 ?+++++++++++ 100.0% D
>> | len ????10000000 :09 ????++++++++ 100.0%
>> | middleman 101111111101 :31 ++++++++++++ 100.0% D
>> | paranoyamn 011000000000 :13 ++++++++++++ 100.0%
>> | tncmm 101111111110 :25 ++++++++++++ 100.0% D
>> | victor ??????111112 :36 ??????++++++ 100.0% D
>> | wig ???110111111 :24 ???+++++++++ 100.0% D
>> | yamn ????11000000 :14 ????++++++++ 100.0%
>> | yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
>> | yamn4 ???????10111 :26 ???????+++++ 100.0% D
>> | yamn2 100100000000 :12 +++++++++++9 99.7%
>>
>> Be honest, which of those YAMN remailers are in one hand?
>
>I run hal and len.
YMMV, but too hot for me.
>
>> Missing starex, as long as there's no strict one-remailer-per-operator
>> rule it's much too dangerous for me to participate in YAMN and get
>> compromised.
>
>Quick questions for you.
>
>Do you know if third parties are theoretically and technically able to append
>long lifetime secret key files from each Mixmaster to one Mixmaster secret
>key file, in case third parties would like to mount something like an eclipse
>attack?
participants statistics and key files of a network topology completely
under your control. At first they're toast, some time later you are. ;)
> Or why Zax invented short living YAMN keys (14 days)?
low, as with Mixmaster you also define key lifetime in days, not in
years.
Stefan Claas
Aug 30, 2021, 4:35:11 PM8/30/21
to
On Monday, August 30, 2021 at 8:30:03 PM UTC+2, Nomen Nescio wrote:
runs, if any.
Another thing which I like to point out. We can combine message(s) sending
with YAMN, Mixmaster and also Bitmessage. Nym is currently not (yet)
an option for such tasks (wish I was a Golang programmer, like Zax is ...)
Then there would be another question from me. Why not all Mixmaster Remops
gave YAMN a try, to increase the YAMN Network, or in case they had doubts, did
not say so, or what else improvements over Mixmaster they had like seen.
I ask because I see YAMN as a TypeII+ Remailer, compared to Mixmaster, which's
development and Network should be supported, because it runs on so many
different devices.
> >> Missing starex, as long as there's no strict one-remailer-per-operator
> >> rule it's much too dangerous for me to participate in YAMN and get
> >> compromised.
> >
> >Quick questions for you.
> >
> >Do you know if third parties are theoretically and technically able to append
> >long lifetime secret key files from each Mixmaster to one Mixmaster secret
> >key file, in case third parties would like to mount something like an eclipse
> >attack?
> Own or take over a reputable pinger service and offer remailer
> participants statistics and key files of a network topology completely
> under your control. At first they're toast, some time later you are. ;)
Another interesting thought. :-)
> > Or why Zax invented short living YAMN keys (14 days)?
> That's an invention? Don't you think you're setting the bar a little
> low, as with Mixmaster you also define key lifetime in days, not in
> years.
Well, invention in that sense that Zax drastically shortened the standard
key lifetime, compared to IIRC standard Mixmaster settings.
Regards
Stefan
> Stefan Claas wrote:
> >> Be honest, which of those YAMN remailers are in one hand?
> >
> >I run hal and len.
> How about inwtx? And finally there are yamn ... yamn4, held by Zax.
> YMMV, but too hot for me.
I must admit I do not know which Remailers besides his inwtx one he also
> >> Be honest, which of those YAMN remailers are in one hand?
> >
> >I run hal and len.
> How about inwtx? And finally there are yamn ... yamn4, held by Zax.
> YMMV, but too hot for me.
runs, if any.
Another thing which I like to point out. We can combine message(s) sending
with YAMN, Mixmaster and also Bitmessage. Nym is currently not (yet)
an option for such tasks (wish I was a Golang programmer, like Zax is ...)
Then there would be another question from me. Why not all Mixmaster Remops
gave YAMN a try, to increase the YAMN Network, or in case they had doubts, did
not say so, or what else improvements over Mixmaster they had like seen.
I ask because I see YAMN as a TypeII+ Remailer, compared to Mixmaster, which's
development and Network should be supported, because it runs on so many
different devices.
> >> Missing starex, as long as there's no strict one-remailer-per-operator
> >> rule it's much too dangerous for me to participate in YAMN and get
> >> compromised.
> >
> >Quick questions for you.
> >
> >Do you know if third parties are theoretically and technically able to append
> >long lifetime secret key files from each Mixmaster to one Mixmaster secret
> >key file, in case third parties would like to mount something like an eclipse
> >attack?
> Own or take over a reputable pinger service and offer remailer
> participants statistics and key files of a network topology completely
> under your control. At first they're toast, some time later you are. ;)
> > Or why Zax invented short living YAMN keys (14 days)?
> That's an invention? Don't you think you're setting the bar a little
> low, as with Mixmaster you also define key lifetime in days, not in
> years.
key lifetime, compared to IIRC standard Mixmaster settings.
Regards
Stefan
Anonymous Remailer (austria)
Aug 30, 2021, 7:24:25 PM8/30/21
to
In article <75795cd43ba7f388...@dizum.com>
Nomen Nescio <nob...@dizum.com> wrote:
>
> Anonymous <nob...@remailer.paranoici.org> wrote:
>
> >In article <587e60b693622bb7...@dizum.com>
> >Nomen Nescio <nob...@dizum.com> wrote:
>
> >> Does Yamn like Mixmaster use a starex strategy to avoid chains of
> >> remailers that are all run by a single entity or organization?
> >
> >Nope.
> >
> >But you can manually hardcode chains as long as you don't get
> >too stupid about it.
>
> But by doing so you can't send multiple copies, which is important for a
> reliable delivery.
Yes you can.
>
> Anonymous <nob...@remailer.paranoici.org> wrote:
>
> >In article <587e60b693622bb7...@dizum.com>
> >Nomen Nescio <nob...@dizum.com> wrote:
>
> >> Does Yamn like Mixmaster use a starex strategy to avoid chains of
> >> remailers that are all run by a single entity or organization?
> >
> >Nope.
> >
> >But you can manually hardcode chains as long as you don't get
> >too stupid about it.
>
> But by doing so you can't send multiple copies, which is important for a
> reliable delivery.
Do some testing, make an honest effort to read the Info:
>
> >
> >As the OP advised, *,*,*,* is good or *,*,*,yamn2 if you need
> >name support.
>
> | Stats-Version: 2.0
> | Generated: Mon 30 Aug 2021 10:30:02 GMT
> | Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
> | ------------------------------------------------------------------------
> | austria ???????10111 :33 ???????+++++ 100.0% D
> | hal ?????0000000 :09 ?????+++++++ 100.0%
> | inwtx 001011000100 :18 ++++++++++++ 100.0% D
> | lambton ?11111111111 :29 ?+++++++++++ 100.0% D
> | len ????10000000 :09 ????++++++++ 100.0%
> | middleman 101111111101 :31 ++++++++++++ 100.0% D
> | paranoyamn 011000000000 :13 ++++++++++++ 100.0%
> | tncmm 101111111110 :25 ++++++++++++ 100.0% D
> | victor ??????111112 :36 ??????++++++ 100.0% D
> | wig ???110111111 :24 ???+++++++++ 100.0% D
> | yamn ????11000000 :14 ????++++++++ 100.0%
> | yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
> | yamn4 ???????10111 :26 ???????+++++ 100.0% D
> | yamn2 100100000000 :12 +++++++++++9 99.7%
>
> Be honest, which of those YAMN remailers are in one hand?
>
> Missing starex, as long as there's no strict one-remailer-per-operator
> rule it's much too dangerous for me to participate in YAMN and get
> compromised.
Chain: yamn3,inwtx,*,hal Copies=3
Chain: *,*,*,yamn3 Copies=3
Chain: *,wig,*,yamn2 Copies=3
Chain: *,*,tncmm,paranoyamn Copies=3
Nomen Nescio
Aug 30, 2021, 8:08:35 PM8/30/21
to
> That's an invention? Don't you think you're setting the bar a little
> low, as with Mixmaster you also define key lifetime in days, not in
> years.
| From: Nomen Nescio <nob...@dizum.com>
> low, as with Mixmaster you also define key lifetime in days, not in
> years.
| Newsgroups: alt.privacy.anon-server
| References: <slrnjpdp...@erl.tahina.priv.at> <v7udp75h40p0ngde8...@Osama-is-dead.net> <slrnjpdv...@erl.tahina.priv.at>
| Subject: Re: austria remailer's keys compromised
| Message-ID: <b1f9788b07c07ddc...@dizum.com>
| Date: Wed, 25 Apr 2012 00:04:22 +0200 (CEST)
| Mail-To-News-Contact: ab...@dizum.com
| Organization: mail...@dizum.com
| Xref: news.mixmin.net alt.privacy.anon-server:39878
|
| christian mock wrote:
|
| >G Morgan <seal...@osama-is-dead.net> wrote:
| >
| >>>What does this mean?
| >>
| >> The US authorities are going to grab an image of every remailer
| >> drive and break the chain?
| >
| >That would only make sense if they seized all remailers at the same
| >time, or else they risk keys getting wiped in anticipation of their
| >next move.
|
| That's a minor risk. Let's see whether there are remops who renew
| keys after those incidents. Keys are usually valid for one year.
|
| I don't know whether two Mixmaster keys could be used at the same time
| for message decryption. But if so, why not always have two keys
| simultaneously in action with the older one being renewed every week?
| No message is in transit for such a long time. Users just had to
| update keys more often.
Anonymous
Aug 30, 2021, 11:08:50 PM8/30/21
to
>> | Stats-Version: 2.0
>> | Generated: Mon 30 Aug 2021 10:30:02 GMT
>> | Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
>> | ------------------------------------------------------------------------
>> | austria ???????10111 :33 ???????+++++ 100.0% D
>> | hal ?????0000000 :09 ?????+++++++ 100.0%
>> | inwtx 001011000100 :18 ++++++++++++ 100.0% D
>> | lambton ?11111111111 :29 ?+++++++++++ 100.0% D
>> | len ????10000000 :09 ????++++++++ 100.0%
>> | middleman 101111111101 :31 ++++++++++++ 100.0% D
>> | paranoyamn 011000000000 :13 ++++++++++++ 100.0%
>> | tncmm 101111111110 :25 ++++++++++++ 100.0% D
>> | victor ??????111112 :36 ??????++++++ 100.0% D
>> | wig ???110111111 :24 ???+++++++++ 100.0% D
>> | yamn ????11000000 :14 ????++++++++ 100.0%
>> | yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
>> | yamn4 ???????10111 :26 ???????+++++ 100.0% D
>> | yamn2 100100000000 :12 +++++++++++9 99.7%
> Chain: *,*,*,yamn3 Copies=3
>> | Generated: Mon 30 Aug 2021 10:30:02 GMT
>> | Mixmaster Latent-Hist Latent Uptime-Hist Uptime Options
>> | ------------------------------------------------------------------------
>> | austria ???????10111 :33 ???????+++++ 100.0% D
>> | hal ?????0000000 :09 ?????+++++++ 100.0%
>> | inwtx 001011000100 :18 ++++++++++++ 100.0% D
>> | lambton ?11111111111 :29 ?+++++++++++ 100.0% D
>> | len ????10000000 :09 ????++++++++ 100.0%
>> | middleman 101111111101 :31 ++++++++++++ 100.0% D
>> | paranoyamn 011000000000 :13 ++++++++++++ 100.0%
>> | tncmm 101111111110 :25 ++++++++++++ 100.0% D
>> | victor ??????111112 :36 ??????++++++ 100.0% D
>> | wig ???110111111 :24 ???+++++++++ 100.0% D
>> | yamn ????11000000 :14 ????++++++++ 100.0%
>> | yamn3 ?10000001000 :14 ?+++++++++++ 100.0%
>> | yamn4 ???????10111 :26 ???????+++++ 100.0% D
>> | yamn2 100100000000 :12 +++++++++++9 99.7%
-> yamn,yamn1,yamn2,yamn3 -> toast
-> yamn2,yamn,yamn4,yamn3 -> toast
-> yamn4,yamn2,yamn1,yamn3 -> toast
-> yamn,yamn2,yamn1,yamn3 -> toast
-> yamn1,yamn4,yamn2,yamn3 -> toast
... toast, toast, toast
Anonymous Remailer (austria)
Aug 31, 2021, 1:31:26 AM8/31/21
to
In article
<3deb701d98b10af9...@remailer.paranoici.org>
Some OP said:
"> >But you can manually hardcode chains as long as you don't get
> >too stupid about it."
Four of your five chains are invalid.
"> >But you can manually hardcode chains as long as you don't get
> >too stupid about it."
Good luck crossing steets. Use walkovers or unders, stay out of
crosswalks.
Nomen Nescio
Aug 31, 2021, 6:32:55 AM8/31/21
to
Nomen Nescio
Aug 31, 2021, 7:03:20 AM8/31/21
to
On 8/30/2021 7:08 PM, Nomen Nescio wrote:
>> That's an invention? Don't you think you're setting the bar a little
>> low, as with Mixmaster you also define key lifetime in days, not in
>> years.
>
> | From: Nomen Nescio <nob...@dizum.com>
> | Newsgroups: alt.privacy.anon-server
> | References: <slrnjpdp...@erl.tahina.priv.at> <v7udp75h40p0ngde8...@Osama-is-dead.net> <slrnjpdv...@erl.tahina.priv.at>
> | Subject: Re: austria remailer's keys compromised
> | Message-ID: <b1f9788b07c07ddc...@dizum.com>
> | Date: Wed, 25 Apr 2012 00:04:22 +0200 (CEST)
> | Mail-To-News-Contact: ab...@dizum.com
> | Organization: mail...@dizum.com
> | Xref: news.mixmin.net alt.privacy.anon-server:39878
> |
> | christian mock wrote:
> |
> | >G Morgan <seal...@osama-is-dead.net> wrote:
> | >
> | >>>What does this mean?
> | >>
> | >> The US authorities are going to grab an image of every remailer
> | >> drive and break the chain?
> | >
> | >That would only make sense if they seized all remailers at the same
> | >time, or else they risk keys getting wiped in anticipation of their
> | >next move.
> |
> | That's a minor risk. Let's see whether there are remops who renew
> | keys after those incidents. Keys are usually valid for one year.
What are these "incidents" of which you speak?
>> That's an invention? Don't you think you're setting the bar a little
>> low, as with Mixmaster you also define key lifetime in days, not in
>> years.
>
> | From: Nomen Nescio <nob...@dizum.com>
> | Newsgroups: alt.privacy.anon-server
> | References: <slrnjpdp...@erl.tahina.priv.at> <v7udp75h40p0ngde8...@Osama-is-dead.net> <slrnjpdv...@erl.tahina.priv.at>
> | Subject: Re: austria remailer's keys compromised
> | Message-ID: <b1f9788b07c07ddc...@dizum.com>
> | Date: Wed, 25 Apr 2012 00:04:22 +0200 (CEST)
> | Mail-To-News-Contact: ab...@dizum.com
> | Organization: mail...@dizum.com
> | Xref: news.mixmin.net alt.privacy.anon-server:39878
> |
> | christian mock wrote:
> |
> | >G Morgan <seal...@osama-is-dead.net> wrote:
> | >
> | >>>What does this mean?
> | >>
> | >> The US authorities are going to grab an image of every remailer
> | >> drive and break the chain?
> | >
> | >That would only make sense if they seized all remailers at the same
> | >time, or else they risk keys getting wiped in anticipation of their
> | >next move.
> |
> | That's a minor risk. Let's see whether there are remops who renew
> | keys after those incidents. Keys are usually valid for one year.
Anonymous
Aug 31, 2021, 8:04:04 AM8/31/21
to
rmd
Aug 31, 2021, 8:09:34 AM8/31/21
to
Nomen Nescio
Aug 31, 2021, 4:04:44 PM8/31/21
to
which was involved in an e-mailed bomb threat, was seized by
Austrian authorities at the FBI's instigation.
<https://groups.google.com/g/alt.privacy.anon-server/c/q8oMjdbQg8g>
<https://news.softpedia.com/news/FBI-Pays-Visit-to-Austrian-Remailer-in-Connection-to-Bomb-Threats-266582.shtml>
<https://arstechnica.com/tech-policy/2012/04/fbi-seizes-activists-anonymous-remailer-server-in-bomb-threat-investigation/>
<https://www.wired.com/2012/04/fbi-seizes-server/>
Such incidents should pull the trigger for the immediate renewal of
all remailers' keys with a destruction of the old ones shortly
afterwards.
Anonymous Remailer (austria)
Sep 1, 2021, 6:06:52 AM9/1/21
to
Anonymous Remailer (austria)
Sep 1, 2021, 6:16:07 AM9/1/21
to
Anonymous Remailer (austria)
Sep 1, 2021, 6:37:50 AM9/1/21
to
In article <2b0452b164fd1f71...@dizum.com>
over toilet access. One of them is a well-known Usenet abuser
named Seamus. Yes THAT Seamus.
Bomb threats at Penn State are nothing new. It happens all the
time.
Anonymous Remailer (austria)
Sep 1, 2021, 7:25:33 PM9/1/21
to
In article <053636bbb9f2c0a4...@remailer.privacy.at>
his penis with garden clippers.
Zax
Sep 8, 2021, 4:35:45 PM9/8/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sun, 29 Aug 2021 19:51:07 -0400, SEC3 wrote in
Message-Id: <N3VWI.966062$Jv1.5...@fx07.ams1>:
>> ya...@remailer.privacy.at,ya...@remailer.privacy.at,ya...@mixmin.net
>>
>> The 1st hope was specified by me, the 2nd one was chosen by YAMN.
>>
>> yamn.cfg:
>>
>> [Stats]
>> Minrel=98.5
>> Relfinal=98.5
>> Distance=3
>
> "Distance" is not a valid setting in YAMN.
Distance is a valid setting and it is defined in the Stats section.
> My experience with YAMN has taught me that it doesn't behave well when
> you try and hardcode your chains.
Chain selection is probably the trickiest thing to get right and it's
quite likely there are bugs in the current implementation (the OP
appears to be seeing one).
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.
> Just let it pick some randoms for you and it will. It will also pick an
> exit for your last remailer, so you don't have to concern yourself with
> that.
>
> *,*,*,* 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.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmE5Hp8ACgkQgyyPTc2Q
QmMHJBAAlz1TiRo8aXJsFlqG77cC7iT1GNqC0yM40doU3dDmtHjynZRPvqiIAMVW
iFgOlR1WgnkrRTbnTPOz3OBVpHIB+7AKkmVXdZgOA0NlMDMw6BEZS5d1xNNDfmT5
zIQ3df1l6Yk3xUi6EDSBoOVuadXqNG1PPur9wvIL9hCB35hazO3uIRvs3Y9/tt0U
awh6RZLYmNxDHoLBw4jYmRPn/R3r2ZA4bzRNwfBfUv7yxmXZRr4hi5JmF5+W9Z+f
mN3g1fF5CzVwJh1L7zDV6D3ty01JPb04N9wNiaCzLSwhBwzQlo/SdHntIQMOQS8f
bCdDNF0KlSQQZzn88JcqSmSkMbJSeeQoYC6z8lmwbQ7JB3ZqCis2yUEdH6T23oS5
gJbNlUf9Yru/19I45flfy2pC9Ro3xfDOqTocb3YuFVXUC3LlWPtWvZ/Aj7QGluGN
g+RSzylqtFMK0tdAbDGEjuDrKKfG8BuGOvqo9RayaSK5AoT04IKkIEucyZzfX7Is
Zgzrie44g/LMw0rbpYKCsiAtkmxqm3CFBjH+EkB83qRp4w0pEQ7u0a0Wzm+439JD
y7gVs1fYsVWEpUUbzms6YXy99BLR/rGUPboZBB6qbi26+q835rGs7uyIrFHwPY46
1tUcULpEMZ6WnzcL3ce84M0L9T/P5CRqH9gwHCA0YhpfpWEouyc=
=3AGZ
-----END PGP SIGNATURE-----
--
pub 1024D/228761E7 2003-06-04 Steven Crook <st...@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S
Hash: SHA256
On Sun, 29 Aug 2021 19:51:07 -0400, SEC3 wrote in
Message-Id: <N3VWI.966062$Jv1.5...@fx07.ams1>:
>> ya...@remailer.privacy.at,ya...@remailer.privacy.at,ya...@mixmin.net
>>
>> The 1st hope was specified by me, the 2nd one was chosen by YAMN.
>>
>> yamn.cfg:
>>
>> [Stats]
>> Minrel=98.5
>> Relfinal=98.5
>> Distance=3
>
> "Distance" is not a valid setting in YAMN.
> My experience with YAMN has taught me that it doesn't behave well when
> you try and hardcode your chains.
quite likely there are bugs in the current implementation (the OP
appears to be seeing one).
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.
> Just let it pick some randoms for you and it will. It will also pick an
> exit for your last remailer, so you don't have to concern yourself with
> that.
>
> *,*,*,* is the chain that I would suggest you use.
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.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmE5Hp8ACgkQgyyPTc2Q
QmMHJBAAlz1TiRo8aXJsFlqG77cC7iT1GNqC0yM40doU3dDmtHjynZRPvqiIAMVW
iFgOlR1WgnkrRTbnTPOz3OBVpHIB+7AKkmVXdZgOA0NlMDMw6BEZS5d1xNNDfmT5
zIQ3df1l6Yk3xUi6EDSBoOVuadXqNG1PPur9wvIL9hCB35hazO3uIRvs3Y9/tt0U
awh6RZLYmNxDHoLBw4jYmRPn/R3r2ZA4bzRNwfBfUv7yxmXZRr4hi5JmF5+W9Z+f
mN3g1fF5CzVwJh1L7zDV6D3ty01JPb04N9wNiaCzLSwhBwzQlo/SdHntIQMOQS8f
bCdDNF0KlSQQZzn88JcqSmSkMbJSeeQoYC6z8lmwbQ7JB3ZqCis2yUEdH6T23oS5
gJbNlUf9Yru/19I45flfy2pC9Ro3xfDOqTocb3YuFVXUC3LlWPtWvZ/Aj7QGluGN
g+RSzylqtFMK0tdAbDGEjuDrKKfG8BuGOvqo9RayaSK5AoT04IKkIEucyZzfX7Is
Zgzrie44g/LMw0rbpYKCsiAtkmxqm3CFBjH+EkB83qRp4w0pEQ7u0a0Wzm+439JD
y7gVs1fYsVWEpUUbzms6YXy99BLR/rGUPboZBB6qbi26+q835rGs7uyIrFHwPY46
1tUcULpEMZ6WnzcL3ce84M0L9T/P5CRqH9gwHCA0YhpfpWEouyc=
=3AGZ
-----END PGP SIGNATURE-----
--
pub 1024D/228761E7 2003-06-04 Steven Crook <st...@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S
Yamn Remailer
Sep 8, 2021, 6:38:16 PM9/8/21
to
Zax <ad...@mixmin.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, 29 Aug 2021 19:51:07 -0400, SEC3 wrote in
> Message-Id: <N3VWI.966062$Jv1.5...@fx07.ams1>:
>
> >> ya...@remailer.privacy.at,ya...@remailer.privacy.at,ya...@mixmin.net
> >>
> >> The 1st hope was specified by me, the 2nd one was chosen by YAMN.
> >>
> >> yamn.cfg:
> >>
> >> [Stats]
> >> Minrel=98.5
> >> Relfinal=98.5
> >> Distance=3
> >
> > "Distance" is not a valid setting in YAMN.
>
> Distance is a valid setting and it is defined in the Stats section.
>
>
> > SNIPP
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, 29 Aug 2021 19:51:07 -0400, SEC3 wrote in
> Message-Id: <N3VWI.966062$Jv1.5...@fx07.ams1>:
>
> >> ya...@remailer.privacy.at,ya...@remailer.privacy.at,ya...@mixmin.net
> >>
> >> The 1st hope was specified by me, the 2nd one was chosen by YAMN.
> >>
> >> yamn.cfg:
> >>
> >> [Stats]
> >> Minrel=98.5
> >> Relfinal=98.5
> >> Distance=3
> >
> > "Distance" is not a valid setting in YAMN.
>
> Distance is a valid setting and it is defined in the Stats section.
>
>
> >
> > *,*,*,* 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.
>
Thank you so much.
> > *,*,*,* 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.
>
Anonymous Remailer
Sep 8, 2021, 7:09:23 PM9/8/21
to
In article <slrnsji7l0...@fleegle.mixmin.net>
Zax <ad...@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.
>
> Moving the whole chain creation process to a dedicated package and
> adding some tests would be a good start.
Anonymous
Sep 17, 2021, 12:33:15 PM9/17/21
to
> 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.
>
> (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,
> 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.
also picking up some randoms remailer always only the first remailer changes.
Only the dummy is using diverent remailer.
Info: 2021/09/17 16:37:03 chain.go:36: Stats updated and reimported
Info: 2021/09/17 16:37:03 client.go:172:
*Chain:
yamn@mix
1.remail
er.xyz,ya...@middleman.remailer.online,ya...@mixmin.net,ya...@mix1.remailer.xyz*
Trace: 2021/09/17 16:37:03 client.go:228: Encrypting Final Hop:
Hop=ya...@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mixmin.net,
KeyID=2477df1042cc8cd4776f93c4314c2fc6
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@middleman.remailer.online, KeyID=8c7e5566995ae9405b9891078f5511df
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mix1.remailer.xyz,
KeyID=e3dd4bd7f418334dc46b28492849c6c8
Info: 2021/09/17 16:37:03 client.go:172:
*Chain:
yamn@yam
n.parano
ici.org,ya...@middleman.remailer.online,ya...@mixmin.net,ya...@mix1.remailer.xyz*
Trace: 2021/09/17 16:37:03 client.go:228: Encrypting Final Hop:
Hop=ya...@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mixmin.net,
KeyID=2477df1042cc8cd4776f93c4314c2fc6
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@middleman.remailer.online, KeyID=8c7e5566995ae9405b9891078f5511df
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
Info: 2021/09/17 16:37:03 client.go:172:
*Chain:
yamn@mix
2.remail
er.xyz,ya...@middleman.remailer.online,ya...@mixmin.net,ya...@mix1.remailer.xyz*
Trace: 2021/09/17 16:37:03 client.go:228: Encrypting Final Hop:
Hop=ya...@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mixmin.net,
KeyID=2477df1042cc8cd4776f93c4314c2fc6
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@middleman.remailer.online, KeyID=8c7e5566995ae9405b9891078f5511df
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mix2.remailer.xyz,
KeyID=12ae1d651de452cbeba31d4e710b0599
Trace: 2021/09/17 16:37:03 client.go:350: Sending dummy through:
ya...@yamn.paranoici.org,ya...@mix1.remailer.xyz,yamn@tnetconsultin
g.net,ya...@mixmin.net.
Trace: 2021/09/17 16:37:03 client.go:228: Encrypting Final Hop:
Hop=ya...@mixmin.net, KeyID=8f652b81dd69e5dfb1c7a9626b6f7a46
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@tnetconsulting.net, KeyID=b42cffbfb4f026ce3b073a8202df8c8b
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting: Hop=ya...@mix1.remailer.xyz,
KeyID=e3dd4bd7f418334dc46b28492849c6c8
Trace: 2021/09/17 16:37:03 client.go:281: Encrypting:
Hop=ya...@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
I'm using the yamn.exe 2021-07-03 19:14 8.4M from your page.
Anonymous Remailer
Sep 19, 2021, 4:58:34 PM9/19/21
to
In article <6ff3f3cdfe4e3923...@remailer.paranoici.org>
Anonymous <nob...@remailer.paranoici.org> wrote:
>In article <slrnsji7l0...@fleegle.mixmin.net>
>Zax <ad...@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!
>In article <slrnsji7l0...@fleegle.mixmin.net>
>Zax <ad...@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.
Anonymous
Oct 30, 2021, 2:54:41 PM10/30/21
to
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: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mix1.remailer.xyz,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@remailer.privacy.at,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ny...@remailer.frell.eu.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@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: ya...@mix2.remailer.xyz,ya...@mix1.remailer.xyz,ya...@virebent.art,ya...@remailer.privacy.at,ya...@mixmin.net,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@tnetconsulting.net,ya...@yamn.paranoici.org,ya...@remailer.privacy.at,ya...@mixmin.net,ya...@mix2.remailer.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@virebent.art,ny...@remailer.frell.eu.org,ya...@yamn.paranoici.org,ya...@mixmin.net,ya...@mix1.remailer.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@mixharbor.xyz,ya...@middleman.remailer.online,ny...@remailer.frell.eu.org,ya...@mix1.remailer.xyz,ya...@virebent.art,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@tnetconsulting.net,ya...@mixmin.net,ya...@mixmin.net,ya...@middleman.remailer.online,ya...@mix2.remailer.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@remailer.privacy.at,ya...@virebent.art,ya...@mixmin.net,ya...@mixharbor.xyz,ya...@mix1.remailer.xyz,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@tnetconsulting.net,ya...@mix1.remailer.xyz,ya...@mixmin.net,ya...@mix2.remailer.xyz,ya...@mixmin.net,ya...@mixmin.net
| Info: 2021/10/30 09:54:15 client.go:174: Chain: ya...@mixmin.net,ya...@mixmin.net,ya...@mix2.remailer.xyz,ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@mixmin.net
| Info: 2021/10/30 09:54:16 client.go:174: Chain: ya...@mix1.remailer.xyz,ya...@yamn.paranoici.org,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@middleman.remailer.online,ya...@mixmin.net
| Info: 2021/10/30 09:54:16 client.go:174: Chain: ya...@mixmin.net,ya...@yamn.paranoici.org,ya...@remailer.privacy.at,ya...@mixmin.net,ya...@mixharbor.xyz,ya...@mixmin.net
Anonymous
Oct 31, 2021, 4:41:36 AM10/31/21
to
>| >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: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mix1.remailer.xyz,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@remailer.privacy.at,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ny...@remailer.frell.eu.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@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?
>| 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: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mix1.remailer.xyz,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:35 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@mixmin.net,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@remailer.privacy.at,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ny...@remailer.frell.eu.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
>| Info: 2021/10/30 09:52:36 client.go:172: Chain: ya...@yamn.paranoici.org,ya...@middleman.remailer.online,ya...@tnetconsulting.net,ya...@mix2.remailer.xyz,ya...@mixharbor.xyz,ya...@mixmin.net
SEC3
Oct 31, 2021, 11:49:10 AM10/31/21
to
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/
Yamn Remailer
Oct 31, 2021, 12:57:09 PM10/31/21
to
chains.
Nomen Nescio
Oct 31, 2021, 5:11:49 PM10/31/21
to
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 <086319e2f9bb747e...@remailer.paranoici.org>
| Chain: ya...@cloaked.pw,ya...@mixmin.net,ya...@mixmin.net
| Chain: ya...@sec3.net,ya...@mixmin.net,ya...@mixmin.net
| Chain: ya...@cloaked.pw,ya...@mixmin.net,ya...@mixmin.net
or MID <5fd8b87dd8937cfa...@remailer.privacy.at>
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > ya...@remailer.privacy.at,ya...@mixport.xyz,ya...@mixmin.net
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > ya...@mixharbor.xyz,ya...@mixport.xyz,ya...@mixmin.net
| > > Info: 2021/05/02 16:26:43 client.go:171: Chain:
| > > ya...@mixharbor.xyz,ya...@mixport.xyz,ya...@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:
| ya...@mixport.xyz,ya...@middleman.remailer.online,ya...@mixmin.net
| Info: 2021/05/02 20:12:52 client.go:171: Chain:
| ya...@mixmin.net,ya...@middleman.remailer.online,ya...@mixmin.net
| Info: 2021/05/02 20:12:52 client.go:171: Chain:
| ya...@mixmin.net,ya...@middleman.remailer.online,ya...@mixmin.net
| Message sent!
instead of promoting YAMN wherever possible
MID <20200313163...@300baud.de>
| > Any suggestions?
| > Thanks!
|
| *flame on*
|
| switch to modern YAMN ...
|
| https://sec3.net/yamnhelp/
or MID <ltvQI.774385$HdJ9....@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....@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 <33bf4db4ae6bcbba...@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. ;-)
Nomen Nescio
Oct 31, 2021, 6:17:21 PM10/31/21
to
where chain creation problems don't matter.
Fritz Wuehler
Nov 1, 2021, 1:25:54 AM11/1/21
to
In article <20211031.165...@mixmin.net>
All solutions will ultimately be at the expense of hops.
But how many hops does one need?
But how many hops does one need?
Anonymous Remailer (austria)
Nov 1, 2021, 3:19:03 AM11/1/21
to
Fritz Wuehler <fr...@spamexpire-202111.rodent.frell.theremailer.net>
wrote:
>
>But how many hops does one need?
Anonymous Remailer (austria)
Nov 1, 2021, 5:22:22 AM11/1/21
to
In article <0b6156b5e0cb8543...@remailer.privacy.at>
> >
> >But how many hops does one need?
>
> 5+?
choice into a yamn or mixmaster network.
0 new messages