{"type":"rich","version":"1.0","author_name":"npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","author_url":"https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-19\n🗒️ Summary of this message: Proposal to limit trusted CA certificates for Bitcoin client to those with good identity verification practices, but this may limit accessibility.\n📝 Original message:On Monday, December 19, 2011 6:44:59 AM Andy Parkins wrote:\n\u003e Perhaps we should be more strict about which CA certificates are trusted by\n\u003e the bitcoin client: say restrict it to those who have demonstrably good\n\u003e practices for verifying identity; rather than the ridiculous amount of\n\u003e trust that comes pre-installed for me in my browser.\n\nAccepted CAs is/should be a property of your *operating system*, not any \nparticular software. Anyhow, restricting this further just makes it even more \nunusable. Already there is only 1 or 2 CAs that will provide a gratis \ncertificate for personal/small users. If you only allow high-class CAs, I \nimagine that will restrict \"no key in the URI\" aliases to those who will fork \nover a lot of money."}