Moonshot Express Mac OS
Moonshot Express Mac OS
- Moonshot Express Mac Os Catalina
- Moonshot Express Mac Os 11
- Moonshot Express Mac Os Download
- Moonshot Express Mac Os X
- Installing Node.js and Express on Linux or Mac Matt YIU, Man Tung (mtyiu@cse) SHB 118 Office Hour: Tuesday, 3-5 pm 2015.02.12 Installing Node.js and Express on Linux or Mac This set of slides illlustrate the steps for installing Node.js and Express on Linux and Mac. Please don’t print it in order to save paper!
- A Moonshot (10x improvement), in contrast, can’t be achieved by working harder alone. You have to start with a clean sheet of paper and be willing to try seemingly crazy ideas. You have to keep writing down crazy ideas until you find one that doesn’t actually seem so crazy.
The current Mac operating system is macOS, originally named 'Mac OS X' until 2012 and then 'OS X' until 2016. Developed between 1997 and 2001 after Apple's purchase of NeXT, Mac OS X brought an entirely new architecture based on NeXTSTEP, a Unix system, that eliminated many of the technical challenges that the classic Mac OS faced.
This page is obsolete. Please, use Build Moonshot from source on macOS (with macOS Identity Selector) instead
The Moonshot source code is available from our GIT repository and it all can be built by hand relatively easily, assuming you have all of the prerequisite packages installed. This page has instructions for building the software itself.
Contents
macOS versions
These instructions have been tested on Mac OS X 10.10 Yosemite, Mac OS X 10.11 El Capitan, macOS 10.12 Sierra and macOS 10.13 High Sierra.
1.1. Requirements
To build all of the Moonshot components, you need various packages installed. To install all of these, see below.
1.1.1. Get Xcode for macOS
To get all of the requirements on your macOS platform, you will need to install Xcode and the Xcode command-line extensions:
Install Xcode from the Mac App Store.
Open a Terminal, then install the Xcode Command Line Tools. You will be prompted with a dialog to install the Command Line Tools after a 130MB download.
If you have never launched Xcode before, do so at least once, or run the following command in your Terminal window.
1.1.2. Install the GNU tools for macOS
You will need to install several GNU tools:
- Install the GNU tools that are required for Moonshot by following the instructions at How to install Autoconf, Automake and related tools on Mac OS X from source?
Additionally, install GNU GetText:
1.1.3. Install MacPorts and Makedepend
Makedepend is available from MacPorts. Install MacPorts:
Download the latest install package from MacPorts.org, then update it:
Install Makedepend from MacPorts:
MacPorts
If you prefer to not install MacPorts, install Makedepend manually as follows:
Install pkg-config:
Install util-macros:
Install xproto:
Install makedepend:
1.1.4. Install JSON from CPAN
Update CPAN and install JSON:
Just like on Linux, build and installation locations matter, with one vital difference. On macOS, the /usr
tree itself is locked down and inaccessible, even for the privileged (root) user. However, locations like /usr/local
are open, and with newer versions of the OS, expect this to change.
For the purposes of this set of instructions, we recommend the following:
- For all the Moonshot dependencies, including Moonshot itself, but excluding Heimdal, the
--prefix
parameter should be set to/usr/local/moonshot
.
If you decide to change this location, you should appropriately change the locations in the commands in Sections 3 and 5 to your preference. - For Heimdal, the
--prefix
parameter should be set to/usr/local/heimdal
. This is because we are using Heimdal only for the header files that the Heimdal build generates, not for any library linking. It makes the eventual distribution easier. - We recommend that you build all libraries with the
-rpath
parameter enabled for all libraries to avoid any clashes with other libraries (such as the older version of OpenSSL that macOS ships for compatibility reasons). We have been assured by macOS developers that theclang
andlibtool
tools for macOS support this. - We do NOT recommend using the Apple-provided sources for some libraries (such as Heimdal) as they have various customisations that may negatively impact how Moonshot works, and because Apple categorically WILL NOT support any of their own source sets (we've tried through a Platinum support path and had the support ticket closed and refunded).
If you DO try using Apple's OpenSource sources and find that things build and function fine, please let us know by commenting on this document (with instructions that we can update this document with). These instructions should generally be backward-compatible.
3.1.1. OpenSSL
- Create a directory called
openssl
. Download the OpenSSL build tree from Apple's OpenSource site. Some scripts that Apple provides will be needed, but we will not build it.
Download the latest OpenSSL build from the OpenSSL website. We will build this version.
- Extract
OpenSSL098-59.60.1.tar.gz
, copy its 'bin' directory into the openssl directory, then delete the extracted source. - Edit the
extract_source.sh
script in thebin
directory: - Comment out the IDEA removal and patch lines (lines 39-49).
- Add the following parameters to each of the three
./Configure
lines:no-ssl2 enable-ec_nistp_64_gcc_128
- Change the
--openssldir
parameter to your appropriate directory. We recommend/usr/local/moonshot/bin
- Change the
--prefix
parameter from/usr
to/usr/local/moonshot
- Comment out the line
'rm -f Makefile'
- Find the line
'rm -f x86_64.h i386.h'
, and insert the following below it:ln -s crypto/idea/idea.h include/openssl/idea.h
From the openssl directory, run the following:
- In the
src
directory, edit theMakefile
file:- Add the
-DNO_IDEA
parameter to theCFLAG
line - Add the
-DNO_IDEA
parameter to theDEPFLAG
line
- Add the
Run the following commands:
3.1.2. Heimdal
Heimdal requires OpenSSL. Once OpenSSL has built successfully, build Heimdal.
Download Heimdal:
Extract Heimdal:
Build Heimdal:
- Note down both the location in which you built Heimdal, as well as where the Heimdal libraries are installed to (if you changed the
--prefix
parameter to something else). You will need a binary from the Heimdal build for the Moonshot build in Section 6, and you will need to set the--with-krb5
parameter of the Moonshot./configure
command in Section 6 to the location where you installed Heimdal.
3.1.3. LibConfuse
Clone the latest Libconfuse repository:
Build Libconfuse:
3.1.4. LibEvent
Libevent requires OpenSSL. Once OpenSSL has built successfully, build Libevent.
Clone the latest Libevent repository:
Build Libevent:
The Moonshot source code is all stored in a GIT repository. To fetch it, issue the following command.
The Moonshot repository contains a set of internal dependencies. These need to be built before you can build the Moonshot mechanism itself.
5.1.1. Libradsec
Libradsec is used by the Moonshot libraries.
Configure the Libradsec build:
- Edit the
Makefile
:- Find the
AM_CFLAGS
line, remove the-Werror
parameter. - Find the
libradsec_la_CFLAGS
line, remove the-Werror
parameter - Save the file.
- Find the
Build Libradsec:
5.1.2. Jansson
Jansson is used by the Moonshot libraries.
Configure and build Jansson:
Before building Moonshot, check what the HEAD of your Git tree is:
- Check the output.
- If your head revision is
dfa044b5b
, please download the Heimdal patch first, then follow Step 4 to apply it. If your head revision is3fbcdec
or newer, go directly to Step 5.
heimdal-patch.patch Apply the Heimdal patch:
Configure the Moonshot build:
Configure script parameters
There are several parameters in the command above that rely on locations noted down previously:
LIBS
contains explicit library location references to the macOS-native Heimdal and GSS frameworks as well as the Moonshot libraries.COMPILE_ET
contains the full path to thecompile_et
binary that will be in your Heimdal build tree. You noted this down in the last step of Section 3.1.2.--with-krb5
contains the location where the Heimdal libraries and headers were installed. You noted this down in the last step of Section 3.1.2.- Edit the top-level
Makefile
:- Remove the parameter
-L/usr/local/heimdal/lib
from theKRB5_LDFLAGS
line. - Remove the parameters
-L/usr/local/heimdal/lib -lgssapi
from theKRB5_LIBS
line in the file. - Save the file.
- Remove the parameter
- Edit the
Makefile
in thelibeap
directory:- Remove the parameter
-L/usr/local/heimdal/lib
from theKRB5_LDFLAGS
line. - Remove the parameters
-L/usr/local/heimdal/lib -lgssapi
from theKRB5_LIBS
line in the file. - Save the file.
- Remove the parameter
- Edit the
Makefile
in themech_eap
directory:- Remove the parameter
-L/usr/local/heimdal/lib
from theKRB5_LDFLAGS
line. - Remove the parameters
-L/usr/local/heimdal/lib -lgssapi
from theKRB5_LIBS
line in the file. - Remove the parameters
-L/usr/local/heimdal/lib -lgssapi
from themech_eap_la_LIBADD
line in the file. - Remove the parameter
-Werror
from themech_eap_la_CFLAGS
line. - Remove the parameter
-Werror
from themech_eap_la_CXXFLAGS
line. - Save the file.
- Remove the parameter
Build Moonshot:
You should now have a
mech_eap.so
file in/usr/local/lib/gss
.
To test this build of Moonshot, you will need to make some privileged changes to the system you built this on:
In
/etc
, create agss
directory:Copy the
mech
file from the Moonshotmech_eap
build directory to/etc/gss
- As the privileged user, edit the
/etc/gss/mech
file:- Change the
mech_eap.so
entry on each line to the full path of the library, e.g./usr/local/lib/gss/mech_eap.so
- Save the file.
- Change the
- Create a
.gss_eap_id
file in your user's home directory:- On the first line of the file, put your Moonshot credential in email form, e.g.
username@moonshot.realm
. - On the second line of the file, put your password for the Moonshot credential in the first line.
- Save the file.
- On the first line of the file, put your Moonshot credential in email form, e.g.
Run an SSH command to a Moonshot-enabled system that the credentials you added in the previous step will be valid for:
Jisc Assent
If you have an identity provider on the Jisc Assent network, you can use
ssh -Kv moonshot@ssh.test.moonshot.ja.net
to test whether your macOS Moonshot mechanism worked successfully.You should successfully connect to the service, and you should see several lines like this in the output:
Jisc Assent
On the Jisc Assent Test SSH Service, the final output for success will be this:
To distribute this binary set, you will need to trim down the binaries you have built to include only the dynamic libraries and only bare essentials needed to run the mechanism:
Make a copy of the
/usr/local
directory into a second location as the privileged user.Once the duplication process is complete, change to your duplicate location's
usr/local
directory and delete all directories except the following:lib
moonshot
- In the
lib
directory, delete everything except the following:gss
libintl.8.dylib
libintl.dylib
- In the
moonshot
directory, delete everything except the following:lib
- In the
moonshot/lib
directory, delete:- all
*.a
files - all
*.la
files - the
pkgconfig
directory
- all
- Now use tar to package up the contents of your distribution directory. You should have a tarball around 2 MB in size.
- On your target machine, extract the tarball in such a way that the files end up in the
/usr/local/lib
and/usr/local/moonshot
directories. - To finish the deployment, create the
/etc/gss/mech
file, then try to run the SSH test (section 7, steps 4 to 6) to check that the mechanism is correctly loaded.
Current issues with this build include that the macOS SSH client abandons any gssapi-with-mic
conversations if the first mechanism it chooses, fails.
In a domain environment, this usually involves a Kerberos interaction, i.e. where you have received a Kerberos ticket before by logging in or by running kinit
. Other ssh clients (or a custom build of the ssh client) may not exhibit this behaviour.
On macOS Sierra and later, the native SSH client is sandboxed when run from its default location in /usr/bin
. Making a copy of the binary in /usr/local/bin
enables it to authenticate with Moonshot. Adjust /etc/paths
to load binaries in /usr/local/bin
first, then restart your sessions.
Accounts and bookkeeping program for businessesInvoicingCreate quotes, invoices and more Accounts PayableManage and track payments Analysis & ReportsGenerate more than 20 reports Web AccessSecure web access feature Express Accounts is professional business accounting software, perfect for small businesses needing to document and report on incoming and outgoing cash flow including sales, receipts, payments and purchases.
Free Accounting Software. A free version of this bookkeeping software is available for use by small businesses with less than five employees. The free version does not expire, but does not support some features designed for larger organizations. You can download the free accounting software version here. | |
Organize your Bookkeeping |
Sales and Accounts Receivable
Accounts Payable
| Financial Analysis and Reports
Additional Accounting Features
|
Bookkeeping Features
System Requirements
Download Now
- for Windows
- for Mac
Screenshots
Questions (FAQs)
Bookkeeping 101
Technical Support
Moonshot Express Mac Os Catalina
Pricing & PurchaseMoonshot Express Mac Os 11
Related Business Software
Inventory Software
Invoicing Software
Manage Remote Employees
Personal Finance Software
Digital Dictation Software
Moonshot Express Mac Os Download
More Business Software...
Moonshot Express Mac Os X
Moonshot Express Mac OS