Re: Barcode Email
From: Jean-Luc Cooke (jlcooke_at_engsoc.org)
Date: 07/26/05
- Next message: Luc The Perverse: "Re: Barcode Email"
- Previous message: Luc The Perverse: "Re: Barcode Email"
- In reply to: Luc The Perverse: "Re: Barcode Email"
- Next in thread: Ari Silversteinn: "Re: Barcode Email"
- Reply: Ari Silversteinn: "Re: Barcode Email"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 26 Jul 2005 15:12:15 GMT
In sci.crypt Luc The Perverse <sll_noSpamlicious_z_XXX_m@cc.usu.edu> wrote:
> "Ari Silversteinn" <abcarisilverstein@yahoo.comxyz> wrote in message
> news:b4geqken9wp2.1rnri2c9f93gw$.dlg@40tude.net...
> *snip all*
> I've got it!
> You have a trusted third party server S, which enables secure
> connections via standard web secure stuff. The sender uploads his
> message to the server and then receives encrypted a message ID, which
> is turned into a barcode and a forwarded via unencrypted email to his
> friend/recipient. His friend then scans the Barcode ID, logs into the
> trusted server and goes to his inbox looking for the message with
> this Barcode ID. (He has a user name and password too.)
That might even be useful. But now... the message ID ... how to protect
that? Do we even want to? Either way, this approach actually makes
100x more sense than Ari's "hook'em and crook'em" scheme.
The acid test: will be listen?
JLC
--
- Next message: Luc The Perverse: "Re: Barcode Email"
- Previous message: Luc The Perverse: "Re: Barcode Email"
- In reply to: Luc The Perverse: "Re: Barcode Email"
- Next in thread: Ari Silversteinn: "Re: Barcode Email"
- Reply: Ari Silversteinn: "Re: Barcode Email"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|