Delivery-Date: Thu, 24 Sep 2015 16:58:48 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id A59951E13B5;
	Thu, 24 Sep 2015 16:58:46 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 42B6F3723B;
	Thu, 24 Sep 2015 20:58:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 870C63723B
 for <tor-talk@lists.torproject.org>; Thu, 24 Sep 2015 20:58:38 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id DUeCwpvP2aH3 for <tor-talk@lists.torproject.org>;
 Thu, 24 Sep 2015 20:58:38 +0000 (UTC)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com
 [IPv6:2607:f8b0:4002:c07::233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 615DE371D6
 for <tor-talk@lists.torproject.org>; Thu, 24 Sep 2015 20:58:38 +0000 (UTC)
Received: by ykdg206 with SMTP id g206so95162209ykd.1
 for <tor-talk@lists.torproject.org>; Thu, 24 Sep 2015 13:58:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=p2OYIdg/NZVrQUfyfAFIs7Lpo/DztjwiqRqAPIKM0MA=;
 b=UGAAnkD2jB0jSvy4sOnJF2Y8XNYih/jRQMHMgBZmhAqernvi2LkMP7RMFF4HUbUQr6
 NS2Hdv4UZ9ZQdGXAl0gq/+j6kytmpBi5g0OKKa+VYXA/Cy2dmm9gCl77zdxk95t0m8nS
 ZrzydHnUfCePoerzlFNqaYpz2NSBxOT0ilEA+aeUqGYJLPY+ovCQjZuR5XDRMAb4uBiX
 +GUnm6wbwg2UYBGUtumREUPifueBfvSSdp/jv/hMJMpJwey5ePvbwqOQVvL0hD+EO96r
 3TacLxTpBRrjIMqNae5i7APeiHdoa6T0mLg0P1zMXcdZYA4CU4/GwsAAzj5CdrC2ptKR
 C49g==
MIME-Version: 1.0
X-Received: by 10.170.53.209 with SMTP id 200mr1662968ykv.39.1443128316097;
 Thu, 24 Sep 2015 13:58:36 -0700 (PDT)
Received: by 10.13.246.70 with HTTP; Thu, 24 Sep 2015 13:58:36 -0700 (PDT)
Date: Thu, 24 Sep 2015 21:58:36 +0100
Message-ID: <CA+QqAMM2WtEAHY_-+wOLba6=yithdTrB9+kRCJZVcJ5j9V9Fsg@mail.gmail.com>
From: Darren Allen <darreneallen@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Server / Browser html PGP Encryption
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hi,

I've been trying to think of ideas that would aid the Tor world and a
random idea occurred.

Once a user has joined an Onion web server, they download the servers PGP
Public Key, and upload their own PGP Public Key.
All HTML commication, .jpg images, etc are then encoded by the server using
the user's Public Key.

The user has their private key attached the to Tor Browser, (The browser
could generate a random PGP key set for each Onion site), which then
decrypts the incoming communication back into HTML etc to be displayed in
the browser.

All new page requests, sent by the user, are likewise encrypted using the
Onion sites Public Key, and decrypted by the server.

This would require altering the Tor Broswer, and web-hosting software, but
would essentially allow SSL encryption for the Tor network.

Regards,

Darren Allen
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

