|
Home > Archive > Anonymous Servers > February 2006 > pymenu - simple mixmaster menu
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
pymenu - simple mixmaster menu
|
|
| admin 2006-02-17, 11:08 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I put up a version of Sofa King's PyNnonymous that uses a simple
ncurses-type menu.
This way, you can use any number or combination of remailers while still
getting the automatic header creation.
It's at http://www.eelbash.org.
Follow the Scripts linke to PYMENU.
Here is an example of using it:
user@2[~]$ bin/py/pymenu
Specify the chain - up to 19: *****
(you can just press the enter key if all you want is the exit remailer)
Exit Remailer? dizum
Copies? 6
mixmaster -m --chain=*,*,*,*,*,dizum --copies=6 temp.txt
Is this what you want? Y or N
If you enter N, it repeats the prompts. If you enter Y, it calls mixmaster
and sends the message.
The From header will be whatever is in our message, if anything.
Same for Subject and any other headers.
Please let me know how it works out if you try it.
As always, use at your own risk.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD9J5mEC+g9Qawm6QRAtqgAKDAL+kR0ocA
xM/dJjjX1qYO6VPPagCg2gKO
nM65Atlna8NV4eVQEJTBaSs=
=zIJo
-----END PGP SIGNATURE-----
| |
| Anonymous via the Cypherpunks Tonga Remailer 2006-02-17, 11:08 pm |
| In article <ML7ACZXD38764.4898263889@anonymous.poster>
admin <admin@eelbash.org> wrote:
>
> As always, use at your own risk.
Using anything from a person with such a long reputation of being an
enemy of free speech is definitely a risk.
| |
| Borked Pseudo Mailed 2006-02-17, 11:08 pm |
| admin <admin@eelbash.org> wrote:
> I put up a version of Sofa King's PyNnonymous that uses a simple
> ncurses-type menu.
I think I'll wait for Sofa King to release any new versions. I wouldn't
want to find that your update changes "bad" words into [EELBASH_TAGS]
| |
| TwistyCreek 2006-02-17, 11:08 pm |
| On Thu, 16 Feb 2006 14:46:07 -0700, Borked Pseudo Mailed wrote:
> admin <admin@eelbash.org> wrote:
>
>
> I think I'll wait for Sofa King to release any new versions. I wouldn't
> want to find that your update changes "bad" words into [EELBASH_TAGS]
The script is easy enough to read. If there were any civil remailer code
in it you would spot it.
| |
| Borked Pseudo Mailed 2006-02-17, 11:08 pm |
| TwistyCreek wrote:
> On Thu, 16 Feb 2006 14:46:07 -0700, Borked Pseudo Mailed wrote:
>
>
> The script is easy enough to read. If there were any civil remailer code
> in it you would spot it.
Is that so? <evil grin>
Would you be shocked to find that the original by "Sofa King" had a little
flag to tell the difference between posts sent with it and posts sent with
other clients? And I'm not talking about the borked up references header
problem, although it's related. Maybe intentional.... maybe not.
Just because everyone can read the code, doesn't mean everyone can
understand it. I didn't say anything until now because I doubted anyone
would use it when it was found to be flawed. And "Sofa King" apparently
evaporated. But there **IS** a little tell in every message posted with
that script, even when the headers aren't obviously messed up.
As a game, or a test if you like, let's see if anyone else can spot it.
And by the way, the latest Eeltard atrocity has nothing at all to do with
ncurses no matter what that freak of nature says out of sheer ignorance.
And it's HORRIBLY flawed above and beyond how the original was. Eeltard
really shouldn't be allowed to play with this stuff, and anyone who uses
ANYTHING coming from that remailer needs their head examined.
I refuse to detail the additional problems that infest the Eeltard
versions of these utilities because it would encourage the idiot. I'll
post the little flaw in the original after I have a tiny bit of fun with
it, just so people will know I'm not bullshitting. But as much as it pains
me to say it, beyond that...
"You have been warned!"
<grinning, ducking, and running>
| |
|
| On Thu, 16 Feb 2006 23:47:25 -0700 (MST), Borked Pseudo Mailed wrote in
Message-Id: <0865c635968f373647a6c91833c7f103@pseudo.borked.net>:
> As a game, or a test if you like, let's see if anyone else can spot it.
You've beaten me. 
I even hexdumped the output file and I still can't see anything wrong
with it. It's a nice little script even if it does have a secret flaw.
--
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>
| |
| Borked Pseudo Mailed 2006-02-17, 11:08 pm |
| Zax wrote:
> On Thu, 16 Feb 2006 23:47:25 -0700 (MST), Borked Pseudo Mailed wrote in
> Message-Id: <0865c635968f373647a6c91833c7f103@pseudo.borked.net>:
>
>
> You've beaten me.
Ok, I won't torture you any longer. <grin>
Check messages processed by the original Pynonymous script and you'll see
that it appends a single, extra whitespace to the end of the last
References header entry. I've already seen a couple of these messages
appear here in this group, so it's obvious that little "flag" is passed
through the network at least some of the time. But from my VERY
brief testing, it varies with Mixmaster version for some reason. So does
the "munged third Reference" problem I believe. All version dependent I
think.
It's almost as though this long header problem was a thorn for Mixmaster
developers too, and a couple different things were tried to solve it. With
only slightly more success than the recent offerings of message
"pre-processors" (for lack of a better term). I don't think Mixmaster
handles them the "right way", if there even is such a thing, but it's
at least consistent inside major version numbers. Don't know for sure, I
have neither the time nor the inclination to diff the various Mixmaster
source codes.
> I even hexdumped the output file and I still can't see anything wrong with
> it. It's a nice little script even if it does have a secret flaw.
The only reason I saw it at all is I'm working on another project that
coincidentally has to deal with text data being split across multiple
lines. I had already dealt with a similar issue, and while I was skimming
through script the section of code that does it just "stick out" a bit.
It's even out of character with the rest of the script, which as you say,
isn't a bad bit of work at all.
The problem is in the anon_header() function, around line 265-266 if
memory serves. It tests for the existence of a closing '>' bracket and if
found, appends a space character. Probably to compensate for the way Pan
replaces spaces with tabs when it "folds" long headers. Probably an
accident, but it would help partition users none the less.
Actually, I think the whole thing can be solved, munged references and
all, by deleting the two lines that test for the closing '>' and folding
headers "properly" with a <CR><SPACE> combination. But I haven't tested
that theory. ;)
| |
| Anonyma 2006-02-19, 8:22 am |
| In article <600732e59398aefaec6c65068d2c1f40@pseudo.borked.net>
Borked Pseudo Mailed <nobody@pseudo.borked.net> wrote:
>
> Ok, I won't torture you any longer. <grin>
>
> Check messages processed by the original Pynonymous script and you'll
> see that it appends a single, extra whitespace to the end of the last
> References header entry. I've already seen a couple of these messages
> appear here in this group, so it's obvious that little "flag" is
> passed through the network at least some of the time.
This extra space may also occur with cotse's news2remail. Let's see if it
does in this case.
| |
|
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 18 Feb 2006 10:11:37 -0500, Anonyma wrote:
> In article <600732e59398aefaec6c65068d2c1f40@pseudo.borked.net> Borked
> Pseudo Mailed <nobody@pseudo.borked.net> wrote:
>
> This extra space may also occur with cotse's news2remail. Let's see if it
> does in this case.
I put in a change to remove the space at the end of the last reference
header and the tests indicate it is working.
This will be another test.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD9048EC+g9Qawm6QRAuoZAJ9Oxd1thpP1
e5sc+WE04PBDGPkAUgCaA193
9sYBSiKUa4MLk9IulDGRyMo=
=LWhr
-----END PGP SIGNATURE-----
|
|
|
|
|