new remailer: remailer@xs4all.nl
Robert
esub cut hash post repgp remix reord ext max test inflt75 rhop5 klen1000";
Type Bits/KeyID Date User ID
pub 1024/D6D729E1 2003/09/22 garsmano <rema...@xs4all.nl>
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3i
Comment: Requires PGP version 2.6 or later.
mQCNAj9vfZoAAAEEAOhF82hFTYZnKwzVbJzq4mCGYbIWO/OkalC+cuA4MO+OvcTE
iV7LGnUPU+b0/yjvl2bCUHYEtdURkN75mun28c19cLOcPz2yIEGCpKAp9y+fTiOo
ZUOZERam4d90x0P4XQ8AqcU+ohgSEioVrvlqjAcwnqtaEAKWUjQulqzW1ynhAAUT
tB1nYXJzbWFubyA8cmVtYWlsZXJAeHM0YWxsLm5sPokAlQIFED9vfZs0Lpas1tcp
4QEBGvEEANIgAeiZ0cWLHYmlK93nvmexxktR69w1Bk0PoVZt75T35g84zBf+E4sf
ZOiF6sCTFNRcWOfEdIuxeuR7ebOYov/HRmKPOoudKVSJhOAHDC5e0OKxdcl4zYsF
xjyYP63LanbdUMxRkeNW9YMlsO8Kn8Ci2sleBJ5PIin3945FpHwE
=D2/0
-----END PGP PUBLIC KEY BLOCK----
garsmano rema...@xs4all.nl 0497225bf2e5ec2bb5f7f368b9f09492 2.0.4b45 CN
-----Begin Mix Key-----
0497225bf2e5ec2bb5f7f368b9f09492
258
AATZ2hCmv5MqTKZcrDVn5Blupatg+ZCuDu4rmY23
MOzhDWFxqF8/PeekJa6zHhF2EbkopuFwaZNGJjZ/
GcUm11uRu7NYaEDp7sNVWiANi6eS5sALc+DmKbNV
fFia7TV5q2B+lr3qwOvDECHZyZ7gAixj0nr9xvjC
75FEVhjfCbegTQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAQAB
-----End Mix Key-----
Frog-Admin
On Tue, 23 Sep 2003, "Robert" <m...@my.org> wrote:
>$remailer{"garsmano"} = "<rema...@xs4all.nl> cpunk mix hybrid pgp latent ek
>esub cut hash post repgp remix reord ext max test inflt75 rhop5 klen1000";
0) WELCOME
1)
GENERAL
Addresses In Header Maximum: 15
Crosspost Maximum: 10
You'll be a magnet for abuse
(Frog's corresponding values are 5 and 5)
2)
NEWS
News Posting Route (mail2news): mail...@anon.lcs.mit.edu
NAN is down, so putting it as sole m2news will result in post loss
better put more than 1 anyways, and preferably working ones
eg: mail...@dizum.com,mail...@frogadmin.yi.org,mail...@freedom.gmsociety.org
I just arrived, so that's a quick look, but everything else looks OK
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBP2+Q7IDgT488d3zFAQFIQAgA14VgposA1T7NZZZZAP2kBBx0rOxTs9p6
ChAy9yvJThrvNw1CumuHlgi/30AkJBoaudbRPufWgl9idfKdQSTd4RpSWy/fP5ri
4BznqaPwAMreDZ5ImBwbNRT3/9Mtew/GsGaE0oN20xL+GDZXYTCnQET1zbpmoRKX
e0niVDT0Wev4MevoR/H7leOZFDi2czNB8WYcKxr0AmUpkKbSskihxjIwoO2I4Wwg
m2mUVXPKkMNPg+SS8bMhh+iv2cgmuisyf1NbhNlqnhTLarlaV/nuBr92JpiUMS95
sDe/HZcvx2GZuN3sogilLdpixrecMxOQlCXJSRr+FM/cA/OkvVgRMg==
=MdYn
-----END PGP SIGNATURE-----
BiKiKii-Admin
No effort was made to verify the identity of the sender.
--------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 23 Sep 2003, Robert wrote:
>$remailer{"garsmano"}
>post
>
Greetings,
This will not get you too far:
Subject: Re: remailer-conf [garsmano]
NEWS
Anon-Post-To Supported (post): True
News Posting Route (mail2news): mail...@anon.lcs.mit.edu
as LSC is currently dead.
May I suggest you either pick another M2N gateway or use a "multiple".
See the remailer-conf of BigApple, BiKiKii, Italy, etc. as examples.
Good luck.
Cheers,
BiKiKii
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBP2+kRPBluLRpZm7PAQFMVAgA0d7mi3I846itPcTNcEYBr8trCKDAcMuE
V/Bw+YoZTOmdYZsT0oejaBRmsA+X6prgg9RnX6dMAU4agZHe/bsGgwtdl4lOjnHT
FVpYqxgjfl5woCyCkumMgtuQ2sraqYRVLOcMmPscsjqD+Q7zEF5vRsZ6rrVsSPfl
bWas61XbzdU/sb2yvIXGWOJmKZwJa6Y1kupwEYrzScvwE5UNEYWVJRitIICtRb3f
9lbLurg42f7JG/WRxqHRrOZoemygDBIdDMy42jWjoEzJwC9gEyXQntpqEuaCbmB9
3P0UKfstoaUjcYmP7a3l3S/JaWO25tytDbX+HLovqTuj2QG8Z99cKg==
=WdwR
-----END PGP SIGNATURE-----
Robert
robert
"BiKiKii-Admin" <Use-Author-Supplied-Address-Header@[127.1]> schreef in
bericht news:F26DF...@bikikii.ath.cx...
Frog-Admin
On Tue, 23 Sep 2003, "Robert" <m...@my.org> wrote:
>$remailer{"garsmano"} = "<rema...@xs4all.nl> cpunk mix hybrid pgp latent ek
>esub cut hash post repgp remix reord ext max test inflt75 rhop5 klen1000";
One of my subsystems choked on your PGP key, whose trailing armor is incomplete (missing a "-").
I don't know if my program was too picky, or if there might be consequences with some versions of PGP, but it normally needs 5 "-"
Same shows on your announcement post, BTW:
...
xjyYP63LanbdUMxRkeNW9YMlsO8Kn8Ci2sleBJ5PIin3945FpHwE
=D2/0
- -----END PGP PUBLIC KEY BLOCK----
^
should be v
- -----END PGP PUBLIC KEY BLOCK-----
Please correct, just in case it would really matter for somebody
I saw no other problem,
and according to http://frogadmin.yi.org/Thesaurus/index.html#Error
you are holding proper MIX keys for all remailers
(Because of PGP 2.x, I don't know for PGP)
Your stats look good: definitely a good start / welcome
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBP3DKnYDgT488d3zFAQGt1wgAl/utNPWG8AN/jnLTWGmtazuINNQDEIeD
gE1wuEajOyE9aJinJO2kt28b64rAtmnsQq6ZX7Qf3Y5QDDueWp2hQ5dMKMTn0Rrt
c2MQWt03QSUlSubcOhQFmCSCqtGOdl8ykX7cCOzucJXjiXD+1viBqOmpw2Ne0fNQ
u8pgvF8QZ2UAfh6Je0Tr5vuph7pyWcZTltoPIw1wSyRBrR6UYqnm4b549eGFBmlc
S6YfaHGoVlap7gaSnPu7o013HAt3th6dUJ4hlEtGQkjl+tcsA9FEbBRgAKGEqGIg
S6PzvUgG2jUA1HFJ6IqSFMB7NxIsxfVNMoqlcMQBFMcfL2RtnXWyyA==
=JOkC
-----END PGP SIGNATURE-----
Robert
Had problems with pgp cpunk msg's and had posted some questions about it
here.
Hadnt read your post yet.
Maybe this will fix it..
Thanks..
"Frog-Admin" <Anonymous...@See.Comment.Header> schreef in bericht
news:OWQ53TZO3788...@Gilgamesh-frog.org...
Robert
"Elisabeth van Aaring" <Ev...@gmx.net> schreef in bericht
news:6m63nvostlkm5mg25...@4ax.com...
> Robert wrote:
>
> > $remailer{"garsmano"} = "<rema...@xs4all.nl> cpunk mix hybrid pgp
latent ek
> > esub cut hash post repgp remix reord ext max test inflt75 rhop5
klen1000";
>
> Is "garsmano" in any relation (same operator?) to *dizum*, formerly
> known as *replay*? This comes to my mind because:
>
> - dizum/replay is located in NL
> - Replay used xs4all
> - RSA-key is 1024 bits, too
>
> Perhaps Alex can comment on it?!
>
Robert
Somehow I still have the problem as posted in Subject: again a question
about running a remailer.
copy below:
Last posting didnt get any reactions at all..maybe just got lost in the
waves..
I have the Reliable 1.05 remailer (pgp 2.6.3i) up and running at
rema...@xs4all.nl
.
Mixmaster messages seem to work fine as the remailer processes a few 1000 a
day.
However, I think there is a problem with CPUNK messages, many get rejected
because of "unable to decrypt".
When I check the key id's of the remailers pubkey in Reliable's FILES
section against what pgp extracts from the pubkey.pgp key id's are the
same.
When I send a msg (pgp encrypted with -eat & remailer pubkey & correctly
formated)) to the remailer I can see it being rejected and I find it back in
the remailers trash.
When I decrypt the message in a dosbox decryption works fine, so it seems
the combination of keys in the secring and pubring for the remailer is ok.
All paths's etc are set ok.
Could it be a PGP version issue? In the options of Reliable it says: 6.3.x
most variants..
Does anyone have any idea or suggestions?
Frog-Admin
On Sat, 27 Sep 2003, "Robert" <gars...@xs4all.nl> wrote:
>Hi just read you reply...
>Had problems with pgp cpunk msg's and had posted some questions about it
>here.
>Hadnt read your post yet.
>Maybe this will fix it..
I saw that a reinstall cleaned up the leftover from a previous PGP 5 install.
Anyways:
there was no chance that modifying your remailer-key reply,
or even modifying the .asc for your PGP key
or even reloading your PGP key
would cure anything
I would have thought of systematic typo when enterung your passphrase....
Anyways, you got everything fixed: good
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBP3gqWoDgT488d3zFAQHbqAf+PZYuU9EWgcDArSI96VvyjyHYCEi361oe
U7w96YWZG6fzwMHwm9p/ZL0HP0wQdQX1FbuWwytU2AnwaCgXVbvYnB1oivuHaFiF
Zp2utXVYdIECwIG6aR02G09lncX75i64PRUaCJzQnwEGVNwJKEA0Fq92yHlIf+/z
KIREDNukC73gQXeZ20tDm4hO7vlwDsnc6Tib9hZVwN4GE486eNPoO4bbFncXVu6k
f3Hi2ooqS3DxU6H01M3vum0cWNiyyIjRRzPH2SL7Hsg6aDG5RkMBk4xKNqkRSS1Q
0DCSYu0lLwnGC+FoOrdV09GyGGJ4nbyzlfeUDwaZdMOB2gywj+/4cg==
=T5Kj
-----END PGP SIGNATURE-----
Anonymous
frog-admin posted this message. It is well known that he is a liar
and the worst abuser of the remailer network in its history.
A couple years ago, I used frog quite regularly for anon posting.
One of my messages, in this group, was followed up by another anon
poster who, it was clear, knew that I was the actual source of my
article. That was it for me and frog. I will never support him or
use any of his services again.