From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Jeff Sickel <jas@corpus-callosum.com>
In-Reply-To: <CANUoZoF-WRO8mTOcHFhsyDmGaKyx_0sKUdksjsCtzFLyjh9YfQ@mail.gmail.com>
Date: Tue,  3 Dec 2013 12:43:35 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E8B7915-70E1-4E44-9F09-89DFBCE05BB2@corpus-callosum.com>
References: <de695aff3307446172d4e3382720a1f2@felloff.net>
	<AC7F138C-28D0-4828-A319-3FD41ADBC7CE@corpus-callosum.com>
	<CANUoZoF-WRO8mTOcHFhsyDmGaKyx_0sKUdksjsCtzFLyjh9YfQ@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ca.pem
Topicbox-Message-UUID: 91dbfd18-ead8-11e9-9d60-3106f5b1d025

I was primarily interested in doing:

	go get code.google.com/p/goprotobuf/proto
	go get code.google.com/p/goprotobuf/protoc-gen-go

Which works w/ a ca.pem using a trusted root CA.  I should probably
fix that with the python code as well since hg pull of go ends
up getting new code.google.com fingerprints every few days.

On Dec 3, 2013, at 12:36 PM, David du Colombier <0intro@gmail.com> =
wrote:

> Yes, but using "go get" on a HTTPS URI will fail if you don't trust =
its root certificate authority.
>=20
> --=20
> David du Colombier
>=20