1995-02-03 - Re: Remailer Unreliability

Header Data

From: Robert Rothenburg Walking-Owl <rrothenb@ic.sunysb.edu>
To: nobody@myriad.pc.cc.cmu.edu (Anonymous) (Anonymous)
Message Hash: 53ef8c7818601902da6d9b6586634e00ca5ea536453df12f5f14dfceabcbd179
Message ID: <199502030236.VAA22498@libws2.ic.sunysb.edu>
Reply To: <m0raAVp-000vl1C@myriad.pc.cc.cmu.edu>
UTC Datetime: 1995-02-03 02:36:54 UTC
Raw Date: Thu, 2 Feb 95 18:36:54 PST

Raw message

From: Robert Rothenburg Walking-Owl <rrothenb@ic.sunysb.edu>
Date: Thu, 2 Feb 95 18:36:54 PST
To: nobody@myriad.pc.cc.cmu.edu (Anonymous) (Anonymous)
Subject: Re: Remailer Unreliability
In-Reply-To: <m0raAVp-000vl1C@myriad.pc.cc.cmu.edu>
Message-ID: <199502030236.VAA22498@libws2.ic.sunysb.edu>
MIME-Version: 1.0
Content-Type: text/plain


> 
> What if it was possible to specify an alternate remailer?  In the case that
> a remailer went down, you could specify an alternate.  For example:
> 
[ Snip! ]
> 
> If foo.com was down, the message would be delivered to bar.com instead.
> The PGP message would have to be readable to both of them, so it would
> decrease security, but reliability would be better, especially for
> reply blocks.  Comments?
> 
Hmmm. Not as secure, but how about this... (a kind of script)

begin A
  if active(mailer@foo.com) mail(mailer@foo.com,B,C)
  elseif active(mailer@bar.com) mail(mailer@bar.com,B,C)
end

begin B
 { next block of scripts for chain... remailer would encrypt B and C
 blocks for appropriate mailer }
end

begin C
 { this block would be cargo... could even contain multiple messages? }
end

That's a pseudoscript, but you get the idea... (no pun intended ;)







Thread