From: Greg Stark <gsstark@mit.edu>
Cc: Greg Stark <gsstark@mit.edu>, Gnus Mailing List <ding@gnus.org>
Subject: Re: Spook MIME Boundaries
Date: 19 Aug 2004 17:35:10 -0400 [thread overview]
Message-ID: <87oel6dd69.fsf@stark.xeocode.com> (raw)
In-Reply-To: <87r7q2yi1n.fsf@deneb.enyo.de>
Florian Weimer <fw@deneb.enyo.de> writes:
> It's a rather old idea:
>
> <http://www.splode.com/~friedman/software/emacs-lisp/src/spookmime.el>
Indeed I think it was that version that inspired me to write the hook for
ding. If I had remembered that I would have given credit. I'll add a comment
to my source so I don't forget again.
> More effective would be BEGIN PGP MESSAGE line, followed by random
> base64 encoded junk.
At this point anybody listening would pretty much have to be able to base64
decode at wirespeed anyways.
--
greg
next prev parent reply other threads:[~2004-08-19 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:09 Greg Stark
2004-08-19 20:44 ` Florian Weimer
2004-08-19 21:35 ` Greg Stark [this message]
2004-08-19 21:44 ` Greg Stark
2004-08-20 0:01 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oel6dd69.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).