[Cryptography-dev] PyCA domain

[Donald Stufft]

I imagine we’d just get a *.pyca.io certificate and be done with it.

+1 from me, I needed another similar thing to tab complete now that I have
pypi.io and pypa.io ;)

On Jun 10, 2014, at 6:19 AM, Terry Chia <terrycwk1994 at gmail.com> wrote:

> This sounds good to me but someone needs to take care of setting it up. Managing the SSL certs for the various sub domains can be potentially annoying. 
> 
> On Tuesday, June 10, 2014, Hynek Schlawack <hs at ox.cx> wrote:
> Hi,
> 
> since I’m considering to move service_identity into PyCA (comments welcome), I would like to suggest to grab pyca.io (which is currently free) and use it as our own namespace for our RTFD sites.  In this case service-identity.pyca.io.  I’m pretty sure that’s good for our braaaand (we wanted to push PyCA anyway in the “cryptography” thread) and it would give us some uniformity (same for pyopenssl.pyca.io, bcrypt.pyca.io, potentially cryptography.pyca.io… etc, pp).
> 
> Opinions?
> —h
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev


-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140610/e08a451f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140610/e08a451f/attachment.sig>