Table of Contents


As you might have guessed from my previous post, I am trying to standardize at work. Part of this was to move many core OS X services away from OS X Server and towards Ubuntu. This will allow us to use our existing virtualization infrastructure. After reposado the next big service was our munki repo.

Munki is a very powerful open source tool for patch management and software updates for OS X clients. The client component is pretty easy to install but the server component can be a bit more tricky for newer administrators. The goal of this guide is to walk through setting up the server web share with http basic authentication (read simply security), and lastly setup samba so we can remote into our web server to manage files.

In the past, our munki_repo has been shared using apache but due to some research and a few internal tests I will be using nginx as the backend in this guide.

Since our Munki setup has many add-on projects including: mandrill, munkireport-php, and our in-house rsync replication I will be splitting this series into multiple parts.

The Install

It is good practice to make sure our Ubuntu server is fully patched before we start. Then we will install git, curl, build-essential, nginx, apache2-utils, and samba.

Installing Required Software

sudo apt-get update
sudo apt-get upgrade
sudo apt-get -y install git curl build-essential nginx apache2-utils samba

Setup the directories:

sudo mkdir /usr/local/munki_repo
sudo mkdir -p /etc/nginx/sites-enabled/
ln -s /usr/local/munki_repo/ ~/
cd /usr/local/munki_repo
sudo mkdir catalogs client_resources icons manifests pkgs pkgsinfo

Creating the service accounts & set directory permissions:

sudo addgroup --system munki
sudo adduser --system munki --ingroup munki
sudo usermod -a -G munki $USER # Adds the current console user to munki group
sudo usermod -a -G munki www-data # Adds web user to munki group
sudo chown -R $USER:munki /usr/local/munki_repo
sudo chmod -R 2774 /usr/local/munki_repo

Setting up Nginx

Nginx is fast, light-weight, and uses a fraction of the resources that Apache uses. But don’t take my word for it there are lots of other reason why you might want to use Nginx.

Nginx’s installation on Ubuntu is very similar to Apache. All of its config files are stored in /etc/nginx.

Lets backup the original default file create and create our own.

sudo mv /etc/nginx/sites-enabled/default ~/default.bkup
sudo nano /etc/nginx/sites-enabled/default

Make sure and change the server_name to match your server’s Fully Qualified Domain Name (FQDN) or IP.

server {
  listen 80 default_server;
  listen [::]:80 default_server ipv6only=on;

  root /usr/share/nginx/html;
  index index.php index.html index.htm;

  server_name munki; # Change this to your FQDN.

  location /munki_repo/ {
    alias /usr/local/munki_repo/;
    autoindex off;
    auth_basic "Restricted";
    auth_basic_user_file /etc/nginx/.htpasswd;

And finally start the nginx service.
sudo /etc/init.d/nginx start

Nginx Issues: To have Nginx check your configuration for issues run the following command:
nginx -c /etc/nginx/nginx.conf -t

Securing your munki_repo

For my purpose, I will be securing my munki_repo with simple http basic authentication. Depending on the needs of your organization this might be enough but you might need to look into ssl and other advanced options. If you are interesting in these options check out the munki wiki.

Create an http user and password sudo htpasswd -c /etc/nginx/.htpasswd munkihttpuser

The tool will prompt you to enter a password (make it strong).

New password: ******
Re-type new password: ******
Adding password for user munkihttpuser

The structure of the htpasswd is login:password_hash.

We must reload the nginx service to update the reflected change.
sudo /etc/init.d/nginx reload

Now when you try to access your website, [http://yourmunkiserver/munki_repo/](), you will notice a browser prompt that asks you to enter the login and password. Enter the details that you used while creating the .htpasswd file. The prompt does not allow you to access the website until you enter the right credentials. The munki client supports this security feature with the AdditionalHttpHeaders key more info.


Note: If you do not want to secure your munki repo you can remove this setting in the above nginx config file by removing the two lines that start with auth_basic

Setting up Samba

Now we just need a way to mount our munki_repo on a mac so we can do administrative things. Samba uses a separate set of passwords than the standard Linux system accounts (stored in /etc/samba/smbpasswd), so you’ll need to create a Samba password for yourself.

sudo smbpasswd -a munki
#output on the following lines
New SMB password: *****
Retype new SMB password: ****
Added user munki.

Now we need to share the munki_repo. Once “smb.conf” has loaded, add this to the very end of the file:
sudo nano /etc/samba/smb.conf

path = /usr/local/munki_repo
available = yes
valid users = munki      
read only = no
browseable = yes
public = no
writable = yes

Test for errors with the config file with: testparm

Now we must restart samba.
sudo /etc/init.d/smbd reload

From your mac you will be able to access the munki_repo with the following: smb://


We now have a working munki_repo fully configured and ready for use to start importing packages into the repo. If you are really new to Munki, this takes care of the “Demonstration Setup” section from the munki wiki. To start populating Munki with manifests, packages, and more I would recommend using MunkiAdmin.

How to configure Nginx,
Configuration - Official nginx documentation,
Samba Setup,
Basic Http Auth with Nginx,