- From: Peter Saint-Andre <stpeter@stpeter.im>
- Date: Wed, 18 Jul 2012 21:44:16 -0600
- To: Nico Williams <nico@cryptonector.com>
- CC: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Tim Bray <tbray@textuality.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/18/12 9:42 PM, Nico Williams wrote: > On Wed, Jul 18, 2012 at 10:32 PM, Peter Saint-Andre > <stpeter@stpeter.im> wrote: >> On 7/18/12 6:13 PM, "Martin J. Dürst" wrote: >> >>> I have my own server for my lab (way less slick than Ongoing, >>> I have to admit), and I have considered using https: at least >>> about once every year, probably more. It would be the right >>> thing to do. But the amount of time it would require from me, >>> to set it up and to make sure it's set up correctly, is just >>> too much. >> >> Martin, I think you overestimate the time it takes. Personally, >> I've found it to be quite easy. If you'd like, I'll write a blog >> post about it sometime soon and post it at my TLS-protected >> website: https://stpeter.im/ > > It's less easy if you use a hosting service, particularly one that > doesn't support SNI. Then you get charged extra for a dedicated > address. (At least one hosting service does that.) Sure, I have a VPS so it's a bit easier. > There's roadblocks... Agreed. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAHgpAACgkQNL8k5A2w/vyftACfWstcT3RCV2somP9hbNMOpVkH LWUAnjg3vlyW05pMO3L8APUI70IdFo+C =yBwv -----END PGP SIGNATURE-----
Received on Thursday, 19 July 2012 03:44:44 UTC