Selecting a new custom provider from ConfigurationWizard may throw a download security exception
Tested introducing https://bitmask.net. In provider.json file the https://api.bitmask.net:4430/1/config/eip-service.json certificate differs from https://api.bitmask.net/1/config/eip-service.json (this last one is stored in our bitmask.url file from assets) one.
This situation could be reproduced if the user enters a provider whose eip-service.json and provider.json files are transmitted via https using not-trusted certificates.
One possible solution: We should have to provide a means to the user to download and reckon as trusted a selected certificate (just as web browsers do when you meet an https using a self-signed certificate).
(from redmine: created on 2013-02-13, closed on 2013-03-18)