On 8 Jun 2010, at 21:35, SitG Admin wrote:
>> you have to manually export "firefox hjs3" and then manually
>> import it into Chromium? Even on the same computer?
>
> Or, worse yet, Firefox itself *won't launch* and therefore you have to track
> down obscure references to figure out where within Firefox's resource files
> that information is kept, and how it is encoded, and . . . no, exporting
> won't work. If it can be kept in an external file with browser-neutral
> format, and what Firefox stores internally is merely the path on your system
> to locate it, then it won't matter if you accidentally delete your entire
> Firefox *folder*, you'd still have the cert available.
Again, you don't have to export certificates from one browser to the other, or
one machine to the other. You can create one for each browser or machine.
Creating a foaf+ssl certificate, is cheap.
But if you do want to do it right, then why not use the Operating System
Keychain. That is what Chrome does correctly on OSX. Safari and Chrome share
the same OS level keychain. Then indeed all your apps can use the same
certificate.
Common sense really.
Henry
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
