[147611] in cryptography@c2.net mail archive
Re: [Cryptography] prism-proof email in the degenerate case
daemon@ATHENA.MIT.EDU (Lars Luthman)
Fri Oct 11 00:15:21 2013
X-Original-To: cryptography@metzdowd.com
From: Lars Luthman <mail@larsluthman.net>
To: cryptography@metzdowd.com
Date: Fri, 11 Oct 2013 02:30:30 +0200
In-Reply-To: <52571A15.2060606@sonic.net>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============2018554416625769581==
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
boundary="=-ivtwkaXKv8xBZIgUl0de"
--=-ivtwkaXKv8xBZIgUl0de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Thu, 2013-10-10 at 14:20 -0700, Ray Dillinger wrote:=20
> Wrong on both counts, I think. If you make access private, you
> generate metadata because nobody can get at mail other than their
> own. If you make access efficient, you generate metadata because
> you're avoiding the "wasted" bandwidth that would otherwise prevent
> the generation of metadata. Encryption is sufficient privacy, and
> efficiency actively works against the purpose of privacy.
>=20
> The only bow I'd make to efficiency is to split the message stream
> into channels when it gets to be more than, say, 2GB per day. At
> that point you would need to know both what channel your recipient
> listens to *and* the appropriate encryption key before you could
> send mail.
This is starting to sound a lot like Bitmessage, doesn't it? A central
message stream that is split into a tree of streams when it gets too
busy and everyone tries to decrypt every message in their stream to see
if they are the recipient. In the case of BM the stream is distributed
in a P2P network, the stream of an address is found by walking the tree,
and you need a hash collision proof-of-work in order for other peers to
accept your sent messages. The P2P aspect and the proof-of-work
(according to the whitepaper[1] it should represent 4 minutes of work on
an "average computer") probably makes it less attractive for mobile
devices though.
[1] https://bitmessage.org/bitmessage.pdf
--ll
--=-ivtwkaXKv8xBZIgUl0de
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAABAgAGBQJSV0amAAoJEKZaiTrBe5RLQ3gP/06rMwTrqaFYRqAoxyGadMMv
vSPk3uHvrVNQh25MObQq4Waon7OFwulO5WkzpIEp3b8l1JxOvONIjMRy4XJUZBlh
ghC9EpolyVjQgLPKoXhpGpV13GOgmPz1d1Ekacaqc6lL97S6NPnRH3XHJuxIgI/H
qygYG77lRYSz7l0uyTL5TXYtJofXw1u6hkbjDqj8kpC++QsVx5/djkY4Hmgx5mbM
X255HBv0OhnHWWBBAX+JRPq4fEtdpHuLTTbB27QpfCD+CW+X+rkDW9LGwzaIpmOs
5ktGhciWS7kRbCtPgH/QVaxizJKNlZPDrGt2xGKCKhV0hcDqGgO2XX8KXmUFCiYB
By2K8woVBuaSzxYvsYMtS/96HHPUCH2b899MS2x7jNNf7hb1dTyiXDkQNGXF4PY2
xAX1Vkqbfk3PjxdHGz7ZoHzoE6VQHiVINlTKmsEc65T83nANoalmPmANMreyEB7z
z6l0OaZ/EVNmSLsR1z+yiSCB/mDaV0M5nrs7Q4DSRnlyJOhGUP7snjBNCIIUz/Xr
RIl8bpLHXD0FR1+7t+KkuVHYD013KcYx8VCgXERhXf1fYPc7odV4LHWe2g53hAWS
sklYGHgenFu8FBYenX9knTYqnizyGpku4ln0h7aBm6ZAjwIQMLOh6rmVAa/o7+Kt
ZNtSFY71A/PmO4/xY9XO
=hDsX
-----END PGP SIGNATURE-----
--=-ivtwkaXKv8xBZIgUl0de--
--===============2018554416625769581==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============2018554416625769581==--
