1+ <!DOCTYPE html>
2+ < html lang ="en-US ">
3+ < head >
4+ < title > articlefetch</ title >
5+ < link rel ="stylesheet " href ="https://caltechlibrary.github.io/css/site.css ">
6+ < link rel ="stylesheet " href ="https://media.library.caltech.edu/cl-webcomponents/css/code-blocks.css ">
7+ < script type ="module " src ="https://media.library.caltech.edu/cl-webcomponents/copyToClipboard.js "> </ script >
8+ < script type ="module " src ="https://media.library.caltech.edu/cl-webcomponents/footer-global.js "> </ script >
9+ </ head >
10+ < body >
11+ < header >
12+ < a href ="https://library.caltech.edu "> < img src ="https://media.library.caltech.edu/assets/caltechlibrary-logo.png " alt ="Caltech Library logo "> </ a >
13+ </ header >
14+ < nav >
15+ < ul >
16+ < li > < a href ="/ "> Home</ a > </ li >
17+ < li > < a href ="index.html "> README</ a > </ li >
18+ < li > < a href ="LICENSE "> LICENSE</ a > </ li >
19+ < li > < a href ="INSTALL.html "> INSTALL</ a > </ li >
20+ < li > < a href ="user_manual.html "> User Manual</ a > </ li >
21+ < li > < a href ="about.html "> About</ a > </ li >
22+ < li > < a href ="search.html "> Search</ a > </ li >
23+ < li > < a href ="https://github.com/caltechlibrary/articlefetch "> GitHub</ a > </ li >
24+ </ ul >
25+ </ nav >
26+ < section >
27+ < p > Installing an unsigned executable on macOS can be a bit tricky due to
28+ macOS’s security features designed to protect users from potentially
29+ harmful software. Here’s a general guide on how to do it:</ p >
30+ < ol type ="1 ">
31+ < li > < p > < strong > Download the Executable</ strong > : First, download the
32+ unsigned executable file you want to install.</ p > </ li >
33+ < li > < p > < strong > Locate the File</ strong > : Use Finder to locate the
34+ downloaded file. It’s often in the < code > Downloads</ code > folder unless
35+ you specified a different location.</ p > </ li >
36+ < li > < p > < strong > Attempt to Open the File</ strong > : Double-click the file
37+ to open it. macOS will likely show a warning that the file cannot be
38+ opened because it is from an unidentified developer.</ p > </ li >
39+ < li > < p > < strong > Override Security Settings</ strong > :</ p >
40+ < ul >
41+ < li > < strong > Option 1: Open via Context Menu</ strong >
42+ < ul >
43+ < li > Right-click (or Control-click) the file.</ li >
44+ < li > Select < code > Open</ code > from the context menu.</ li >
45+ < li > You’ll see another warning, but this time there will be an option to
46+ < code > Open</ code > the file anyway. Click < code > Open</ code > .</ li >
47+ </ ul > </ li >
48+ < li > < strong > Option 2: Allow Apps from Anywhere (Temporarily)</ strong >
49+ < ul >
50+ < li > Open < code > System Preferences</ code > and go to
51+ < code > Security & Privacy</ code > .</ li >
52+ < li > Click the lock icon in the bottom left corner and enter your
53+ password to make changes.</ li >
54+ < li > Under the < code > General</ code > tab, you might see a message about
55+ the app being blocked. Click < code > Open Anyway</ code > .</ li >
56+ < li > If you don’t see this option, you can temporarily change the setting
57+ to allow apps downloaded from < code > Anywhere</ code > . However, this
58+ option is not available in the latest versions of macOS by default. You
59+ may need to use the Terminal to do this:
60+ < ul >
61+ < li > Open Terminal and type:
62+ < code > sudo spctl --master-disable</ code > </ li >
63+ < li > Press Enter and provide your password.</ li >
64+ < li > This will allow you to run apps from anywhere, but it’s recommended
65+ to re-enable security by typing < code > sudo spctl --master-enable</ code >
66+ after installing your app.</ li >
67+ </ ul > </ li >
68+ </ ul > </ li >
69+ </ ul > </ li >
70+ < li > < p > < strong > Use Terminal (Advanced Users)</ strong > : If the above
71+ methods don’t work, you can use the Terminal to run the executable
72+ directly:</ p >
73+ < ul >
74+ < li > Open Terminal.</ li >
75+ < li > Navigate to the directory where the file is located using the
76+ < code > cd</ code > command.</ li >
77+ < li > Make the file executable by typing:
78+ < code > chmod +x filename</ code > </ li >
79+ < li > Run the file by typing: < code > ./filename</ code > </ li >
80+ </ ul > </ li >
81+ < li > < p > < strong > Check for Updates</ strong > : Sometimes, developers will
82+ sign their apps later. Check if there’s a signed version available to
83+ avoid these steps in the future.</ p > </ li >
84+ </ ol >
85+ < h3 id ="important-considerations "> Important Considerations</ h3 >
86+ < ul >
87+ < li > < strong > Security Risks</ strong > : Running unsigned executables can
88+ expose your system to malware and other security risks. Only proceed if
89+ you trust the source of the software.</ li >
90+ < li > < strong > System Integrity Protection (SIP)</ strong > : Some steps might
91+ be restricted by SIP, which is designed to protect your system.
92+ Disabling SIP is not recommended unless absolutely necessary.</ li >
93+ </ ul >
94+ < p > If you’re unsure about any of these steps or the safety of the file,
95+ it’s best to consult with someone who has more experience with macOS or
96+ to contact the software developer for support.</ p >
97+ </ section >
98+ < footer-global > </ footer-global >
99+ </ body >
100+ </ html >
0 commit comments