From owner-freebsd-chromium@FreeBSD.ORG Mon Oct 13 00:16:50 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFCE467A; Mon, 13 Oct 2014 00:16:50 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6652BCF7; Mon, 13 Oct 2014 00:16:50 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so2297209wiw.7 for ; Sun, 12 Oct 2014 17:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=KV1nc6kt3mIT1MlIuQyZQgoGZ/v4IVLHRQPitiOL5Uk=; b=Gk0dsZ6s4RbXwmxL2YuwpXkKp/5Ei3ctscv80cGS+He/iaZ4nDZfm5T/R4ClE8UNtq OZiwfKGrqBEVf+E0uRYStkCV3p9TWyp242NUlLOcA5pajcXoJTacwdII7wYCLh30pRhJ cAkmYXfArp2LlHaslr4C0+6gpCd4Gf+tg2ofOL9edEW6Y6BH3Ymo1LWhJnlGex47s9is 6UMiobXBHF6JOTie5f9uYufEKOJV7ubRXNoh3stJ8SgBBBeI4osaQwUBu83z77NlwPAG W63gjfOhdSp07vCL+W7pJ6m1Gp/dTeGaSIAZ12AUBDajzephkfeu3Si1OE3s5CzWzmH7 sRpw== X-Received: by 10.180.38.114 with SMTP id f18mr16891728wik.24.1413159408629; Sun, 12 Oct 2014 17:16:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Sun, 12 Oct 2014 17:16:28 -0700 (PDT) In-Reply-To: References: From: Miguel Clara Date: Mon, 13 Oct 2014 01:16:28 +0100 Message-ID: Subject: Re: chromium 38 up for testing To: =?UTF-8?Q?Ren=C3=A9_Ladan?= , chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 00:16:51 -0000 On Mon, Oct 13, 2014 at 1:14 AM, Miguel Clara wrote: > Please see this bug report: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 > > This is still happening on 38 and its really a killer bug... I cant type > in my native language and this surely affects all uses with latin keyboards. > > Is there any idea why this happens? > > Tried playing with locale settings and nothing worked. > > Thanks > > (Forgot to cc the list) From owner-freebsd-chromium@FreeBSD.ORG Mon Oct 13 09:51:39 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10372523 for ; Mon, 13 Oct 2014 09:51:39 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0C22BDE for ; Mon, 13 Oct 2014 09:51:38 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id x13so8283700wgg.30 for ; Mon, 13 Oct 2014 02:51:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:from:to:subject:mime-version:content-type :content-transfer-encoding; bh=89ICRW3uwPUGZEMj89DwNjC+kIs21d//yG0lBtOke6I=; b=tknbA64QiyjY43ZGqCDPO/8V4ArKV+X4JJhYdcvygJVnhIVPqkpMJMsx+/xlt+T3Hj 5rKZzSMWLnO5DjJjsAfRoGeGBYc8HcUN43WkHKjy/6BQk5zSUcPfv92EjPoBs+DxitV2 p+OtzVprt9yGEcNjAX65RGuzrzBctgRLT61/dNMdz9pzkWhx6wSObLGNvsqQbhSrNVLW c0r/TQNYmGWvSA1qdpC2x62nakdCKqOYn/UPeoSSTyQIxSlicGuPzJwn4AQZ5joW8tLX WK9lGqbOhEK78lTVep6QrIaiqKTEb/BLYWkEcoWxedkE/X4GFHFIb1Z7FZo73Ug6eBJ2 D8yw== X-Received: by 10.194.78.136 with SMTP id b8mr1491531wjx.106.1413193896814; Mon, 13 Oct 2014 02:51:36 -0700 (PDT) Received: from almelo.raji.xor ([46.142.52.32]) by mx.google.com with ESMTPSA id ky3sm16013097wjb.39.2014.10.13.02.51.35 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 13 Oct 2014 02:51:36 -0700 (PDT) Date: Mon, 13 Oct 2014 11:51:34 +0200 Message-Id: From: Wolfgang Hukriede To: freebsd-chromium@freebsd.org Subject: Re: chromium 38 up for testing MIME-version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 09:51:39 -0000 Freshly compiled from ports, with all dependencies up to date Chromium 38.0.2125.101 segfaults on start for me. (This is FreeBSD 9.1-PRERELEASE #0, i386) Messages from gdb: Error while reading shared library symbols: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/local/lib/gcc48/libstdc++.so.6] Error while reading shared library symbols: ... many more like this Error while reading shared library symbols: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/local/lib/gcc48/libgcc_s.so.1] [New Thread 320fc400 (LWP 101378/chrome)] [New Thread 358e0900 (LWP 101380/chrome)] [New Thread 32288a00 (LWP 101381/chrome)] [New Thread 320fe500 (LWP 101382/chrome)] [Thread 32288100 (LWP 101374/chrome) exited] [New Thread 32288d00 (LWP 101335/chrome)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 31404300 (LWP 100282/chrome)] 0x2ddbbd18 in getframeaddr () from /usr/local/lib/libexecinfo.so.1 Kind regards, Wolfgang From owner-freebsd-chromium@FreeBSD.ORG Mon Oct 13 13:57:09 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07E46EA9 for ; Mon, 13 Oct 2014 13:57:09 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFD997F4 for ; Mon, 13 Oct 2014 13:57:08 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Xdg7X-00089C-6t for freebsd-chromium@freebsd.org; Mon, 13 Oct 2014 06:57:07 -0700 Date: Mon, 13 Oct 2014 06:57:07 -0700 (PDT) From: Jongmin Won To: freebsd-chromium@freebsd.org Message-ID: <1413208627207-5956460.post@n5.nabble.com> Subject: "Exec format error" with Debug option MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 13:57:09 -0000 Hello, I have tried to build chromium on FreeBSD 10.0 64bit environment. My chromium version is 38.0.2125.101 (maybe latest one) When I build it as release version, the binary chrome worked with X server. However, built binary with debug option can not be executed producing this error message: "cannot execute binary file: Exec format error", and I haven't solved this problem. I found similar problem in past posting(http://freebsd.1045724.n5.nabble.com/chromium-37-up-for-testing-and-polishing-td5941131i20.html#a5943220), but there is no solution I think. Someone have any idea about this problem? Please let me know to build successfully with debug option, I am sure debugging is possible. (I can not imagine developing chromium without debugger) Thank you for your help in advance! -- View this message in context: http://freebsd.1045724.n5.nabble.com/Exec-format-error-with-Debug-option-tp5956460.html Sent from the freebsd-chromium mailing list archive at Nabble.com. From owner-freebsd-chromium@FreeBSD.ORG Tue Oct 14 13:38:18 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BCEA1FC for ; Tue, 14 Oct 2014 13:38:18 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 835E9DD0 for ; Tue, 14 Oct 2014 13:38:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9EDcIM9082173 for ; Tue, 14 Oct 2014 13:38:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 193725] chromium-37 Latin accent keys are not working Date: Tue, 14 Oct 2014 13:38:17 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: miguelmclara@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 13:38:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 --- Comment #6 from miguelmclara@gmail.com --- Same in version 38... This really makes the browser unusable to me and probably most users hat need the same characters. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Tue Oct 14 20:06:07 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4481665E for ; Tue, 14 Oct 2014 20:06:07 +0000 (UTC) Received: from olejniczak.info (olejniczak.info [85.17.214.250]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB24FE83 for ; Tue, 14 Oct 2014 20:06:06 +0000 (UTC) Received: by olejniczak.info (Postfix, from userid 65534) id 87FF015AE94; Tue, 14 Oct 2014 22:04:31 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on olejniczak.info X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.3.2 Received: from webmail.olejniczak.info (olejniczak.info [85.17.214.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by olejniczak.info (Postfix) with ESMTPSA id D590315AE16 for ; Tue, 14 Oct 2014 22:04:24 +0200 (CEST) Mime-Version: 1.0 Date: Tue, 14 Oct 2014 20:04:24 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-ID: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> X-Mailer: RainLoop/1.6.10.182 From: "Tomek" Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working To: chromium@freebsd.org In-Reply-To: References: X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 20:06:07 -0000 Hi,=0A=0A> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193725=0A>= =0A> --- Comment #6 from miguelmclara@gmail.com ---=0A> Same in version = 38...=0A> =0A> This really makes the browser unusable to me and probably = most users hat need=0A> the same characters.=0A=0AThese three patches sho= uld fix the compose key - please test it (I'm not normally using compose = key myself).=0A=0A--- chrome/browser/ui/browser_command_http://controller= .cc.orig 2014-10-14 21:32:48.000000000 +0200=0A+++ chrome/browser/ui/brow= ser_command_http://controller.cc 2014-10-14 21:22:15.000000000 +0200=0A@@= -67,7 +67,7 @@=0A#include "chrome/browser/ui/browser_commands_chromeos.h= "=0A#endif=0A=0A-#if defined(OS_LINUX) && !defined(OS_CHROMEOS)=0A+#if de= fined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD)=0A#include "u= i/events/linux/text_edit_key_bindings_delegate_auralinux.h"=0A#endif=0A= =0A@@ -279,7 +279,7 @@=0Aif (window()->IsFullscreen() && command_id =3D= =3D IDC_FULLSCREEN)=0Areturn true;=0A=0A-#if defined(OS_LINUX) && !define= d(OS_CHROMEOS)=0A+#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defin= ed(OS_BSD)=0A// If this key was registered by the user as a content editi= ng hotkey, then=0A// it is not reserved.=0Aui::TextEditKeyBindingsDelegat= eAuraLinux* delegate =3D=0A=0A--- ui/base/ime/input_method_http://factory= .cc.orig 2014-10-14 21:31:49.000000000 +0200=0A+++ ui/base/ime/input_meth= od_http://factory.cc 2014-10-14 21:26:34.000000000 +0200=0A@@ -14,7 +14,7= @@=0A#include "ui/base/ime/remote_input_method_win.h"=0A#elif defined(OS= _MACOSX)=0A#include "ui/base/ime/input_method_mac.h"=0A-#elif defined(USE= _AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS)=0A+#elif defined(USE= _AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD)= =0A#include "ui/base/ime/input_method_auralinux.h"=0A#else=0A#include "ui= /base/ime/input_method_minimal.h"=0A@@ -47,7 +47,7 @@=0Areturn scoped_ptr= (new InputMethodWin(delegate, widget));=0A#elif defined(OS_M= ACOSX)=0Areturn scoped_ptr(new InputMethodMac(delegate));=0A= -#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS)=0A= +#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) ||= defined(OS_BSD)=0Areturn scoped_ptr(new InputMethodAuraLinu= x(delegate));=0A#else=0Areturn scoped_ptr(new InputMethodMin= imal(delegate));=0A=0A--- content/browser/renderer_host/render_widget_hos= t_view_http://aura.cc.orig 2014-10-14 21:55:07.000000000 +0200=0A+++ cont= ent/browser/renderer_host/render_widget_host_view_http://aura.cc 2014-10-= 14 21:26:40.000000000 +0200=0A@@ -88,7 +88,7 @@=0A#include "ui/gfx/win/dp= i.h"=0A#endif=0A=0A-#if defined(OS_LINUX) && !defined(OS_CHROMEOS)=0A+#if= defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD)=0A#include= "content/common/input_messages.h"=0A#include "ui/events/linux/text_edit_= command_auralinux.h"=0A#include "ui/events/linux/text_edit_key_bindings_d= elegate_auralinux.h"=0A@@ -2418,7 +2418,7 @@=0A=0Avoid RenderWidgetHostVi= ewAura::ForwardKeyboardEvent(=0Aconst NativeWebKeyboardEvent& event) {=0A= -#if defined(OS_LINUX) && !defined(OS_CHROMEOS)=0A+#if defined(OS_LINUX) = && !defined(OS_CHROMEOS) || defined(OS_BSD)=0Aui::TextEditKeyBindingsDele= gateAuraLinux* keybinding_delegate =3D=0Aui::GetTextEditKeyBindingsDelega= te();=0Astd::vector commands;=0A=0A--=0ABes= t Wishes=0ATomek From owner-freebsd-chromium@FreeBSD.ORG Tue Oct 14 21:27:01 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 103108D1 for ; Tue, 14 Oct 2014 21:27:01 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AECB988 for ; Tue, 14 Oct 2014 21:27:00 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hi2so11302992wib.15 for ; Tue, 14 Oct 2014 14:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Qi5I+e2o1DZKGtEIreSzXh2+y4GSUZTLA1jbuYytKt8=; b=WV754nwTtvpgGYnL4PY+EhE5j4uojjaNfUqVgxUN4xzbRCSwYOowrh/NjwW7BMMbkM Y3KvsMm6p3hsXVkjuDS8NIAOpyO7ZbG+dOW00HYEEd62o2/ffff2aHOzWAeM7wd77iVb SwKbE6oS+8oqNZqx0dH3gPg6AD5p8VhNrv1IA/ex7L4fEtioW9JrPtbq8cTeVTyyVZXr PonZX8Mf36Mbe5XwRIzpcjkOODXTEF0iQAdzsdy8QUJc3Xyq42DKPPLEZM0BpOu7Bllu mdmEJd1M05/ALW7hkxz5tmznMhLcc8w6Xh4iHlZmYBoFzMeTQOzf+hbVWYAFUMSl9z+I UIdA== X-Received: by 10.194.81.70 with SMTP id y6mr4983651wjx.113.1413322018691; Tue, 14 Oct 2014 14:26:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Tue, 14 Oct 2014 14:26:38 -0700 (PDT) In-Reply-To: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> From: Miguel Clara Date: Tue, 14 Oct 2014 22:26:38 +0100 Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working To: Tomek Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 21:27:01 -0000 Testing this now, thanks for the patch Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Tue, Oct 14, 2014 at 9:04 PM, Tomek wrote: > Hi, > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 > > > > --- Comment #6 from miguelmclara@gmail.com --- > > Same in version 38... > > > > This really makes the browser unusable to me and probably most users hat > need > > the same characters. > > These three patches should fix the compose key - please test it (I'm not > normally using compose key myself). > > --- chrome/browser/ui/browser_command_http://controller.cc.orig > 2014-10-14 21:32:48.000000000 +0200 > +++ chrome/browser/ui/browser_command_http://controller.cc 2014-10-14 > 21:22:15.000000000 +0200 > @@ -67,7 +67,7 @@ > #include "chrome/browser/ui/browser_commands_chromeos.h" > #endif > > -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) > #include "ui/events/linux/text_edit_key_bindings_delegate_auralinux.h" > #endif > > @@ -279,7 +279,7 @@ > if (window()->IsFullscreen() && command_id == IDC_FULLSCREEN) > return true; > > -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) > // If this key was registered by the user as a content editing hotkey, then > // it is not reserved. > ui::TextEditKeyBindingsDelegateAuraLinux* delegate = > > --- ui/base/ime/input_method_http://factory.cc.orig 2014-10-14 > 21:31:49.000000000 +0200 > +++ ui/base/ime/input_method_http://factory.cc 2014-10-14 > 21:26:34.000000000 +0200 > @@ -14,7 +14,7 @@ > #include "ui/base/ime/remote_input_method_win.h" > #elif defined(OS_MACOSX) > #include "ui/base/ime/input_method_mac.h" > -#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) || > defined(OS_BSD) > #include "ui/base/ime/input_method_auralinux.h" > #else > #include "ui/base/ime/input_method_minimal.h" > @@ -47,7 +47,7 @@ > return scoped_ptr(new InputMethodWin(delegate, widget)); > #elif defined(OS_MACOSX) > return scoped_ptr(new InputMethodMac(delegate)); > -#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) || > defined(OS_BSD) > return scoped_ptr(new InputMethodAuraLinux(delegate)); > #else > return scoped_ptr(new InputMethodMinimal(delegate)); > > --- content/browser/renderer_host/render_widget_host_view_ > http://aura.cc.orig 2014-10-14 21:55:07.000000000 +0200 > +++ content/browser/renderer_host/render_widget_host_view_http://aura.cc > 2014-10-14 21:26:40.000000000 +0200 > @@ -88,7 +88,7 @@ > #include "ui/gfx/win/dpi.h" > #endif > > -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) > #include "content/common/input_messages.h" > #include "ui/events/linux/text_edit_command_auralinux.h" > #include "ui/events/linux/text_edit_key_bindings_delegate_auralinux.h" > @@ -2418,7 +2418,7 @@ > > void RenderWidgetHostViewAura::ForwardKeyboardEvent( > const NativeWebKeyboardEvent& event) { > -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) > +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) > ui::TextEditKeyBindingsDelegateAuraLinux* keybinding_delegate = > ui::GetTextEditKeyBindingsDelegate(); > std::vector commands; > > -- > Best Wishes > Tomek > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " > From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 01:04:02 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F0CAADE; Wed, 15 Oct 2014 01:04:02 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id D9704140; Wed, 15 Oct 2014 01:04:01 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id B9434C57E; Wed, 15 Oct 2014 01:03:59 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 933E04F1B; Wed, 15 Oct 2014 03:04:00 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: ports-secteam@freebsd.org Subject: POODLE SSLv3 vulnerability Date: Wed, 15 Oct 2014 03:03:59 +0200 Message-ID: <86iojmgn40.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: gecko@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 01:04:02 -0000 Summary: Google researchers have discovered a plaintext recovery attack against SSL 3.0 with no known mitigation. I would like us to ship Firefox with SSL 3.0 disabled by default. This means setting security.tls.version.min to 1, or, in terms of code, changing the initial value of PSM_DEFAULT_MIN_TLS_VERSION from 0 to 1 in security/manager/ssl/src/nsNSSComponent.cpp. I assume that other Mozilla ports use the same code and require the same changes. Note that this does not preclude the user from changing the setting back to 0 in about:config. I would also like to do the same for Chrome, but I don't know the exact procedure and I am unable to find out or test, since Chrome has been broken for several months. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 02:15:14 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5E74D3C; Wed, 15 Oct 2014 02:15:14 +0000 (UTC) Received: from exodus.zi0r.com (exodus.zi0r.com [71.179.14.195]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "exodus.zi0r.com", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98D55973; Wed, 15 Oct 2014 02:15:14 +0000 (UTC) Received: from exodus.zi0r.com (localhost [127.0.0.1]) by exodus.zi0r.com (Postfix) with ESMTP id 682323A0D1; Tue, 14 Oct 2014 22:08:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at zi0r.com Received: from exodus.zi0r.com ([127.0.0.1]) by exodus.zi0r.com (exodus.zi0r.com [127.0.0.1]) (amavisd-new, port 10026) with LMTP id dGBesWpgTlZQ; Tue, 14 Oct 2014 22:08:16 -0400 (EDT) Received: from exodus.zi0r.com (syn.zi0r.com [71.179.14.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by exodus.zi0r.com (Postfix) with ESMTPSA id D11773A0C3; Tue, 14 Oct 2014 22:08:14 -0400 (EDT) Date: Tue, 14 Oct 2014 22:08:13 -0400 From: Ryan Steinmetz To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: POODLE SSLv3 vulnerability Message-ID: <20141015020813.GA5814@exodus.zi0r.com> References: <86iojmgn40.fsf@nine.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline In-Reply-To: <86iojmgn40.fsf@nine.des.no> User-Agent: Mutt/1.5.23 (2014-03-12) Content-Transfer-Encoding: quoted-printable Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 02:15:14 -0000 On (10/15/14 03:03), Dag-Erling Sm=F8rgrav wrote: >Summary: Google researchers have discovered a plaintext recovery attack >against SSL 3.0 with no known mitigation. > >I would like us to ship Firefox with SSL 3.0 disabled by default. This >means setting security.tls.version.min to 1, or, in terms of code, >changing the initial value of PSM_DEFAULT_MIN_TLS_VERSION from 0 to 1 in >security/manager/ssl/src/nsNSSComponent.cpp. I assume that other >Mozilla ports use the same code and require the same changes. > >Note that this does not preclude the user from changing the setting back >to 0 in about:config. > >I would also like to do the same for Chrome, but I don't know the exact >procedure and I am unable to find out or test, since Chrome has been >broken for several months. > FireFox devs will be disabling SSLv3 by default in the November release o= f Firefox: https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-en= d-of-ssl-3-0/ In the interim, they've released an addon to force TLS only: https://addons.mozilla.org/en-US/firefox/addon/ssl-version-control/ It might be less surprising if we bundle the addon with the current installation. -r >DES >--=20 >Dag-Erling Sm=F8rgrav - des@des.no >_______________________________________________________ >Please think twice when forwarding, cc:ing, or bcc:ing >ports-security-team messages. Ask if you are unsure. --=20 Ryan Steinmetz PGP: 9079 51A3 34EF 0CD4 F228 EDC6 1EF8 BA6B D028 46D7 From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 06:02:22 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70D92C78; Wed, 15 Oct 2014 06:02:22 +0000 (UTC) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.233.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11349123; Wed, 15 Oct 2014 06:02:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codelabs.ru; s=three; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=lq/or6oaI+bD8Xs+sx8FE/S3q4HSOsjm24T6DXyZJs0=; b=uFITlncUuK8QTfa/IbFY90fUSmsdvm7nu479mctrHM2VauZFoXykzu5TTs687CrGFDsUyRYqUpHz9iscLp+P+QZLMfYIz15PxiAP+Xkycxn8GogBLJHEYV37ZvBaC1jXwMwPYkFklhZH3g8nWbJh2XWgOC8uSFVzSpvii3b/nG69qzRJ1M5+1Mlf9s/ht2BwfNMwLYK4YQ0AviGpvz5K3hGktZETLLtCobnWSLniydNjSff2SIpxU8ZFnohJdF7DJL3prpDLEVxWfE22krrI5te96STVSo0Uks4QDlmfTksRqsiXPIkYCpUOwPKalXzfv0kxiOaRKjkdpvsh0HyFSfms6f7QVLWWsZCibaDsZh5rLPgAsbNjJhT5zyEq+ekJ6/Rg31IoidV8KVa/IyYVYHRpz6naEogbK6Dze6xT4e59DE7AOu9018lQI93Ry14NUp1hGAKbULV1TRzK8oP48C8l6KE/ln68y/n7KNoD2fxRGprYH2aH3zqr/zZSuo+a8I4LeNfJQ/GzloWP+MTw5gYeTr+ho9JbjCOvRyCQkFKN8uc6F6vblDC0uxoqXjBLt04rHz/qugI9gdPvqL/g3fmuTj/JYWivcp8qqy9erkpAkx9kiZkSUG1rMvNO4tUGCYy/UvkMjLZihYVrzaVUo9x9YRDZ4efLuK7OEWR0wPk=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.233.66]) by 0.mx.codelabs.ru with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1XeHf9-000EBA-Ir; Wed, 15 Oct 2014 10:02:19 +0400 Date: Wed, 15 Oct 2014 10:02:17 +0400 From: Eygene Ryabinkin To: Dag-Erling =?utf-8?B?U23DuHJncmF2?= Subject: Re: POODLE SSLv3 vulnerability Message-ID: References: <86iojmgn40.fsf@nine.des.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="L5nTHegdhbHhzmSD" Content-Disposition: inline In-Reply-To: <86iojmgn40.fsf@nine.des.no> Sender: rea@codelabs.ru Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 06:02:22 -0000 --L5nTHegdhbHhzmSD Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Wed, Oct 15, 2014 at 03:03:59AM +0200, Dag-Erling Sm=C3=B8rgrav wrote: > Summary: Google researchers have discovered a plaintext recovery attack > against SSL 3.0 with no known mitigation. Having spent some time with the attack paper, https://www.openssl.org/~bodo/ssl-poodle.pdf I am posting my findings: may be they will be of some help (or may be someone will pinpoint the areas where I wasn't correct). {{{ It is an active attack (means that you can't do many sensible things with just recorded sessions), and it can be used to recover the plaintext, provided that a. attacker can trick the victim host to send many (around 256 per one recovered byte) requests to the server in question; the URL to be accessed and the body of request should also be controllable by the attacker; b. attacker has control over victim's network channel, so he can manipulate its contents. The problem is that section 5.2.3.2 of RFC6101, https://tools.ietf.org/html/rfc6101#section-5.2.3.2 specifies that for block ciphers the last byte of the plaintext with addition of the MAC and padding ends on the length of the padding, the value that can be made known. So, people talk about case when padding takes an entire block of ciphertext (so the size of original data and MAC is divisible by the block size): in this case the last byte will be (L-1) where L is the cipher's block length. Additional requirement is that the byte that we should decipher should be the last byte of some block of size L. This is where we need the condition "a": since in HTTP requests URL comes before, say, POST content, by controlling the URL or its part attacker should be able to shift the needed byte to the right position; since the body of request is controllable by the attacker, he can make the total length of the request to be fittable to the multiple of the block size (along with the trailing MAC). Since the attacker sees all communications (in encrypted form), he sees blocks C_i (the one that bears the byte to be decrypted as the last byte in block) and C_N (byte with the padding). And attacker swaps the last block with C_i, so here is requirement "b": full control over victim's network channel. The thing is that the value of the padding isn't protected with MAC, so it is essentially random and is trown away if things are fine. So, when server tries to decipher the last block, it will do P_N =3D decrypt(C_i) xor C_{N-1} where P_N is plaintext, decrypt() is block decipher function, C_i and C_{N-1} are respective ciphertext blocks (remember, attacker replaced C_N with C_i). The only thing that server will check for resulting P_N is that its last byte is equal to (L-1). So, if server doesn't reject this attempt, it means that L-1 =3D P_N[L-1] =3D decrypt(C_i)[L-1] xor C_{N-1}[L-1] But decrypt(C_i) =3D P_i xor C_{i-1}, so P_i[L-1] =3D (L-1) xor C_{N-1}[L-1] xor C_{i-1}[L-1] and we know P_i[L-1], since all things in right-hand side are visible to the attacker. Generally, attacker can have control only for the URL part, but then it will need to guess the size of the payload (more properly, its size modulo block length, so there are not that many variants, because block length is typically 8 or 16 bytes). Then he will know that last byte of the padding and can adjust for the changes in request length (that arise because he wants to shift the byte to be deciphered into the proper position). And, of course, all this stuff will be usable only for the period of the session when a single shared secret is used: once session key for block cipher is changed, attacker should start again. }}} > I would like us to ship Firefox with SSL 3.0 disabled by default. > This means setting security.tls.version.min to 1, or, in terms of > code, changing the initial value of PSM_DEFAULT_MIN_TLS_VERSION from > 0 to 1 in security/manager/ssl/src/nsNSSComponent.cpp. I assume > that other Mozilla ports use the same code and require the same > changes. I'd also introduce an OPTION for Apache, Nginx and other Web servers we ship in the ports collection that won't allow to use SSLv3 and turn it on by-default. This will break some legacy clients, so it should be an OPTION. stunnel, all Web servers for Ruby and other servers that do SSL should also be modified to include such modification. --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --L5nTHegdhbHhzmSD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iL4EABEKAGYFAlQ+DelfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDgyRkUwNkJDRDQ5N0MwREU0OUVDNEZGMDE2 QUY5RUFFODE1MkVDRkIACgkQFq+eroFS7PsrzwD9EHqFcxjlcdg2TqoBI6QCeQ4R dP79dnWLKYRTOcQx6nsBAJiW8uImd1sfXBx48gIppuXEwnu74vOLQmLSlL8XJY8O =t/Vn -----END PGP SIGNATURE----- --L5nTHegdhbHhzmSD-- From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 06:29:42 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 636BA168; Wed, 15 Oct 2014 06:29:42 +0000 (UTC) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.233.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04A9B363; Wed, 15 Oct 2014 06:29:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codelabs.ru; s=three; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=f56Tr2CNI5KJ0UIqamXEiD9YMWBPt4a0iwFNdNZevBA=; b=Z4r0mNYzkwF434Qsre76czCqnfRdofd2BSKhDqUoViTtUjhPXTjWN6zhS0hl4NBQVti3zR7HlcQANEKeJwUaTM4bQKxiALo3wZZmdmGrVuD2UJeAEBJExsqjyxMsJ7DfM6Fb3LCm4G8YP6nqGvLNGu+ZF1LN3whRoSOLKiQh88mxqVH/4EdwODtfxvTUo9hJkad01qmFgD3+pAHsa9K1V9epgIc7QmKg+MVP+NsKGA7fjagxZnA9N8bJ68YWFp+SoKo5y6xhZd081r4Va1x+SBsiwv1E7W8kmaWfLvSJFP/5MAqq5f71nrV1n1JbQDAWMOr1gxT6AZ9s3SI/NN9ID6duHX5RUq6LzTFpVpMIkJ8y9f0RT0PY1YYomBGdpsqM4Jga4hD+p1ImiV0Tq4uR0lSH4DLmCzjVs4dIGzwrt9XgnFTqYAHTVonqmXj+Cr2I7sgSHjo46iMUFKvi7AwoMWjySNZEXmLTixdRg6l6WVIiiYljeJjiAzwstVKHV9bOvvUf5u0cwgepL3AfPcQNoNUD35MvuEMki3AsZavfvvx3Unt6TAzM70C31pR3eglxek1saTWUivRx27NV6uEwML6jmEgtJiWe37ZavH6ccNPcbnSSqKG5O09LCaUeYX1gX47Ks+sLW5vg3kuJeb1taiP1YhuZPMRKJGrtojAM4RU=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.233.66]) by 0.mx.codelabs.ru with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1XeI5b-000Ebo-Vo; Wed, 15 Oct 2014 10:29:40 +0400 Date: Wed, 15 Oct 2014 10:29:37 +0400 From: Eygene Ryabinkin To: Dag-Erling =?utf-8?B?U23DuHJncmF2?= Subject: Re: POODLE SSLv3 vulnerability Message-ID: References: <86iojmgn40.fsf@nine.des.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pleSNuEbvnUYtMxG" Content-Disposition: inline In-Reply-To: Sender: rea@codelabs.ru Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 06:29:42 -0000 --pleSNuEbvnUYtMxG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Wed, Oct 15, 2014 at 10:02:17AM +0400, Eygene Ryabinkin wrote: > I'd also introduce an OPTION for Apache, Nginx and other Web servers > we ship in the ports collection that won't allow to use SSLv3 and turn > it on by-default. This will break some legacy clients, so it should > be an OPTION. stunnel, all Web servers for Ruby and other servers > that do SSL should also be modified to include such modification. net/haproxy is another port that terminates SSL. --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --pleSNuEbvnUYtMxG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iL4EABEKAGYFAlQ+FFFfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDgyRkUwNkJDRDQ5N0MwREU0OUVDNEZGMDE2 QUY5RUFFODE1MkVDRkIACgkQFq+eroFS7Pur+wD/YneFPEHm/isaPU4VEbZJ1/Vi QQ3HVaDrAtTfaaiab48A/2oOWVtI4Pcek9YL7fZSEPDhtntptf56loRQKxrZG2FO =oerd -----END PGP SIGNATURE----- --pleSNuEbvnUYtMxG-- From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 07:38:24 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD99C362; Wed, 15 Oct 2014 07:38:24 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 9E3DBBFD; Wed, 15 Oct 2014 07:38:24 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id D0502CC3F; Wed, 15 Oct 2014 07:38:16 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id DEFE04F84; Wed, 15 Oct 2014 09:38:17 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ryan Steinmetz Subject: Re: POODLE SSLv3 vulnerability References: <86iojmgn40.fsf@nine.des.no> <20141015020813.GA5814@exodus.zi0r.com> Date: Wed, 15 Oct 2014 09:38:03 +0200 In-Reply-To: <20141015020813.GA5814@exodus.zi0r.com> (Ryan Steinmetz's message of "Tue, 14 Oct 2014 22:08:13 -0400") Message-ID: <86siipg4v8.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 07:38:25 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ryan Steinmetz writes: > It might be less surprising if we bundle the addon with the current > installation. I disagree. The change I proposed is simple and unobtrusive. Please consider this a formal request from the Security Officer. DES =2D-=20 Dag-Erling Sm=C3=B8rgrav - des@des.no --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUPiRbAAoJEO1n7NZdz2rngR8P/2sXguNxmUzWwWb0+zDt0m9l AgKhhDFscuF8oOjjgDP3VqkUf7rXCU6bu/4U2+rNEVxe1g7l4KRaducJ7KvDAmJE v04nhckazq7TzQLK8cT1JhFbZdRQhVLbv49kQ+p5JUYhj5lvHduk/GhJXspIaMKs 7NeWaERmf/crnDoNA5X5J4yZwWT4YFjQ/AECE/n3Vr5z7F4gxEdkLRgiuUSBN4Sf ls1+5DmBOGxuj9tz90l6POrisMdOeZ82QEDkqshzvCh8dVVU2ZxzK9w4QVJMdHLI BkCOUXxiJs/DzaWtHMa3vt2IcbHUNU0jQeCF2f4Jn5X6SnHCEznxMkHdLUojD4q0 py60xcvTyRYEEISjeuM8MOgeBliYHbjgCeIxkwF7rRZG0kLx3e6BPwNfFlRv86u7 gOzCcd/3MFDzVmgSSA8x/GGUs5u4e2XJHByqiAFHCLjZEnaz82V+KUvFvKubd56z ixbowsspi4DQPthFoTTdXCR0jg02pfq/bl7ZZMAyYd5auGucGpOGX1pfT9qkc7oF Z0PJ0dpIBjIEomPdZV86fD5LuVTW+ToqdsWYgsIn3oPREUqeiagFKHGa6JmsH0A7 9uDI7CmCp7v12Vmo7ayMMgINrmzh4Z20YTFWio68na/Eriz9QuQ5wk1vcRtNmLgz yg7049eT+n/xxw9ueIYU =JCCA -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 09:15:41 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40E24E7B; Wed, 15 Oct 2014 09:15:41 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 01B28856; Wed, 15 Oct 2014 09:15:40 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id 07943CDB2; Wed, 15 Oct 2014 09:15:40 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 1F2A04F9F; Wed, 15 Oct 2014 11:15:41 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Eygene Ryabinkin Subject: Re: POODLE SSLv3 vulnerability References: <86iojmgn40.fsf@nine.des.no> Date: Wed, 15 Oct 2014 11:15:41 +0200 In-Reply-To: (Eygene Ryabinkin's message of "Wed, 15 Oct 2014 10:02:17 +0400") Message-ID: <86a94xzoaq.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 09:15:41 -0000 Eygene Ryabinkin writes: > I'd also introduce an OPTION for Apache, Nginx and other Web servers > we ship in the ports collection that won't allow to use SSLv3 and turn > it on by-default. This will break some legacy clients, so it should > be an OPTION. stunnel, all Web servers for Ruby and other servers > that do SSL should also be modified to include such modification. That sounds like a good idea, but also a lot of work... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 13:51:22 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BEF2EFBD for ; Wed, 15 Oct 2014 13:51:22 +0000 (UTC) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49076AD7 for ; Wed, 15 Oct 2014 13:51:22 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id b13so1415523wgh.12 for ; Wed, 15 Oct 2014 06:51:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JcHR/3Jz7Pr0D6YNk4lxdMGVkfUKtSXLe/wFa/XlBFY=; b=bdf4H7g+kBF2a3LmKHwQ7EYLgPMfs9x+ktbqa8Zz3fuKaalKor/nAyoSak55pnSp4K l2cY9fTZ/0Yal9wjVy+sO1AM7HolHfknjN9gu/IJ9wIHfB0J8vMfk3TX7/cVqxRjE0WL mFrrNKbF270YUxt5g8rCHxTx6QSpdRh2SrqllC5VbcV5xcB5RV013QgA1a6MTtzr1HsS RswYMeNEFYlIVUYU9cJSxOeP9A2WRhEga4ONmOVpTM9qK8oQqvtOwaEZK0/vBx+XyxUw 52IQ1vSnZTU2j2UTEOityjPRxs7pbJV0oWxujieCMcJAZbbZBbWxJ/uXeH+AQmupUrr9 O66A== X-Received: by 10.194.242.4 with SMTP id wm4mr12140631wjc.61.1413381080505; Wed, 15 Oct 2014 06:51:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Wed, 15 Oct 2014 06:51:00 -0700 (PDT) In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> From: Miguel Clara Date: Wed, 15 Oct 2014 14:51:00 +0100 Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working To: Tomek Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 13:51:22 -0000 I still see the same issue cant type ~'` etc Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Tue, Oct 14, 2014 at 10:26 PM, Miguel Clara wrote: > Testing this now, thanks for the patch > > > Melhores Cumprimentos // Best Regards > ----------------------------------------------- > *Miguel Clara* > *IT - Sys Admin & Developer* > *E-mail: *miguelmclara@gmail.com > www.linkedin.com/in/miguelmclara/ > > On Tue, Oct 14, 2014 at 9:04 PM, Tomek wrote: > >> Hi, >> >> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 >> > >> > --- Comment #6 from miguelmclara@gmail.com --- >> > Same in version 38... >> > >> > This really makes the browser unusable to me and probably most users >> hat need >> > the same characters. >> >> These three patches should fix the compose key - please test it (I'm not >> normally using compose key myself). >> >> --- chrome/browser/ui/browser_command_http://controller.cc.orig >> 2014-10-14 21:32:48.000000000 +0200 >> +++ chrome/browser/ui/browser_command_http://controller.cc 2014-10-14 >> 21:22:15.000000000 +0200 >> @@ -67,7 +67,7 @@ >> #include "chrome/browser/ui/browser_commands_chromeos.h" >> #endif >> >> -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) >> #include "ui/events/linux/text_edit_key_bindings_delegate_auralinux.h" >> #endif >> >> @@ -279,7 +279,7 @@ >> if (window()->IsFullscreen() && command_id == IDC_FULLSCREEN) >> return true; >> >> -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) >> // If this key was registered by the user as a content editing hotkey, >> then >> // it is not reserved. >> ui::TextEditKeyBindingsDelegateAuraLinux* delegate = >> >> --- ui/base/ime/input_method_http://factory.cc.orig 2014-10-14 >> 21:31:49.000000000 +0200 >> +++ ui/base/ime/input_method_http://factory.cc 2014-10-14 >> 21:26:34.000000000 +0200 >> @@ -14,7 +14,7 @@ >> #include "ui/base/ime/remote_input_method_win.h" >> #elif defined(OS_MACOSX) >> #include "ui/base/ime/input_method_mac.h" >> -#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) || >> defined(OS_BSD) >> #include "ui/base/ime/input_method_auralinux.h" >> #else >> #include "ui/base/ime/input_method_minimal.h" >> @@ -47,7 +47,7 @@ >> return scoped_ptr(new InputMethodWin(delegate, widget)); >> #elif defined(OS_MACOSX) >> return scoped_ptr(new InputMethodMac(delegate)); >> -#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#elif defined(USE_AURA) && defined(OS_LINUX) && !defined(OS_CHROMEOS) || >> defined(OS_BSD) >> return scoped_ptr(new InputMethodAuraLinux(delegate)); >> #else >> return scoped_ptr(new InputMethodMinimal(delegate)); >> >> --- content/browser/renderer_host/render_widget_host_view_ >> http://aura.cc.orig 2014-10-14 21:55:07.000000000 +0200 >> +++ content/browser/renderer_host/render_widget_host_view_http://aura.cc >> 2014-10-14 21:26:40.000000000 +0200 >> @@ -88,7 +88,7 @@ >> #include "ui/gfx/win/dpi.h" >> #endif >> >> -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) >> #include "content/common/input_messages.h" >> #include "ui/events/linux/text_edit_command_auralinux.h" >> #include "ui/events/linux/text_edit_key_bindings_delegate_auralinux.h" >> @@ -2418,7 +2418,7 @@ >> >> void RenderWidgetHostViewAura::ForwardKeyboardEvent( >> const NativeWebKeyboardEvent& event) { >> -#if defined(OS_LINUX) && !defined(OS_CHROMEOS) >> +#if defined(OS_LINUX) && !defined(OS_CHROMEOS) || defined(OS_BSD) >> ui::TextEditKeyBindingsDelegateAuraLinux* keybinding_delegate = >> ui::GetTextEditKeyBindingsDelegate(); >> std::vector commands; >> >> -- >> Best Wishes >> Tomek >> _______________________________________________ >> freebsd-chromium@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >> To unsubscribe, send any mail to " >> freebsd-chromium-unsubscribe@freebsd.org" >> > > From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 14:54:15 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABFA9395; Wed, 15 Oct 2014 14:54:15 +0000 (UTC) Received: from exodus.zi0r.com (exodus.zi0r.com [71.179.14.195]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "exodus.zi0r.com", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DB661C5; Wed, 15 Oct 2014 14:54:15 +0000 (UTC) Received: from exodus.zi0r.com (localhost [127.0.0.1]) by exodus.zi0r.com (Postfix) with ESMTP id CB4CF3A0D1; Wed, 15 Oct 2014 10:54:13 -0400 (EDT) X-Virus-Scanned: amavisd-new at zi0r.com Received: from exodus.zi0r.com ([127.0.0.1]) by exodus.zi0r.com (exodus.zi0r.com [127.0.0.1]) (amavisd-new, port 10026) with LMTP id YgMz66SmfU_F; Wed, 15 Oct 2014 10:54:12 -0400 (EDT) Received: from exodus.zi0r.com (syn.zi0r.com [71.179.14.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by exodus.zi0r.com (Postfix) with ESMTPSA id 3AE733A0C3; Wed, 15 Oct 2014 10:54:12 -0400 (EDT) Date: Wed, 15 Oct 2014 10:54:10 -0400 From: Ryan Steinmetz To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: POODLE SSLv3 vulnerability Message-ID: <20141015145410.GA79014@exodus.zi0r.com> References: <86iojmgn40.fsf@nine.des.no> <20141015020813.GA5814@exodus.zi0r.com> <86siipg4v8.fsf@nine.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline In-Reply-To: <86siipg4v8.fsf@nine.des.no> User-Agent: Mutt/1.5.23 (2014-03-12) Content-Transfer-Encoding: quoted-printable Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 14:54:15 -0000 On (10/15/14 09:38), Dag-Erling Sm=F8rgrav wrote: >Ryan Steinmetz writes: >> It might be less surprising if we bundle the addon with the current >> installation. > >I disagree. The change I proposed is simple and unobtrusive. Please >consider this a formal request from the Security Officer. I do not have a way to test the patch. Will try to locate someone who can. -r > >DES >--=20 >Dag-Erling Sm=F8rgrav - des@des.no --=20 Ryan Steinmetz PGP: 9079 51A3 34EF 0CD4 F228 EDC6 1EF8 BA6B D028 46D7 From owner-freebsd-chromium@FreeBSD.ORG Wed Oct 15 18:49:20 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 715F1783 for ; Wed, 15 Oct 2014 18:49:20 +0000 (UTC) Received: from mail-pa0-x241.google.com (mail-pa0-x241.google.com [IPv6:2607:f8b0:400e:c03::241]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4837CE8C for ; Wed, 15 Oct 2014 18:49:20 +0000 (UTC) Received: by mail-pa0-f65.google.com with SMTP id lf10so757573pab.4 for ; Wed, 15 Oct 2014 11:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:mime-version:from:to:reply-to:subject:content-type :content-transfer-encoding; bh=9agDyBVxaUz7HZXjUzgiGemeqaeiXxy1WOQI6iFDenM=; b=f9XQsUTZzuEDIElJjGoFtlV6/l1obF08C4uVHtqxTCbk7pG3F82COEHRe9DhUGMSrE sduiMG0vmuE5CtqYvKxySMjtO7yYL4NEj2ho8pt+emsoamYgBWAooD/cIciFaFCSVPzC aUxkRlypmUGcgwLhGZZ/RvrsCwqXiEFnHOFk+Fu9J0wSMqYgS4ZpmBacc6/rGSND9jju OKT1lqyObuT/2MSruuICPvy+GqJ6Fh1BRkBxkPC8LjgD7i9mDrEEx6gKnXsPlL5295jd s+E0Op7pYESdgutDUvoFnC/HNH1NnCB7j8Nb5r0nM3pmMn8uevb5dEsvRBkFxYT50JMx 9Opg== X-Received: by 10.68.206.98 with SMTP id ln2mr14421354pbc.83.1413398959748; Wed, 15 Oct 2014 11:49:19 -0700 (PDT) Received: from Inder-PC ([27.255.188.64]) by mx.google.com with ESMTPSA id mu10sm17812946pdb.10.2014.10.15.11.49.18 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 15 Oct 2014 11:49:19 -0700 (PDT) Message-ID: <543ec1af.0a7e460a.7fc6.116f@mx.google.com> Date: Wed, 15 Oct 2014 11:49:19 -0700 (PDT) X-Google-Original-Date: 16 Oct 2014 00:19:21 +0530 From: happier42165@gmail.com To: freebsd-chromium@freebsd.org Reply-To: limpid75154@gmail.com Subject: Has your website : mail-archive.com been penalized by Google ? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 18:49:20 -0000 Good Morning Bussiness Owner Has your website lost traffic or rankings in last few weeks ? If yes, then your website is a VICTIM to these NEW google algorithm updates. To correct this you need to hire a professioanl Search Engine Optimization company who understands these changes better than what you can. More with these new updates coming each month you need your online web presence to be taken care by a group of SEO Experts who are dedicated to learn all these new changes coming their way. We are presently offering a 15 days FREE Trial for our S.E.O Service, so that you can experience our expert S.E.O skills and then decided to sign up with us. Our S.E.O Plans start from just 199$ and go to 399$ / month making sure your website is optimized for all possible keywords and not just 10-20 keywords like other companies offer. Google has recently launched 3 Big updates and refreshes keep coming every month 1) Google Panda Update : Targeting Websites with Bad ONSITE 2) Google Penguin : Targeting Websites with Bad backlinks 3) Google Pigeon : Targeting Websites with bad local presence We have helped our clients pass all these algorithms pass these updates in last 3 years and we are one of those few ONLY SEO companies who have not been affected MUCH by these updates. What makes our company different : 1) We optimize website not keywords : ( We optimize your website for as many keywords possible ) 2) We assure results in first 15 days itself 3) We have the best possible pricing on the web 4) We abide by all google rules 5) Every link built is shared with for your future use 6) We Offer complete SEO Service not just LINK BUILDING Email us back with your website and your phone number so we can study your website and email you back with our Customized proposal. Looking forward working with you. Regards Vince G SEO Manager ( TOB ) Skype ________________________________________ NO CLICK in the subject to STOP EMAILS From owner-freebsd-chromium@FreeBSD.ORG Thu Oct 16 03:18:55 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A84A2B1B for ; Thu, 16 Oct 2014 03:18:55 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D75FBC0 for ; Thu, 16 Oct 2014 03:18:55 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id hi2so3487587wib.14 for ; Wed, 15 Oct 2014 20:18:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=w7EKXhIfVdBgU5haQqD6S74iIPZyGhMOivVfm+QJWCY=; b=akxTGdG69AkHQpQi65uVU7MEWYv+biDEbATeqfzhMOg/FiXjNtkHv1TiqIfyDqpaEq xtzMuT82VmnD6CNRY+9uRkQTeGRt1BbiFrX9i/8tAcJ5Cr8r8KJJSiB2A3aM2mpaiH8e IuM0mICn4S/4jCsVylBhpZnd6mBbYaf71Chja2UlKzjXQPfka4mD2luXhpd7Ehi/Fjmu A+nHF28EPswXgCwK4xjbidk3pdOWPs2xJ6S4nA3o+nyHxXU8iClMJ5YIA5WLM4ORe7WC 2pXw6Ax9T2LdK+GqCLeYHgtPYqFCN91mvikCDLG973LGg07HvpqmSBUPaZfcDdJNWc7n cRjw== X-Received: by 10.180.187.130 with SMTP id fs2mr16599153wic.24.1413429533457; Wed, 15 Oct 2014 20:18:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Wed, 15 Oct 2014 20:18:32 -0700 (PDT) In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> From: Miguel Clara Date: Thu, 16 Oct 2014 04:18:32 +0100 Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working To: Tomek Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 03:18:55 -0000 > 15 pa=C5=BAdziernika 2014 15:49 - "Miguel Clara" = :: >> > I still see the same issue cant type ~'` etc >> >> Strange - as i said before I'm not using compose key but I've tested >> against several examples and it worked: >> >> For example before I could not enter following characters but after >> patching it is possible: >> Compose + s + s gives =C3=9F >> Compose + ` + a gives =C3=A0 >> Compose + b + a gives =C4=83 >> >> *I wrote above characters using patched chromium with compose key :) >> >> Can You give me some examples / compose sequences? >> >> -- >> Best Wishes >> Tomek >> > > What is the compose key for you exactly? I think you might have fix that yes... But I do not have a compose key, my issue is that the keyboard it self (Portuguese - http://www.goodtyping.com/teclatPORok.png) includes accents keys, tilt etc and this don't work in chrome any more and so I can't also type =C3=A0 or = =C4=83.. From owner-freebsd-chromium@FreeBSD.ORG Thu Oct 16 04:12:16 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 619A04B4 for ; Thu, 16 Oct 2014 04:12:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48FCDDA for ; Thu, 16 Oct 2014 04:12:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9G4CGSj036648 for ; Thu, 16 Oct 2014 04:12:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 193610] chromium-37.0.2062.120_1 Bus error (core dumped) Date: Thu, 16 Oct 2014 04:12:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rob@belics.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 04:12:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193610 --- Comment #22 from Rob Belics --- Another upgrade, another core dump. Unable to use chromium since I first reported this. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 04:35:21 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A26EB4BD; Fri, 17 Oct 2014 04:35:21 +0000 (UTC) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 61046EDF; Fri, 17 Oct 2014 04:35:21 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id tr6so42157ieb.19 for ; Thu, 16 Oct 2014 21:35:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=ewapvnMs6kO2B+Wod0ZQ1odMyyi3T9txzWTE8q8ketM=; b=Ddm9/uFmhD5DCxreA9sclOEibeXbwIyebJgsk9yz8+3U/KIeBzWWEFwDO2EFcZJgHk CbfzdAOchPvfIrIXXln0ca9iAa8SgpteYYCV4ga52Im6uX9JRwdw6xHMGY5p/ilnt1OZ hdbnyteR2SdLsJWQFiP28tjAxtl5m3olLmrhLIz3qnXvtQ56QcT+9dj+tS/Om2YvBFFI qSKt3YFv8hh8rMcsQECNdOnK4NCwZ2lfLldDOIMNVn+TuLek+ZL0qpABq0hmjzsSByqm fqWLlQzLzGjcgDM5vMe5CvT57SKrZ9Z49HYMKxPT1iMZXKtDdHtpjyCjA4rv1FgLWlQk abxw== X-Received: by 10.42.62.129 with SMTP id y1mr7915125ich.19.1413520520719; Thu, 16 Oct 2014 21:35:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.175.28 with HTTP; Thu, 16 Oct 2014 21:34:50 -0700 (PDT) In-Reply-To: <86iojmgn40.fsf@nine.des.no> References: <86iojmgn40.fsf@nine.des.no> From: Jia-Shiun Li Date: Fri, 17 Oct 2014 12:34:50 +0800 Message-ID: Subject: Re: POODLE SSLv3 vulnerability To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 04:35:21 -0000 On Wed, Oct 15, 2014 at 9:03 AM, Dag-Erling Sm=C3=B8rgrav wrot= e: > I would also like to do the same for Chrome, but I don't know the exact > procedure and I am unable to find out or test, since Chrome has been > broken for several months. according to askubuntu[1], for Chromium it is as simple as adding --ssl-version-min=3Dtls1 in command line. It can be added to the /usr/local/bin/chrome script executing the actual binary. [1]: http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-= poodle-vulnerability-cve-2014-3566 -Jia-Shiun. From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 11:37:59 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3DEC3E87 for ; Fri, 17 Oct 2014 11:37:59 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B72C9B2F for ; Fri, 17 Oct 2014 11:37:58 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id z12so698804wgg.13 for ; Fri, 17 Oct 2014 04:37:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=AOtO5ySEyjcTgC5eM5nB9EvJUX+gDvvQG0IgmCbgkFs=; b=IislJjLK94Fs1okjLUDUdqKU6D6FZCzdJnmVOd8QSFoUq+At8SnYYWrZuFTdOQeE3x K3P0dkkNv0WKkph0ESvZTJzJYjC7aT5Dc4jaQReVnWNC5HJr6q8DkhArkOzMl6W8V8Uk 7Miq2GRikVlkVJMp1cBnr+NVOSBQL9C9gAZyqRbMOERw8obqekdI18nUN8to6AyzGS74 L8Dnp9Ejeom4iHlkzw23OFAendXwsSOZKBDVpzPZ6tY7lkKW9N8FoTq226eV+dj9tZLg rcvlcxQXij9X4FIGqaq9ZiQnwUvCxvQz4weRlYu4gdub2I57up8nBDFg1xkkHg3RIkvq +jPA== X-Received: by 10.180.149.169 with SMTP id ub9mr13390290wib.73.1413545876301; Fri, 17 Oct 2014 04:37:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 17 Oct 2014 04:37:35 -0700 (PDT) In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> <238121a4b439775b4f6f24b99ebf6f34@webmail.olejniczak.info> From: Miguel Clara Date: Fri, 17 Oct 2014 12:37:35 +0100 Message-ID: Subject: Fwd: [Bug 193725] chromium-37 Latin accent keys are not working To: chromium-list freebsd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 11:37:59 -0000 On Fri, Oct 17, 2014 at 6:50 AM, Tomek wrote: > Hi, > > 17 pa=C5=BAdziernika 2014 02:03 - "Miguel Clara" = :: > > This is the patch I've applied and I get the issue in v10 and 11 in to= o > different laptops :S > > Ok I see the problem - my mailer (for unknown reason) changed few strings > to links... So the patches didn't apply... > > In the attachment You can find proper patches (to be put in > www/chromim/files, make clean and make build again). > > Ah nice, this way I don't have to use the "extra-patch" method, well l to be honest I was a but lazy to create a patch per file :P hehe thanks I'll try this on my FreeBSD11 machine now as poudriere will also build the 10 package for me :) I'll give you feedback on both when done, and I also notice we lost the CC to chromium somewhere in the middle (adding it again and re-attaching the files so they go to the list too) > -- > Best Wishes > Tomek > From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 19:26:19 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE65AA68 for ; Fri, 17 Oct 2014 19:26:19 +0000 (UTC) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EE991B8 for ; Fri, 17 Oct 2014 19:26:19 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id em10so2886357wid.10 for ; Fri, 17 Oct 2014 12:26:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=zr/1nSbqltRMnjFDh8CSRRyAVlVIZ1UccmySbT9zX+0=; b=oQzB0jBYMnqsUCnFGut+MepfSuKSH6Oyhd2NQLTN/npoVs8RPxpnee1YHzx0UJhor8 lTQNBAXbcaAt2PzUDppo8N8gQLhLqgUHzLj1yt9Ih7T1cgLzjSYPgca/d6DVNufIL8HJ gdFcwFhZ9E+G9dSNQEd9uqLl5OeDdyAXgsRDZT2GiYEpDCmpA08ntSaNsEWtkFDITs2r DPESXq3AUR8Xzfuserzt84CUkbak+40R6L4leWjITAi0BHLLKIcVM1KJESJKSo0HDBfa JGsaBDdSbDizfffXGLqhndk/7tDWsqDhAIeL87zesipp0q4rQiItpb10qHdcW7TS0MGQ lz8A== X-Received: by 10.180.187.130 with SMTP id fs2mr1172668wic.24.1413573977796; Fri, 17 Oct 2014 12:26:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.157.202 with HTTP; Fri, 17 Oct 2014 12:25:57 -0700 (PDT) In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> <238121a4b439775b4f6f24b99ebf6f34@webmail.olejniczak.info> From: Miguel Clara Date: Fri, 17 Oct 2014 20:25:57 +0100 Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working To: chromium-list freebsd , Tomek Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 19:26:20 -0000 Working :) Proof: I can now type =C3=A1 =C3=A0 =C3=A3 =C3=B4 :D From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 20:09:43 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57D66AF3 for ; Fri, 17 Oct 2014 20:09:43 +0000 (UTC) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1385B830 for ; Fri, 17 Oct 2014 20:09:43 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id x69so1135907oia.17 for ; Fri, 17 Oct 2014 13:09:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b4GzPubry8OdUDnmUm5r45bJXxIcdKd+SDNpuDv/Sg4=; b=bJVPgzNbtC1XT5x3ZpBwCaWkrJc08EbUlIac/MbSc3q+HZKGzoqx/L00gfJFQeaZvm 2ejh1X4NKU2Dgyrht+eMF/g6KX901k/UcTLBk39t5s3t4Nq8pVoqZxDT822VdlkSUdMb J1KY7gRp5pLI3/tAgyDOjzjbQhDNTudsNFdQ1BoxDbZR/QyyGetBCk05q/2Clb+FC4BL VSxc7opHJFayT4AeKkpaZ5kFa7/52/D92I7COZLK6V/Eyd1BpEQR99d95K2v/wqvDRIH tVfdbGPYI4NsRf08BjnHPyzH7OgeY08c37U9MGmkCEC3r3ou9aRhcNwjptxU2GzQUf0j P5Mw== MIME-Version: 1.0 X-Received: by 10.202.181.197 with SMTP id e188mr2469962oif.96.1413576582363; Fri, 17 Oct 2014 13:09:42 -0700 (PDT) Received: by 10.182.19.133 with HTTP; Fri, 17 Oct 2014 13:09:42 -0700 (PDT) Received: by 10.182.19.133 with HTTP; Fri, 17 Oct 2014 13:09:42 -0700 (PDT) In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> <238121a4b439775b4f6f24b99ebf6f34@webmail.olejniczak.info> Date: Fri, 17 Oct 2014 22:09:42 +0200 Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working From: =?UTF-8?Q?Ren=C3=A9_Ladan?= To: Miguel Clara Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 20:09:43 -0000 Op 17 okt. 2014 21:26 schreef "Miguel Clara" : > > Working :) > > Proof: I can now type =C3=A1 =C3=A0 =C3=A3 =C3=B4 :D > So Tomeks patches posted earlier in this thread did the trick? Ren=C3=A9 From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 21:39:37 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DF574DB for ; Fri, 17 Oct 2014 21:39:37 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9EC1F0 for ; Fri, 17 Oct 2014 21:39:36 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id b13so1756700wgh.34 for ; Fri, 17 Oct 2014 14:39:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=Xvl5b1a3wF8aq92ydh9TsP9uOK+QhyZhjSaGMGe87co=; b=rECIslaTDByJ/uoOtVMF6rcWL0SyANkb5iH6+pF4OoGU/NmQ6Acx4IoV93xSO7QM+l UdrzspOsVBN2O1dmSuwB8RXWXjF1qXVC7TL6qZlKCNTMHGqEkw/CrjZuBAyuStO0TtBO mLs2VlnOi2bcropKm/PNEn/La0EKAir853Gb/pX8fQKddBtZWSzDhmmpPxIK4xYiOs85 QPizV6M3dsF3pnf88SN6QQt+pK1+otc/4koLoz7mEwRKKbmc3GbuOtQCfXJ0YjwBrxhW Xryb+XdHFuHMcDue7sYYtctN1dlYKmtUED5IaUToElMUWsqm22vtFfXxwtQpEriY5CbY v+bg== X-Received: by 10.194.119.193 with SMTP id kw1mr13552324wjb.37.1413581973582; Fri, 17 Oct 2014 14:39:33 -0700 (PDT) Received: from [192.168.1.95] (194.73.37.188.rev.vodafone.pt. [188.37.73.194]) by mx.google.com with ESMTPSA id au4sm3080056wjc.15.2014.10.17.14.39.32 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 Oct 2014 14:39:32 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> <238121a4b439775b4f6f24b99ebf6f34@webmail.olejniczak.info> MIME-Version: 1.0 Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working From: Miguel Clara Date: Fri, 17 Oct 2014 22:39:29 +0100 To: =?ISO-8859-1?Q?Ren=E9_Ladan?= Message-ID: <8804A144-1625-4F80-8CF8-64DEE15CF1A2@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 21:39:37 -0000 No the pasted patches were missing something, he then sent to me attachments with the correct version and those did the trick, I've forwarded them to the list but now that I think about it they were probably striped !? In any case I guess maybe tomek could make a merge request on the github version? There's also the bug I've opened about this, not sure if the best is to post the patches there? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 Tanks to both, tomek for the patch and René for the continuous work on the chromium port! Miguel C. On October 17, 2014 9:09:42 PM WEST, "René Ladan" wrote: >Op 17 okt. 2014 21:26 schreef "Miguel Clara" : >> >> Working :) >> >> Proof: I can now type á à ã ô :D >> >So Tomeks patches posted earlier in this thread did the trick? > >René -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-chromium@FreeBSD.ORG Fri Oct 17 23:32:11 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1AC6792E for ; Fri, 17 Oct 2014 23:32:11 +0000 (UTC) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CAB6EDDC for ; Fri, 17 Oct 2014 23:32:10 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id wn1so1421318obc.34 for ; Fri, 17 Oct 2014 16:32:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OZcAkyDstf6+OuB5sJtfOu/cTnXunlg1D+atMPtmPtM=; b=qku+tTK51WFCIS0sJLg6s8eylp95yW1wOLe80jetI802aZAwAKgRvnCLUDc7ZbGgLy QvKd7RQwT/4DglAOkEqfzOY0JLkHeprvFDnskdRSMrQEykV1lkEs8t5zMmlcOjI62zej ukrNRU/e4f3E5ORMjThOmGbqLIoflo0zieF07S5SssfXI/QEwom5xPJSPW4n3WPkI64F gEUFOsV3w6c6gEFZYaPfxhmbgPwSdUfAZiGKQNInKNcXyegjlJB/C//u47UK3Ia84wis TF9C8FYeIVMyG6hF/r4GMPxcQUMO93wjkoof1j+4Sct/Qhiu8CrroWYFidpZ8ESmozqO wShQ== MIME-Version: 1.0 X-Received: by 10.202.8.132 with SMTP id 126mr2935358oii.32.1413588730182; Fri, 17 Oct 2014 16:32:10 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.182.19.133 with HTTP; Fri, 17 Oct 2014 16:32:10 -0700 (PDT) Received: by 10.182.19.133 with HTTP; Fri, 17 Oct 2014 16:32:10 -0700 (PDT) In-Reply-To: <8804A144-1625-4F80-8CF8-64DEE15CF1A2@gmail.com> References: <319a0f139f45ae0b0471679e65ab1d58@webmail.olejniczak.info> <4fac24f3c1d77c8d0a15b14f3294951f@webmail.olejniczak.info> <238121a4b439775b4f6f24b99ebf6f34@webmail.olejniczak.info> <8804A144-1625-4F80-8CF8-64DEE15CF1A2@gmail.com> Date: Sat, 18 Oct 2014 01:32:10 +0200 X-Google-Sender-Auth: z1mljGefjDpGCx7Otq8X_OHEREQ Message-ID: Subject: Re: [Bug 193725] chromium-37 Latin accent keys are not working From: =?UTF-8?Q?Ren=C3=A9_Ladan?= To: Miguel Clara Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 23:32:11 -0000 Op 17 okt. 2014 23:39 schreef "Miguel Clara" : > > > No the pasted patches were missing something, he then sent to me attachments with the correct version and those did the trick, I've forwarded them to the list but now that I think about it they were probably striped !? A quick look with my phone suggests so ... > > In any case I guess maybe tomek could make a merge request on the githb version? Sure, I can merge it back into the ports tree from there. > > There's also the bug I've opened about this, not sure if the best is to post the patches there? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193725 > That's also fine. > Tanks to both, tomek for the patch and Ren=C3=A9 for the continuous work = on the chromium port! > > Miguel C. > > > > On October 17, 2014 9:09:42 PM WEST, "Ren=C3=A9 Ladan" wrote: >> >> >> Op 17 okt. 2014 21:26 schreef "Miguel Clara" : >> > >> > Working :) >> > >> > Proof: I can now type =C3=A1 =C3=A0 =C3=A3 =C3=B4 :D >> > >> So Tomeks patches posted earlier in this thread did the trick? >> >> Ren=C3=A9 > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-chromium@FreeBSD.ORG Sat Oct 18 08:14:34 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C24D297B for ; Sat, 18 Oct 2014 08:14:34 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A9ED1DE for ; Sat, 18 Oct 2014 08:14:34 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9I8EYTO023723 for ; Sat, 18 Oct 2014 08:14:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 193610] chromium-37.0.2062.120_1 Bus error (core dumped) Date: Sat, 18 Oct 2014 08:14:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: gerrit@weinberg2.de X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2014 08:14:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193610 gerrit@weinberg2.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gerrit@weinberg2.de --- Comment #23 from gerrit@weinberg2.de --- Same here. Both the last v37 and the new v38 just give a bus error and a core dump on my system (the binary version from pkg as well as the ones I compiled from ports): zsh/2 372 % pkg info|grep chromium chromium-38.0.2125.101_2 Google web browser based on WebKit zsh/2 369 % chrome Bus error (core dumped) zsh/2 370 [138] % uname -a FreeBSD comet.terra.ger 9.3-BETA2 FreeBSD 9.3-BETA2 #0 r267293: Tue Jun 10 10:16:51 CEST 2014 root@comet.terra.ger:/usr/obj/usr/src/sys/COMET amd64 I'd really like to have chrome running again, I miss it. -- You are receiving this mail because: You are the assignee for the bug.