From owner-freebsd-questions@freebsd.org Fri Jun 26 00:09:10 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 156AA98CD71 for ; Fri, 26 Jun 2015 00:09:10 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (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 E7E39122B for ; Fri, 26 Jun 2015 00:09:09 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 304963F770 for ; Thu, 25 Jun 2015 20:09:03 -0400 (EDT) Message-ID: <558C981E.4090107@sneakertech.com> Date: Thu, 25 Jun 2015 20:09:02 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: FreeBSD questions Subject: Re: Is there something wrong with forums.freebsd.org? References: <558C7C37.6060505@sneakertech.com> <558C82C1.103@sneakertech.com> <558C8BF0.4050905@sneakertech.com> <558C8EF9.4080008@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 00:09:10 -0000 >>>> Let me ask this a different way: did they update to something so new >>>> that it only works on very recent OSs? Like should I test with a >>>> windows 8 system or something? >>> >>> No. Firefox 38 on FreeBSD 10-STABLE here, works fine. >> >> Well, given that 10.0 came out only a year and a half ago, that >> doesn't really give me any more info. I'm wondering where the cutoff >> is for "too old" in this case, assuming that's even the issue. > > It is the browser, not the operating system. Unless you have an > unpatched openSSL, maybe. OK, where does curl fit into that then? Presumably all the versions I have access to are too old I guess.