public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Tom Lane <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Community accounts and SSL
Date: Wed, 12 Mar 2008 14:33:13 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 12 Mar 2008 17:25:11 -0400
Tom Lane <[email protected]> wrote:
> "Joshua D. Drake" <[email protected]> writes:
> > That is certainly one way, but do we really need that? Isn't a self
> > signed cert good enough?
>
> Self-signed certs on a public-facing website scream of amateurism.
> Every time someone visits the site, their browser will complain
> about it, and quite rightly.
Well that isn't true. It asks once and that's it. I will admit
though that FF3 certainly makes it abundantly clear that it doesn't like
it that first time. As far as the amateurism, opinion vary :).
>
> If you wanna do this, you need to pony up some cash to Verisign or
> one of the other recognized CAs.
Well like I said, we can do that. If that is the way the community
wants to go. A 5 year wildcard cert which could be used across all
subdomains is about 500.00.
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL political pundit | Mocker of Dolphins
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH2EwZATb/zqfZUUQRAo1/AJoC6oZi3mrVKNA9Uey9HVwmCUACfwCfRHkp
hXTfhn/hzNN6lvIuFxroQrc=
=ZSPd
-----END PGP SIGNATURE-----
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Community accounts and SSL
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox