IETF Logo Mail Archive

Re: Microsoft github

Nico Williams <nico@cryptonector.com> Wed, 06 June 2018 17:36 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E48130FA0 for <ietf@ietfa.amsl.com>; Wed, 6 Jun 2018 10:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.794
X-Spam-Level:
X-Spam-Status: No, score=-2.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.795] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgoZFXDk4nw2 for <ietf@ietfa.amsl.com>; Wed, 6 Jun 2018 10:36:51 -0700 (PDT)
Received: from homiemail-a106.g.dreamhost.com (homie-sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 978B2126CB6 for <ietf@ietf.org>; Wed, 6 Jun 2018 10:36:46 -0700 (PDT)
Received: from homiemail-a106.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a106.g.dreamhost.com (Postfix) with ESMTP id 1FF443000293D for <ietf@ietf.org>; Wed, 6 Jun 2018 10:36:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=cryptonector.com; bh=8HSvengUkgX77q1ugz7N 3IwBvpc=; b=ZPJ1J2xeTMU53nyVg6lgut8jdtqHhLMBShYrvTZZzEE+0R1rl2Q8 7peBsuPUBBoyVMl/Ono94gfY8X742YWsEfjN5alHTAFkn6asxdgRnrgKUUNN1dgo wTFjUVsyrATq7Y3lHeo8DTUYY7f+O1ZoCt1/ew1AfAruedV2K/UoGEA=
Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com [209.85.213.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a106.g.dreamhost.com (Postfix) with ESMTPSA id 0AE7A3000293B for <ietf@ietf.org>; Wed, 6 Jun 2018 10:36:46 -0700 (PDT)
Received: by mail-vk0-f44.google.com with SMTP id y137-v6so4291319vkd.6 for <ietf@ietf.org>; Wed, 06 Jun 2018 10:36:45 -0700 (PDT)
X-Gm-Message-State: APt69E2jFmF3b8ERWc2GgV8GNlQjm/gouff2WSd1IFBf6UAzNIn/TeZS /9r59U+Mm+ogBXIKextUI/JufuecdZ5x+Suacg==
X-Google-Smtp-Source: ADUXVKIlQKC8R+c2NWIYdChbDXYYqSoYC89J1dqGYlzqf555NjZNEt1NFPGrzoA0g5jjW8TO2V42bkvS00PaSSwslc4=
X-Received: by 2002:a1f:1a47:: with SMTP id a68-v6mr2569428vka.38.1528306605377; Wed, 06 Jun 2018 10:36:45 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.OSX.2.21.1806042339080.12230@ary.local> <C449CDB6-D253-4BB3-A18E-1912BACDBA26@mcgrail.com> <CAMm+LwizGrfN56Hx-K52O2127Gnrqh=xqzKQ-a3iq+6n_TfDQQ@mail.gmail.com> <CAMm+LwjLy29Ugd=xuzoy8Dxd9Tcmet5yMtpxUymAHtHs2oVdhQ@mail.gmail.com> <20180606135225.GA3831@thunk.org> <CAL9jLaY3wT=tfYqfMND_7NE9-i6Ed7dF1E8q6uAky_6g0_qP+w@mail.gmail.com>
In-Reply-To: <CAL9jLaY3wT=tfYqfMND_7NE9-i6Ed7dF1E8q6uAky_6g0_qP+w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
Date: Wed, 06 Jun 2018 13:36:34 -0400
X-Gmail-Original-Message-ID: <CAK3OfOizQmdpTF5GKFP8kvhv4mzn69_r-Hz3G7UHxnF5J5kXbA@mail.gmail.com>
Message-ID: <CAK3OfOizQmdpTF5GKFP8kvhv4mzn69_r-Hz3G7UHxnF5J5kXbA@mail.gmail.com>
Subject: Re: Microsoft github
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: John Levine <johnl@taugh.com>, Phillip Hallam-Baker <phill@hallambaker.com>, Theodore Ts'o <tytso@mit.edu>, ietf <ietf@ietf.org>, kevin.mcgrail@mcgrail.com
Content-Type: multipart/alternative; boundary="0000000000005251ad056dfc9c19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vu62RniAI3Zfr3jjl7G1Y1pOmk8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2018 17:36:55 -0000

On Wed, Jun 6, 2018 at 11:22 AM Christopher Morrow <morrowc.lists@gmail.com>
wrote:

> On Wed, Jun 6, 2018 at 9:53 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
>>
>> If you are talking about software stored on internal, closed source
>> repo's, (a) why can't you run your own internal git server --- it
>> really isn't *that* hard, and (b) why did you trust github before its
>>
>
> I think this point is important: "why would anyone have trusted github?"
> or their employees really... certainly "any" (some, not all) github
> employees could have had access to all of the repositories (public/private)
> and copied away relevant bits on demand... Changing the label on the
> employee's shirt isn't really changing the equation.
>

Lots of organizations trust third parties with sensitive content.  Usually
one uses contracts to get desired assurances and recourse to the courts.  A
contractually-bound third party is like yet another insider.  The risks may
or may not be higher than insider risk, depending on lots of specific
details.

Nico
-- 

>

v2.23.0 | Report a Bug | By Email