From owner-freebsd-security@freebsd.org Sun Dec 10 23:07:22 2017 Return-Path: Delivered-To: freebsd-security@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 19511EA07B4 for ; Sun, 10 Dec 2017 23:07:22 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id ED9FE67768 for ; Sun, 10 Dec 2017 23:07:21 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from typhoon.sorbs.net (203-206-128-220.perm.iinet.net.au [203.206.128.220]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0P0R00BDWPYOB500@hades.sorbs.net> for freebsd-security@freebsd.org; Sun, 10 Dec 2017 15:16:02 -0800 (PST) Subject: Re: http subversion URLs should be discontinued in favor of https URLs To: Igor Mozolevsky , freebsd security References: <5A2709F6.8030106@grosbein.net> <11532fe7-024d-ba14-0daf-b97282265ec6@rawbw.com> <8788fb0d-4ee9-968a-1e33-e3bd84ffb892@heuristicsystems.com.au> <20171205220849.GH9701@gmail.com> <20171205231845.5028d01d@gumby.homeunix.com> <20171210173222.GF5901@funkthat.com> <20171210190257.GH5901@funkthat.com> <20171210194234.GJ5901@funkthat.com> From: Michelle Sullivan Message-id: <5A2DBDA8.7030703@sorbs.net> Date: Mon, 11 Dec 2017 10:05:12 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <20171210194234.GJ5901@funkthat.com> X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 23:07:22 -0000 John-Mark Gurney wrote: > Igor Mozolevsky wrote this message on Sun, Dec 10, 2017 at 19:17 +0000: >> On 10 December 2017 at 19:02, John-Mark Gurney wrote: >> >> >>> So, you require an exploit in the wild before you'll patch? >> No, I'm saying it's not a realistic threat model! If the threat is the >> integrity of the source code in transit, then it'd be way cheaper and way >> more reasonable to implement a Merkle Tree-like verification with each >> revision. > Then you should be fine w/ http for banking sites, since it's not realistic > that your ISP will MITM your connection to steal money from you, right? > I don't know of a single instance of an ISP MITM'ing banking transactions > to steal money. > Invalid analogy... You probably shouldn't go there... so I will. I have in the past (long time ago - well past that statute of limitations - so can share now) compromised an FTP server on a certain European ISPs network, on there I put a password sniffer looking for a very specific user/connection/password combination... 4 hours it took to get the password I then had "root" across their entire network and in particular to their IRC server... needless to say I have grown up since those days. However, at the time there was very little online banking, and all the banking I knew about was pretty much read only (checking balances, authorising payments to pre-existing arrangements etc)... but using this 'well you might as well use HTTP' would have left me with the opportunity to make a lot of illegal money real quick if you apply it now. Here's a tip, you come to my street and find my open wifi, I'll compromise your arse (just the same as these hypothetical 'malicious Tor node operators') you want a secure connection, one that won't leave you with a hacked android device, don't use my open wifi network. Come and ask me to use my secure network, or use another network. Michelle