Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1YAbUY-0004bL-Cy for bitcoin-development@lists.sourceforge.net; Mon, 12 Jan 2015 09:40:58 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.177 as permitted sender) client-ip=209.85.213.177; envelope-from=laanwj@gmail.com; helo=mail-ig0-f177.google.com; Received: from mail-ig0-f177.google.com ([209.85.213.177]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YAbUW-0000BE-JZ for bitcoin-development@lists.sourceforge.net; Mon, 12 Jan 2015 09:40:58 +0000 Received: by mail-ig0-f177.google.com with SMTP id z20so10664513igj.4 for <bitcoin-development@lists.sourceforge.net>; Mon, 12 Jan 2015 01:40:51 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.107.155.65 with SMTP id d62mr26444104ioe.79.1421055651317; Mon, 12 Jan 2015 01:40:51 -0800 (PST) Received: by 10.64.195.225 with HTTP; Mon, 12 Jan 2015 01:40:51 -0800 (PST) In-Reply-To: <54B11897.5020100@archlinux.info> References: <CAAS2fgR2a+3wb+He611pxy_Ypur0gq+o7SRjUHa4-R+xHLLnyA@mail.gmail.com> <CA+s+GJCe+6ioiopyfi4eJvFkrPukyW+mMedZ_nKcUEdy-5TEhg@mail.gmail.com> <54B11897.5020100@archlinux.info> Date: Mon, 12 Jan 2015 09:40:51 +0000 Message-ID: <CA+s+GJBMcZ3Bzpcrk1PngOzOzhO7ravkrY0zp6nd9iifqJpxTg@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Ivan Jelincic <parazyd@archlinux.info> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YAbUW-0000BE-JZ Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] OpenSSL 1.0.0p / 1.0.1k incompatible, causes blockchain rejection. X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 12 Jan 2015 09:40:58 -0000 On Sat, Jan 10, 2015 at 12:18 PM, Ivan Jelincic <parazyd@archlinux.info> wrote: > Is openssl1.0.1j unaffected? Yes. It concerns CVE-2014-8275. Which in https://www.openssl.org/news/openssl-1.0.1-notes.html is under: Major changes between OpenSSL 1.0.1j and OpenSSL 1.0.1k [8 Jan 2015] Wladimir