Date: Tue, 12 Dec 2017 14:28:08 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Karl Denninger <karl@denninger.net> Cc: freebsd-security@freebsd.org Subject: Re: http subversion URLs should be discontinued in favor of https URLs Message-ID: <26440.1513088888@critter.freebsd.dk> In-Reply-To: <c27552cf-45d8-7686-c60d-256537780edc@denninger.net> References: <20171205231845.5028d01d@gumby.homeunix.com> <CADWvR2gVn8H5h6LYB5ddwUHYwDtiLCuYndsXhJywi7Q9vNsYvw@mail.gmail.com> <20171210173222.GF5901@funkthat.com> <CADWvR2iGQOtcU=FnU-fNsso2eLCCQn=swnOLoqws%2B33V8VzX1Q@mail.gmail.com> <5c810101-9092-7665-d623-275c15d4612b@rawbw.com> <CADWvR2j_LLEPKnSynRRmP4LG3mypdkNitwg%2B7vSh=iuJ=JU09Q@mail.gmail.com> <fd888f6b-bf16-f029-06d3-9a9b754dc676@rawbw.com> <CADWvR2jnxVwXmTA9XpZhGYnCAhFVifqqx2MvYeSeHmYEybaNnA@mail.gmail.com> <19bd6d57-4fa6-24d4-6262-37e1487d7ed6@rawbw.com> <5A2DB80D.3020309@sorbs.net> <20171210225326.GK5901@funkthat.com> <99305.1512947694@critter.freebsd.dk> <86d13kgnfh.fsf@desk.des.no> <79567.1513083576@critter.freebsd.dk> <c27552cf-45d8-7686-c60d-256537780edc@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <c27552cf-45d8-7686-c60d-256537780edc@denninger.net>, Karl Denn= inger writes: >Now the question becomes this -- is the proper means to handle this via >TLS (using that root cert) OR should the *transport* be fixed so that >https doesn't need to be used? I certainly would caution against inventing more encrypted transports than we already have. The only feasible alternative I see is SSH, provided we can persuade it somehow to not authenticate the client. If this requires a hacked sshd(8) which just says "welcome" I would be very worried about it coexisting with a untainted sshd on any system. >I argue the second, because the goal when it comes to source >distributions is ensuring that the code you transfer is bit-wise >identical to the code on the FreeBSD project repositories *which can be >mirrored.* I am personally a very big fan of integrity checks which does not also encrypt the content with an ephemeral key for exactly that reason. Most of the people who try to force everything behind HTTPS don't even know you can do that. For the FreeBSD SVN tree, this could almost be as simple as posting an email, maybe once a week, with the exact revision checked out and the PGP signed output of: svn co ... && find ... -print | sort | xargs cat | sha256 Such an archive would also be invaluable for reauthenticating in case, somebody ever manages to do something evil to our repo. >Solve the problem at the correct location -- either fix svn to sign and >verify updates or dump it for something that can and use that existing >mechanism (e.g. git) As I mentioned humoursly to you in private email, I don't think this particular problem will reach consensus any sooner if you = also tangling it in the SVN vs GIT political issue. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26440.1513088888>