From owner-freebsd-chromium@FreeBSD.ORG Fri Jul 8 01:56:09 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9D541065673 for ; Fri, 8 Jul 2011 01:56:09 +0000 (UTC) (envelope-from evanm@google.com) Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by mx1.freebsd.org (Postfix) with ESMTP id 7047F8FC13 for ; Fri, 8 Jul 2011 01:56:09 +0000 (UTC) Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id p681jkec016196 for ; Thu, 7 Jul 2011 18:45:46 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1310089546; bh=A4m0wY6b0KYIAoUoqYedDti9BYE=; h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=Td+51lXMdAv1IYK62NsaLypCbvJdhOM854lqIkajycvtN5Z8TKEXVUZMFPHCtTTB2 3ar/oqDQJ9H8OomtC/0Lw== DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:sender:in-reply-to:references:date: x-google-sender-auth:message-id:subject:from:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=uNHysxWhcxjZgpijNKwqAx6+V39/UypqXgq3mR3rjS/nh+B+GtmTkHIR0l0Vy517R y3wGNa1aYjENHpaeC1PEA== Received: from gxk9 (gxk9.prod.google.com [10.202.11.9]) by wpaz5.hot.corp.google.com with ESMTP id p681jbUX020327 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Thu, 7 Jul 2011 18:45:45 -0700 Received: by gxk9 with SMTP id 9so848075gxk.40 for ; Thu, 07 Jul 2011 18:45:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LdgWGZLGehtqkfpEz9g4egi1vyDxEbB2Blgdh79GWN4=; b=GPEIApmmXfenNQMFi/toYf99Nn8qOViR7rHi1Xdp6izXZNzqU2/lw4j2IoCuzOTXHi Xhgnl1xwKT+nE5arw5Nw== MIME-Version: 1.0 Received: by 10.101.189.34 with SMTP id r34mr1271078anp.77.1310089544748; Thu, 07 Jul 2011 18:45:44 -0700 (PDT) Sender: evanm@google.com Received: by 10.100.172.13 with HTTP; Thu, 7 Jul 2011 18:45:44 -0700 (PDT) In-Reply-To: References: Date: Thu, 7 Jul 2011 18:45:44 -0700 X-Google-Sender-Auth: cgZAiMeIHhdlBp3Eg6G7k5x6ug0 Message-ID: From: Evan Martin To: Joseph Mingrone Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true Cc: chromium@freebsd.org Subject: Re: Is synced data encrypted? X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 01:56:09 -0000 I am not familiar with the code, but I believe: - the sync protocol works over https only - the data as stored on Google's servers is not encrypted in such a way that Google can't see it http://www.google.com/support/forum/p/Chrome/thread?tid=3D646b7f8602a91184&= hl=3Den (it used to be the case that your bookmarks would show up in google docs, for example) - recent versions of Chrome can use a local password to encrypt your passwords before sending to Google On Wed, Jul 6, 2011 at 3:37 PM, Joseph Mingrone wrote: > When using the sync feature within chromium, is the data encrypted > locally before being sent to google's servers? =A0I see in the dialog > that passwords can be encrypted, but what about the other data? =A0Are > there details available describing the encryption? > > Thanks, > > Joseph Mingrone > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.or= g" >