Yes, of course, there are some parts that must be dealt with by the site, but the article states a list of things that are outside the reach of what a website should have access to:<p>&gt; They need information on the key generation process.<p>While a useful documentation of sort can be provided by the website, I don&#x27;t think having one visually different procedure per website will help the user<p>&gt; They should allow the user to export the key and to re-import it (just spawning two file dialogs should suffice - of course the key must not be transmitted to the site in the process).<p>We&#x27;re talking about things that go outside the browser here. I think we all agree that giving access to the exterior to a website is easily dangerous<p>&gt; They need a way to list the keys installed in a browser.<p>... only for the related website; I don&#x27;t see why a website should be able to list other keys. Of course we could filter that with the browser... or just do it all from the browser anyway. Also, no website can do this for username&#x2F;passwords<p>&gt; They need to be able to add and remove keys (on the user&#x27;s request).<p>Again, limited to the website, but here again there is no equivalent for passwords