Alexandru Duzsardi aduzsardi

Enable LDAP over SSL (LDAPS) for Microsoft Active Directory servers

By default Microsoft active directory servers will offer LDAP connections over unencrypted connections (boo!).

The steps below will create a new self signed certificate appropriate for use with and thus enabling LDAPS for an AD server. Of course the "self-signed" portion of this guide can be swapped out with a real vendor purchased certificate if required.

Steps have been tested successfully with Windows Server 2012R2, but should work with Windows Server 2008 without modification. Will require both a system with OpenSSL (ideally Linux/OSX) and (obviously) a Windows Active Directory server.

Create root certificate
Import root certificate into trusted store of domain controller
Create client certificate

Verify and Repair Disk Permissions via Terminal (Mac OS X)

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

Creating a bootable macOS USB installer

First, plug in an 8GB (or bigger) USB drive, and use Disk Utility to erase it
If you use the default settings, you should wind up with a blank drive at /Volumes/Untitled.

With that volume in place, and with the macOS installer sitting in /Applications/Install\ macOS\ [VERSION].app, run the following command in your terminal to create a bootable install media (for Sierra):

sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ Sierra.app --nointeraction

	## Install necessary packages
	$ sudo apt-get install virtualbox-ose qemu-utils genisoimage cloud-utils

	## get kvm unloaded so virtualbox can load
	$ sudo modprobe -r kvm_amd kvm_intel
	$ sudo service virtualbox stop
	$ sudo service virtualbox start

	## URL to most recent cloud image of 12.04
	$ img_url="http://cloud-images.ubuntu.com/server/releases/12.04/release"

	# Disable Gnome Keyring SSH agent in Ubuntu
	# To allow using ssh-agent from OpenSSH, mainly because
	# gnome-keyring does not like EC-type SSH keys

	# as regular user (for which to disable):
	systemctl --user mask gnome-keyring-ssh.service

	pam-auth-update
	# and disable "GNOME Keyring Daemon..."
	# which probably also disables automatic keyring unlocking on login

-# NB this depends on devcon. you must install it from chocolatey with choco install -y devcon.portable
-$devcon = "$ENV:ProgramData\Chocolatey\Lib\devcon.portable\Devcon$(if ($ENV:PROCESSOR_ARCHITECTURE -like '*64') {'64'} else {'32'}).exe"
-Get-NetAdapter `
-    | Where-Object {$_.Virtual} `
-    | Where-Object {$_.DriverFileName -like 'VBox*.sys'} `
-    | ForEach-Object {
-        Write-Host "Removing the $($_.InterfaceAlias) interface..."
-        $result = &$devcon remove "@$($_.PnPDeviceID)"

	#!/bin/sh

	###
	# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer)
	# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos
	###

	# Alot of these configs have been taken from the various places
	# on the web, most from here
	# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx