Attn: Zax

Web Server Talk > WebserverTalk Community > Anonymous Servers > Attn: Zax

Last Thread Next Thread Next

Attn: Zax

Nomen Nescio

12-19-07 06:16 AM

Is nym.mixmin.net open for business?

Repeated requests for its public key fail because "nym.mixmin.net"
can't be resolved.[1]  Where can the key be found?

Even if the key were available, if the host name can't be resolved,
how could the nymserver be used?

---

[1] Mail to www4mail@wm.ictp.trieste.it requesting the source of
http://www.mit.edu:8001/finger?rema...@nym.mixmin.net returns

<!-- X-URL: http://stuff.mit.edu/cgi/finger?rem...@nym.mixmin.net -->
<base href="http://stuff.mit.edu/cgi/finger?remailer-key@nym.mixmin.net">
<html><head><isindex>
<title>Finger remailer-key@nym.mixmin.net</title></head>
<body>
<h1>Finger remailer-key@nym.mixmin.net</h1>
<strong>Couldn't resolve host nym.mixmin.net</strong>
<hr>

[ Post a follow-up to this message ]

Re: Attn: Zax

Zax

12-19-07 12:15 PM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, 19 Dec 2007 06:50:37 +0100 (CET), Nomen Nescio wrote in
Message-Id: <43b079d00c3b1cbfdb568c7689ad478a@dizum.com>:

> Is nym.mixmin.net open for business?

Yes it's been running for some time now.

> Repeated requests for its public key fail because "nym.mixmin.net"
> can't be resolved.[1]  Where can the key be found?

You get the key by sending an email to remailer-key@nym.mixmin.net.  The
domain name doesn't resolve because it's a virtual mail domain.  The
only DNS record it has is an MX.

$ dig nym.mixmin.net mx

; <<>> DiG 9.4.2 <<>> nym.mixmin.net mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1848
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 5

;; QUESTION SECTION:
;nym.mixmin.net.                        IN      MX

;; ANSWER SECTION:
nym.mixmin.net.         86400   IN      MX      20 drooper.mixmin.net.
nym.mixmin.net.         86400   IN      MX      10 fleegle.mixmin.net.

;; AUTHORITY SECTION:
mixmin.net.             86400   IN      NS      asteria.debian.or.at.
mixmin.net.             86400   IN      NS      ns2.mixmin.net.
mixmin.net.             86400   IN      NS      ns1.mixmin.net.

;; ADDITIONAL SECTION:
fleegle.mixmin.net.     86400   IN      A       82.133.6.118
drooper.mixmin.net.     86400   IN      A       88.198.22.131
ns1.mixmin.net.         86400   IN      A       82.133.6.118
ns2.mixmin.net.         86400   IN      A       88.198.22.131
asteria.debian.or.at.   6992    IN      A       86.59.21.34

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHaN7qlKZ6CY7Vd0MRCncEAJ9WSx6PY9/aoPgYS3/lvyaEENj3dQCg2odR
5ZCFKH5CHYTHdIRYvPcqzg0=
=NkdL
-----END PGP SIGNATURE-----

--
pub  1024D/8ED57743 2003-07-08 Bananasplit Operator
Key fingerprint = 796F 67E0 E890 A0BB BDAE  EBB4 94A6 7A09 8ED5 7743
uid                            Admin <admin.bananasplit.info>

[ Post a follow-up to this message ]

Re: Attn: Zax

Nomen Nescio

12-20-07 12:15 PM

Zax <admin@bananasplit.info> writes:
 
[vbcol=seagreen]
> You get the key by sending an email to remailer-key@nym.mixmin.net.

But this would flag the sender of the email as the likely owner of any
new pseudonym established shortly thereafter, spoiling untraceability.

Fortunately, your own mail-to-news server has made anonymous email
requests again possible, as they were with anon.lcs.mit.edu of yore.
I send mail such as the following through a chain of remailsrs and
then watch for the results on a.a.m:

To: remailer-key@nym.mixmin.net
Cc: mail2news-20071220-alt.anonymous.messages@m2n.mixmin.net
From: mail2news-20071220-alt.anonymous.messages@m2n.mixmin.net
Reply-To: mail2news-20071220-alt.anonymous.messages@m2n.mixmin.net
Subject:  dd70e5af178a9d04a3ba7e68ab000584b6f652c3
34ff131a

body

But while this works fine for many addressees (such as the finger
server mentioned earlier), it produces no response for this address.
[Why?  Not even the CC: shows up, which is truly mysterious.]

Maybe the simplest thing would be for you to just post the key here on
a.p.a-s.  Thanks!

[ Post a follow-up to this message ]