From owner-freebsd-chromium@FreeBSD.ORG Mon Jul 4 11:06:32 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 880E71065673 for ; Mon, 4 Jul 2011 11:06:32 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5D57F8FC19 for ; Mon, 4 Jul 2011 11:06:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p64B6W1J040009 for ; Mon, 4 Jul 2011 11:06:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p64B6V68040007 for chromium@FreeBSD.org; Mon, 4 Jul 2011 11:06:31 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Jul 2011 11:06:31 GMT Message-Id: <201107041106.p64B6V68040007@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Cc: Subject: Current problem reports assigned to chromium@FreeBSD.org 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: Mon, 04 Jul 2011 11:06:32 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/157730 chromium www/chromium: x11_util.cc X Error detected (BadAccess 1 problem total. From owner-freebsd-chromium@FreeBSD.ORG Wed Jul 6 23:07:00 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 B91CC1065674 for ; Wed, 6 Jul 2011 23:07:00 +0000 (UTC) (envelope-from jrm@mingrone.org) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 58F128FC0A for ; Wed, 6 Jul 2011 23:06:59 +0000 (UTC) Received: by wyg24 with SMTP id 24so392553wyg.13 for ; Wed, 06 Jul 2011 16:06:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mingrone.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=oyH+uRnhvsmIFo1cqUoPafSXnghNAy7HKjClEfseNRA=; b=SR648GC3hozSCLIBXJFoSn0EaxL3wcWnPXgMuO/0hDK0rxpDxdNh2L6vIpqSX3/8y5 uMW72KLjPD+AU4PD/qvopgj1/jO8qmrKXRtk/RFmXu3UkE87JRTIrcYNhbdb2mrn0uBa +LEQ8+awPS/YNGQVnWtPUMfyLGYgn/ReHcFnI= MIME-Version: 1.0 Received: by 10.216.221.33 with SMTP id q33mr5837882wep.90.1309991872834; Wed, 06 Jul 2011 15:37:52 -0700 (PDT) Received: by 10.216.134.209 with HTTP; Wed, 6 Jul 2011 15:37:52 -0700 (PDT) X-Originating-IP: [24.222.128.165] Date: Wed, 6 Jul 2011 19:37:52 -0300 Message-ID: From: Joseph Mingrone To: chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: 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: Wed, 06 Jul 2011 23:07:00 -0000 When using the sync feature within chromium, is the data encrypted locally before being sent to google's servers? I see in the dialog that passwords can be encrypted, but what about the other data? Are there details available describing the encryption? Thanks, Joseph Mingrone From owner-freebsd-chromium@FreeBSD.ORG Thu Jul 7 10:38:06 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 0602D106566B for ; Thu, 7 Jul 2011 10:38:06 +0000 (UTC) (envelope-from schrodinger@konundrum.org) Received: from crux.konundrum.org (crux.konundrum.org [91.121.150.76]) by mx1.freebsd.org (Postfix) with ESMTP id 6238E8FC14 for ; Thu, 7 Jul 2011 10:38:04 +0000 (UTC) Received: from crux.konundrum.org (localhost [127.0.0.1]) by crux.konundrum.org (Postfix) with ESMTP id 5CEA01CDAF2 for ; Thu, 7 Jul 2011 11:21:56 +0100 (IST) X-Virus-Scanned: amavisd-new at konundrum.org Received: from crux.konundrum.org ([127.0.0.1]) by crux.konundrum.org (crux.konundrum.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvFzKSNnYgxF for ; Thu, 7 Jul 2011 11:21:56 +0100 (IST) Received: from localhost (unknown [109.255.232.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: schrodinger@konundrum.org) by crux.konundrum.org (Postfix) with ESMTPSA id A64A91CDAF1 for ; Thu, 7 Jul 2011 11:21:55 +0100 (IST) Date: Thu, 7 Jul 2011 11:21:48 +0100 From: Schrodinger To: chromium@FreeBSD.org Message-ID: <20110707102148.GA7659@defiant.hyperion.xnet> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Chromium Build Error 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: Thu, 07 Jul 2011 10:38:06 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I am having an issue compiling the latest port of Chromium on FreeBSD 8.1. I was wondering if you could help or hopefully this will help you. $ uname -a FreeBSD purplehaze.kerna.ie 8.1-RELEASE FreeBSD 8.1-RELEASE #3: Fri Jul 30 13:29:41 IST 2010 root@purplehaze.kerna.ie:/usr/obj/usr/src/sys/GENERIC i386 $ $ pkg_info | fgrep -i vpx libvpx-0.9.1 VP8 Codec SDK $ root@purplehaze:(/usr/ports/www/chromium) # make showconfig =3D=3D=3D> The following configuration options are available for chromium-1= 2.0.742.112: CODECS=3Doff "Compile and enable patented codecs like H.264" GCONF=3Don "Use GConf2 for preferences" VPX=3Don "Use system libvpx for VP8 codec" =3D=3D=3D> Use 'make config' to modify these settings root@purplehaze:(/usr/ports/www/chromium) #=20 root@purplehaze:(/usr/ports/www/chromium) # make [...] CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebRange.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebRegularExpression.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebRuntimeFeatures.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebScriptController.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebScrollbarImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSearchableFormData.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSecurityOrigin.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSecurityPolicy.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSelectElement.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSerializedScriptValue.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSettingsImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSharedWorkerImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSpeechInputControllerMockImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebSpeechInputResult.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebStorageAreaImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebStorageEventDispatcherImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebStorageNamespaceImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebStorageQuotaCallbacksImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebString.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebTextRun.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebThreadSafeData.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebURL.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebURLLoadTiming.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebURLRequest.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebURLResponse.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebURLError.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebViewImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebWorkerBase.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebWorkerClientImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WebWorkerImpl.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WorkerAsyncFileSystemChromium.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WorkerAsyncFileWriterChromium.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WorkerFileSystemCallbacksBridge.o CXX(target) out/Release/obj.target/webkit/third_party/WebKit/Source/WebKi= t/chromium/src/WorkerFileWriterCallbacksBridge.o AR(target) out/Release/obj.target/chrome/libbrowser.a AR(target) out/Release/obj.target/third_party/WebKit/Source/WebKit/chromi= um/libwebkit.a ACTION Generating manpage out/Release/chrome.1 CXX(target) out/Release/obj.target/chrome/chrome/app/chrome_main.o CXX(target) out/Release/obj.target/chrome/chrome/app/chrome_main_posix.o CXX(target) out/Release/obj.target/chrome/chrome/app/chrome_exe_main_gtk.o CXX(target) out/Release/obj.target/chrome/content/common/content_switches= =2Eo LINK(target) out/Release/chrome out/Release/obj.target/remoting/libchromoting_base.a(decoder_vp8.o): In fun= ction `remoting::DecoderVp8::DecodePacket(remoting::VideoPacket const*)': decoder_vp8.cc:(.text._ZN8remoting10DecoderVp812DecodePacketEPKNS_11VideoPa= cketE+0x1de): undefined reference to `vpx_codec_vp8_dx' out/Release/obj.target/remoting/libchromoting_base.a(encoder_vp8.o): In fun= ction `remoting::EncoderVp8::Init(gfx::Size const&)': encoder_vp8.cc:(.text._ZN8remoting10EncoderVp84InitERKN3gfx4SizeE+0x1ab): u= ndefined reference to `vpx_codec_vp8_cx' gmake: *** [out/Release/chrome] Error 1 *** Error code 1 Stop in /usr/ports/www/chromium. *** Error code 1 Stop in /usr/ports/www/chromium. root@purplehaze:(/usr/ports/www/chromium) # Kind regards, Conor. --=20 +---------------------------------------------------------------+ It was a new day yesterday, but it's an old day now. MSN: schro5@hotmail.com ICQ: 112562229 GPG: http://www.konundrum.org/schro.asc --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (OpenBSD) iEYEARECAAYFAk4ViLwACgkQS2OGhliUqShQTwCfQ0dY5pkPSM/crkoCGr/brp+H 4lYAoL4gWcADvIWJrJEtn2toXASU/9d1 =guK5 -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-chromium@FreeBSD.ORG Thu Jul 7 22:40:47 2011 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED963106566C for ; Thu, 7 Jul 2011 22:40:46 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3FD308FC13 for ; Thu, 7 Jul 2011 22:40:45 +0000 (UTC) Received: by eyg7 with SMTP id 7so612983eyg.13 for ; Thu, 07 Jul 2011 15:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ITZHgVnxVk3pbrRq531rV2ARrKrk1UtNVswj31otHCg=; b=i0Cd6cPh6vWerjuPcTG1pvqZ6061M2p+oUL29P7FWRyg8uSUJcXcuFdDvxTTOrEhTd UKdcQ5EslFqKavNZrV1yOWlDgPAcBBPBFzO6CNvhQz/hsRuSWUaGsYlKauRHSN2WFRoO qdEzGARaPuk8ZVkuEsAZLcYcgDIrG6E8NrM5A= Received: by 10.213.110.3 with SMTP id l3mr457688ebp.92.1310076665918; Thu, 07 Jul 2011 15:11:05 -0700 (PDT) Received: from [192.168.1.14] (ip18-43-209-87.adsl2.static.versatel.nl [87.209.43.18]) by mx.google.com with ESMTPS id z14sm7348893eef.13.2011.07.07.15.11.03 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jul 2011 15:11:04 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <4E162EF6.4090309@freebsd.org> Date: Fri, 08 Jul 2011 00:11:02 +0200 From: Rene Ladan Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110701 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Thu, 07 Jul 2011 22:40:47 -0000 Op 07-07-2011 00:37, Joseph Mingrone schreef: > When using the sync feature within chromium, is the data encrypted > locally before being sent to google's servers? I see in the dialog > that passwords can be encrypted, but what about the other data? Are > there details available describing the encryption? > I think you're better off asking this on the upstream Chromium lists (e.g. chromium-users@chromium.org). You could check it yourself by sending some example data while running a packet sniffer (e.g. tcpdump). René -- http://www.rene-ladan.nl:8080/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) 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" >