From: | Jeffrey Mach <mach@****.CALTECH.EDU> |
---|---|
Subject: | Re: Business? |
Date: | Tue, 3 Mar 1998 11:57:18 -0800 |
> *****Private: Faerie
> >>>>>[++Encryption Daedilus Routine++ At the moment, the two jobs I
have
<<snip>>
> will be forthcoming but at this time these have priority. ++End
> Encryption++
>
> If interested in either please let me know.]<<<<<
> -- Micheal Morningstar <00:26:15/03-03-2059>
A little niggling point.
There was a rather big discussion about a year ago regarding encryption.
At the time there was a growing use of more and more encryption "headers"
that people were using to show how _really_ encrypted their posts were.
While not quite so bad that the Encryption to message ratio was falling
below 1, it was pretty bad. General consensus on the list was that the
use of the *****PRIVATE: header was a sign of significant encryption,
rerouting, etc. and that per list rules already put the message off limits
from anyone but the recipient other than by the specific approval of those
involved. If one needed a character to get ahold of a message that wasn't
sent to then, then it didn't matter how much encryption was put on the
message anyway. You simply had to stipulate that it was defeated (with
the necessary implication of the proficiency of the deckers involved).
So, therefore, additional encryption headers were basically pointless and
should not be used, unless under very special circumstances. Say, for
example, if they were used internal to a post sent to many people (or
publicly) for "eye's only" access to certain parts of the message.
Since the message is already *****PRIVATE to Faerie, then I don't see the
reason why the section you encrypted needed to be any more private than
the rest of it. (As a side note, since I know a little more about the
character than you do, too much technomantic legendermain may make the
post quite unreadable for her...but I guess that is up to Jaimie to
decide.)
--My two yen
Jeff