On 9/6/06, Patrick W. Barnes <nman64@xxxxxxxxx> wrote:
Even if we try to hold off for now, we're eventually going to need
certificates for fedoraproject.org, preferably by a CA that is already
recognized by the more common browsers.
I would personally like to see us get a certificate for "fedoraproject.org"
(no subdomain), make "www.fedoraproject.org" a CNAME to "fedoraproject.org",
and put all content that we need under SSL within
the "https://fedoraproject.org/"; namespace, using reverse proxies if
necessary, and not on subdomains. People with a great deal of experience
with DNS and SSL should understand my technical reasons for this, but it's
also the cheaper way to go.
--
Patrick "The N-Man" Barnes
nman64@xxxxxxxxx
IIRC we were working to do this but we were going to try to use some
service like cacert.org instead of a verisign. Personally I don't
care what we use but from a technical point of view we can get this up
and running as soon as we get the cert.
-Mike
_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
_______________________________________________
fedora-advisory-board-readonly mailing list
fedora-advisory-board-readonly@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
