The trouble with quarantine

Michael Monschau michael at
Fri Mar 15 05:54:43 EDT 2013

Hi Bas,

This is very interesting. I have had customers on Windows Vista and 7 with similar problems when DLLs were downloaded on that machine. I think it depended on their security settings. One work-around I found was to download on Macintosh (I am still on 10.7 on my main development machine) and than copy it across the LAN to windows. I wonder if that also works in reverse. Another was to get the advanced properties of the DLL and click the "Unblock" button.

Do you think downloading on 10.7 and than copying to 10.8 would also avoid this marker?

I wonder if there is a better solution as this will probably come up more and more as people migrate to the newer OS.

Do you mind if I create a technical note on the Brainy Data website about this using your work-around. I will credit you for it.


Michael Monschau (Director)
Brainy Data Limited

Reply To: michael at
Phone: +44 (0)870 474 0708
Web: the home of Omnis Components and Developer Services

On 14 Mar 2013, at 22:30, Bastiaan Olij wrote:

> Hi All,
> I'm not sure if I wrote about this before but as I ran into it again
> today and it may save a lot of people headaches I'll share this with
> everyone.
> For many moons now, when you download something from the internet on Mac
> OS X it gets marked to help prevent people from accidentally running
> malicious software. When you start an application downloaded from the
> internet you get a nice little message "this app has been downloaded
> from the internet, are you really sure it is safe to run" or something
> to that effect. If you answer yes the marker is removed and the
> application will start.
> If you download a ZIP file and then extract the zip file, the contents
> of the zip file actually get the same marker.
> Now with libraries the same thing applies but because the OS can't ask
> you each time you start a library whether it is safe to run. A single
> application may consist of a multitude of libraries (I'm not talking
> about Omnis libraries here but dylibs, xcomps, etc).
> So far this marker is pretty much ignored for libraries but we've
> recently started running into situations, especially on OS X 10.8, but
> also on several late 10.7 installs that libraries weren't being loaded.
> I'm not sure what the trigger is but the approach does make sense, if
> some malicous software manages to download and install some library you
> don't want the OS to just load it up.
> For us we ran into this downloading externals from the web, either new
> xcomps from Tigerlogic or new xcomps from Brainy data. The ZIP files get
> marked and when unzipped the xcomps get marked. Once the xcomps are
> distributed to our clients those clients that have this protection
> enabled suddenly had our application fail on them.
> It's easy to fix though, after unzipping open up terminal and cd to the
> location of the xcomp files. You can check if the marker is in place by
> running:
> xattr myComponent.xcomp
> If marked it will return:
> To remove the marker simply run:
> xattr -d myComponent.xcomp
> Now the Mac OS X will load the xcomp just fine.
> Cheers,
> Bas
> _____________________________________________________________
> Manage your list subscriptions at

More information about the omnisdev-en mailing list