Re: Re: FLTK 1.3.6 Release Candidate 1 is now available for download and testing
Albrecht Schlosser
May 02, 2021
On Am 5/2/21 11:15 AM schrieb Albrecht Schlosser wrote:
On 5/2/21 6:54 AM Manolo wrote:
Le samedi 1 mai 2021 à 17:35:45 UTC+2, Albrecht Schlosser a écrit :
On 5/1/21 4:57 PM Manolo wrote:
> I have the problem after configure + make, but no problem after
CMake +
> make.
> Very strange.
The error occurs after I downloaded the FLTK source tar archive with
Firefox, unfold the archive
and build FLTK. The error symptom is a popup window saying
"Blocks is damaged and can't be opened.
Firefox downloaded this file on …"
If I git clone, git checkout branch-1.3 and build with configure : NO
ERROR!
Yes, I see this too.
If I copy the blocks.app dir from my CMake-based build, _empty it
completely_,
and then fill it with the content of blocks.app from my
firefox+configure build : NO ERROR
Thus, the difference in Info.plist between CMake and configure builds
is not the culprit.
I made a similar test: in the <firefox-download> folder I removed
test/blocks.app/Contents/MacOS and Info.plist, then replaced Info.plist
with the Git version and built again (after also removing the blocks
wrapper script). After these steps I could open blocks.app with the Finder.
Thus , the status "I'm suspect, I was downloaded from internet" seems
transferred
from the tar archive all the way to the blocks.app directory and to
block launching these 3 apps.
To circumvent this "security problem" I moved blocks.app aside and
created it again manually. I used an editor (code => VS Code) to edit
the files to avoid duplicating any "downloaded from internet"
attributes, wherever they may be hidden.
See attached file modify_blocks_app.txt for what I did. This worked as
intended, now blocks.app can be opened with the finder and with 'open
test/blocks.app'.
Finally I recreated the entire directory structure of checkers.app and
just /copied/ everything from the saved structure, see attached
modify_checkers.txt, and this worked as well. This is more or less what
you described but I tried it so we can maybe use it in an automated way
to get rid of the problem.
That's real SECURITY! Move unsecure files away, copy the contents back,
and then it's secure. ;-)
Comments are owned by the poster. All other content is copyright 1998-2025 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.