-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/12 23:41, Bjarni Rúnar Einarsson wrote: > On Sun, Jul 8, 2012 at 10:39 PM, Bjarni Rúnar Einarsson Oops, > please don't take my last reply too seriously. But you're > confusing scenarios there, what you just described is scenario Two > or Four. :-)
Not quite - unlike scenario two, the user would get a subdomain from the PageKite provider, rather than using her own domain. And unlike scenario four, the user would generate a certificate for the subdomain and have it signed by a CA, rather than using someone else's wildcard cert. I'm splitting hairs, though - the main point was that things like certificate signing can be handled by the installation wizard, using service providers that are independent from the hardware vendor. > To make this e-mail not a complete waste: random useful thing: > badger.com provide an API for registering domains. Others may as > well (gandi.net?). This means if someone writes the software, then > buying a domain could be handled entirely within the UI of the box > itself. That sounds great! What was the issue you mentioned with end-to-end HTTPS when using PageKite with the user's own domain? Cheers, Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJP+h0AAAoJEBEET9GfxSfM6w4H+gO0o+Lz3a79WLCdRLYF9wmx xwlMzKfoT4Yv4qAtBCsDiFVape9qpAMsZZAQnxOLKijH3OEnFzt0WGRRieOIPNrh zBi4GuSpgsbzV8SJbO3o49I0UJlmDPa3Orhvs+MuQ2R/Rg93u7AGKH8tabML1S6E Tl+6jRajMXTezPgmtUCI1MD1sgtY8c2tqqlDfZ9hDejCZMJn6eyGCzX9TOVmRnCo M59h8wqRLVoDUMzl+YoirKPJZYcFAwpyTtixouDY9ReliPhml/sulg3DMWbWEiWd foWHnQsaLfyuJt2j5RPm+E4bD+ZgoJsON7PxohlzuTrW5HbUUKtmbsi8vMQGDw4= =tkVl -----END PGP SIGNATURE----- _______________________________________________ Freedombox-discuss mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
