Date: Mon, 10 Jan 2005 06:49:50 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Ted Mittelstaedt <tedm@toybox.placo.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: CA-cert Message-ID: <20050110054950.GB8531@pcwin002.win.tue.nl> In-Reply-To: <LOBBIFDAGNMAMLGJJCKNEEABFAAA.tedm@toybox.placo.com> References: <41E16C3A.6040300@taborandtashell.net> <LOBBIFDAGNMAMLGJJCKNEEABFAAA.tedm@toybox.placo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Offtopic, but... On Sun, Jan 09, 2005 at 09:22:48PM -0800, Ted Mittelstaedt wrote: > > Ted Mittelstaedt wrote: > > > Pointless for us, as CAcert's root certificate isn't included in > > > I.E., so the end users have to go through the same honky-tonk to > > > include it in their browsers as if you just make your own certs. > > > > Not quite. If they include the CA-Cert root certificate, they only have > > to do that once for all of your CA-Cert signed certificates. >=20 > Good point. Not only that, but the more people using CA-Cert, the easier it will become to convince browsers to include the CA-Cert root certificate by default. --Stijn --=20 Tact, n.: The unsaid part of what you're thinking. --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB4hd+Y3r/tLQmfWcRAiYJAKCqfT72/tEbnyKGzm6BdpHG7Gpt+gCgjpn0 qFAGVv5gjuQ/FVCpTmkvW4o= =tWd3 -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050110054950.GB8531>