Difference between revisions of "FAQ:The publisher could not be verified"

From MakeHuman Community Wiki
Jump to: navigation, search
(Created page with "File:Publisher_verified.png This is because Microsoft expects all software authors to pay lots of cash to certificate authorities in order to get rid of the warning. No m...")
 
 
Line 1: Line 1:
 
[[File:Publisher_verified.png]]
 
[[File:Publisher_verified.png]]
  
This is because Microsoft expects all software authors to pay lots of cash to certificate authorities in order to get rid of the warning. No money - warning remains. There's no way around it.
+
This is because Microsoft expects all software authors to pay money to certificate authorities in order to get rid of the warning. There's no way around it, short of paying up.
  
To quote a tutorial on the subject: "We purchased a SHA-2 certificate from them in July 2015, and it seems to work fine for almost everything we need. It only costs about $219 per year."
+
Even "small" recurring sums are insurmountable for an open source project which does not have a budget. So this is not going to be fixed anytime soon.  
 
+
The "only" $219 is insurmountable for an open source project which does not have a budget.  
+
  
 
The upside is you can simply ignore the warning and run anyway. Nothing bad will happen.
 
The upside is you can simply ignore the warning and run anyway. Nothing bad will happen.

Latest revision as of 13:22, 6 March 2016

Publisher verified.png

This is because Microsoft expects all software authors to pay money to certificate authorities in order to get rid of the warning. There's no way around it, short of paying up.

Even "small" recurring sums are insurmountable for an open source project which does not have a budget. So this is not going to be fixed anytime soon.

The upside is you can simply ignore the warning and run anyway. Nothing bad will happen.