jnovack

Proxy SSL Client Certificate Details through NGINX Load-Balancer

SSL connections will terminate and authenticate at the frontend and proxy the connection to the backend.

This should be used in cases:

• you DO NOT have direct access to the backend servers
• you DO NOT require direct client AUTHENTICATION on the backend servers
• you TRUST incoming connections to the backend servers

jnovack

Proxy SSL Client Certificate through NGINX Load-Balancer

The frontend stream proxy_pass can be used for load-balancing without SSL off-loading. All SSL connections will be terminated on the backend and client certificate information can be properly authenticated.

This should be used in cases:

• you have enough CPU to decrypt SSL on the backend servers
• you require direct client AUTHENTICATION on the backend servers

Backend

jnovack

# Generate a BaseSystem.dmg with 10.13 Install Packages
hdiutil attach /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg -noverify -mountpoint /Volumes/highsierra
hdiutil create -o /tmp/HighSierraBase.cdr -size 7000m -layout SPUD -fs HFS+J
hdiutil attach /tmp/HighSierraBase.cdr.dmg -noverify -mountpoint /Volumes/install_build
asr restore -source /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erase

# Do not copy the core, recovery CD ONLY
cp /Volumes/highsierra/Packages/EmbeddedOSFirmware.pkg /Volumes/OS\ X\ Base\ System/System/Installation/
cp /Volumes/highsierra/Packages/FirmwareUpdate.pkg /Volumes/OS\ X\ Base\ System/System/Installation/
cp /Volumes/highsierra/Packages/OSInstall.mpkg /Volumes/OS\ X\ Base\ System/System/Installation/

jnovack

As I tried a bare metal installation of VMware vSphere 6.5 on a fresh Mac mini I ran into the condition that I wasn’t able to boot from a USB stick. It simply didn’t show up as a Startup Disk in macOS in the respective application to flag it as a boot device! That’s something that always had been working flawlessly.

After hours of intensive research and trial and error I finally was able to boot into vSphere 6.5 from a USB stick.

Here’s how:

jnovack

This extends the native SmartThings device handler to support editing the device's parameters from the SmartThings GUI, and to support the use of one or more of the controller's channels in IN/OUT mode.

First go to http://bit.ly/rgbwfib and select all, copy. Then Google search SmartThings IDE . Log in there, and then click on "My Device Handlers" and add new. Click "From Code" along the top then paste in the box. Hit "Save"

jnovack

#!/usr/bin/python
#
# Copyright 2011 VMware, Inc. All rights reserved.
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#

jnovack

Keybase proof

I hereby claim:

• I am jnovack on github.
• I am jnovack (https://keybase.io/jnovack) on keybase.
• I have a public key whose fingerprint is BF9C 783D 2222 5964 3191 04A6 0CD0 19C2 B340 6656

To claim this, I am signing this object:

jnovack

#!/bin/sh
file_env() {
    local envVar="$1"
    local fileVar="${envVar}_FILE"
    eval envVarContents="\$${envVar}"
    eval fileVarContents="\$${fileVar}"
    if [ ! -z "$envVarContents" ] && [ ! -z "$fileVarContents" ]; then
        echo >&2 "error: both $envVar and $fileVar are set (but are exclusive)"
        exit 1
    fi

jnovack

!/bin/bash

# `export WIDTH=120` to change the width

## awk-wrap
alias wrap='awk -v WIDTH="${WIDTH:-72}" '\''
{
    gsub("\t"," ")
    $0 = line $0
    while (length <= WIDTH) {

jnovack

# Exposes the ElasticSearch cluster on :9200
#   of all Docker Swarm Nodes (poor man's clustering)
#   [NSFW] X-Pack-Security Disabled, Kibana-Monitoring Enabled

version: '3.7'
services:
  node:
    image: docker.elastic.co/elasticsearch/elasticsearch:6.4.0
    ports:
      - "9200:9200"