Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: Spook MIME Boundaries
Date: Fri, 20 Aug 2004 02:01:34 +0200	[thread overview]
Message-ID: <87vffe3cf5.fsf@deneb.enyo.de> (raw)
In-Reply-To: <87oel6dd69.fsf@stark.xeocode.com> (Greg Stark's message of "19 Aug 2004 17:35:10 -0400")

* Greg Stark:

>> 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.

No, you just look for "BEGIN PGP MESSAGE", and then you store the IP
addresses involved (and, if possible, email addresses seen earlier on
the same connection).  Traffic analysis is an extremely effective tool
for many applications, and concentrating on encrypted traffic reduces
the data set very nicely.

Something like

-----BEGIN PGP MESSAGE-----

jA0EAwMC4/o8ylG480Ngye38oMxjWBRvkIexOLnESJ07wjS18zZLJJnHkX8CBFG0
8CV61rhpf9CyIj/vZp3TZZhSRjPRuEhHgQ4fE+zUDY5xW4Kx4CffXzJSFEKMcTf6

in your signature would fool some *real* heuristics.



      parent reply	other threads:[~2004-08-20  0:01 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
2004-08-19 21:44     ` Greg Stark
2004-08-20  0:01     ` Florian Weimer [this message]

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=87vffe3cf5.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --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).