<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/wpbdc/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/wpbdc/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/wpbdc/discussion/</id><updated>2012-11-05T03:56:01.190000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>WPBD on Mac OS X 10.8.x</title><link href="https://sourceforge.net/p/wpbdc/discussion/general/thread/4c1c9e26/" rel="alternate"/><published>2012-11-05T03:56:01.190000Z</published><updated>2012-11-05T03:56:01.190000Z</updated><author><name>Gene Ressler</name><uri>https://sourceforge.net/u/generessler/</uri></author><id>https://sourceforge.net0e17ad16a8089728a897008fda03e07711d6040e</id><summary type="html">Hi. With Mountain Lion, Apple by default now requires non-Apple Store applications to be digitally "signed."  The 2012 WPBD is not signed. So you must use the System Preferences dialog.  Select Personal Security &amp; Privacy. Click the lock. Click Allow applications downloaded from: _anywhere_.  (The default is _App Store and identified developers_.)  

We are working on the digital signature technology.  It's just a matter of money and time.  The 2013 BD ought to fix this problem.

Why ML reports a corrupt file rather than an unsigned app is a mystery to us.  We are not experienced in Mac security mechanisms. Any help on this would be greatly appreciated.</summary></entry></feed>