[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Encrypted Web Pages?
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Encrypted Web Pages?
- From: "F. Fox" <kitsune.or@xxxxxxxxx>
- Date: Mon, 17 Dec 2007 17:12:55 -0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Mon, 17 Dec 2007 20:13:06 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=ou65Mg9RdeWRQA/Fn04WBt4TPq/1Kz+gO0a1yZbsGX4=; b=uh9FXf8nb48BqPEdEQ+jPQzVqXcgBUl55kKIxs7Aoxtgvko6vCGb3AwEu24byRhntYqlrJmiDwCfJ6wFgtTjM9VsN10LpCoCRTUndHrma9MxyPqWyjDy70/noCb9QOrY5c8cA+6KARy4K2+Nqsjn/7SbweOLDIneIXGFnKRbiAI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=QP3foI4bjYKdM0PAUKw33gXtLFpKJOlem1Naew4CGVtR8+jdA9fbWnDR6Xlj07SY76Qm1nxiBIdEAkbJaLvI/YHHWx49odA1b7/NBbNqCG/GIbAIWZ8yl19Ro93P9yKu5LzMvbbOOxp2tInCg0ykAYrij+/gqmJdEnMcGHe5Cg8=
- In-reply-to: <229981.46073.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <229981.46073.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Thunderbird 2.0.0.9 (Windows/20071031)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Martin Fick wrote:
> --- "Jonathan D. Proulx" <jon@xxxxxxxxxxxxx> wrote:
>
>> On Mon, Dec 17, 2007 at 09:25:13AM -0800, Martin
>> Fick wrote:
(snip)
>> HTTP is a publishing mechanisim in which you
>> usually want people to see it, or restrict
>> viewing to a group and is thus centered
>> around one to many (or in "web2.0" land
>> many to many) communication lines.
>
> Yes, but I really am just talking about a
> more secure version of the one to many
> scenario where you don't trust the server!
> The many, of course, can always be one.
>
(snip)
This is a good point. Since crypto is being used to enforce access
rights, read permissions can be wide open, as can be file creation (but
not modify, or delete). Only the intended recipient would be able to
read the message, anyway.
So, maybe an HTTP-based solution would work, after all... it could be as
simple as having a script on the server, which would allow file upload
according to the permissions in the previous paragraph.
- --
F. Fox: A+, Network+, Security+
Owner of Tor node "kitsune"
http://fenrisfox.livejournal.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBR2celuj8TXmm2ggwAQgb1A//Xj5RhcnmSyJ5WBtx7lSk8hxAFquc4tB7
E0ge/cgHUehfQjGaCxVD6+iOJY9pjBeMZtjzWLbGqhq1t/xVMPKDcuLtyom37Qj3
vhqt96P8JvUL5/WZ2HynhXDL3At+40SB5pyRn7P4PrzaZaqdLYvPn8mu9K7RImAl
qJ4IWZjG34gRm1pyQe9yQZwk5wjmdh7riecaruwOnsP3KfE5pdqT7xzt1f47KID1
EEen/WboRyqCnkryYxC8YxwjGmCNgHtzbRstd3UW0jlcqa1BwGAljGJIyNKPA2ep
AYdm38BFfCAZjk37uzgygkdqQykk5As4svbXibLbqSa5QWIOU1vxEmMMcqIOaTFK
CVAPNPtZoqdxoPCvnugNKE0covfiCDanomexodSvZ/KROFNlBsL33r+gb52Wtobe
wfkCNUAsOSf+77Uy9PB6LGperQfp2a5cnAVr6AMXNPono5EA3ruNB6uWGHtOXnB6
4QQ54qaii/D6Ho+EhqKfSGX+IveKBcfDEmpAM/km/jbgFkeLoHFOZHM60Gf2zOLS
/g7lteG4W6LvvFLHc/3XKoDtlMyfpeDE4ZxK3lEwMSddV0yzNMFXnNi2t4P4zP/q
6iMmz4SvP1lHeeAPXcp4fQrl8kX42+5R8jA5sRhHa9kOLG4R5Sggu8KonaCO3OoU
t9O+awnShjY=
=1Kln
-----END PGP SIGNATURE-----