Tyler Langlois tylerjl

Better SSH Authorized Keys Management

A seemingly common problem that people encounter is how to handle all of your users authorized_keys file.

People struggle over management, ensuring that users only have specific keys in the authorized_keys file or even a method for expiring keys. A centralized key management system could help provide all of this functionality with a little scripting.

One piece of functionality overlooked in OpenSSH is the AuthorizedKeysCommand configuration keyword. This configuration allows you to specify a command that will run during login to retrieve a users public key file from a remote source and perform validation just as if the authorized_keys file was local.

Here is an example directory structure for a set of users with SSH public keys that can be shared out via a web server:

Mods are mostly only available for 1.8 (not 1.8.1-1.8.3) :(

MultiMC
1.8 mods
Forge mods
- Inventory Tweaks
- Zyin's HUD
- Not Enough Items & CCC
- Waila (What am I looking at - download) You can skip this, you get the same functionality from NEI
LiteLoader mods

Simple Security Guidelines

Using an iDevice? (Best option)

Use an iPod or an iPad without a SIM card
Use an iPhone
Do not jailbreak
Always upgrade to new iOS versions
Use Brave browser

Need Secure chat?

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

	#!/bin/bash

	# As the "bufferbloat" folks have recently re-discovered and/or more widely
	# publicized, congestion avoidance algorithms (such as those found in TCP) do
	# a great job of allowing network endpoints to negotiate transfer rates that
	# maximize a link's bandwidth usage without unduly penalizing any particular
	# stream. This allows bulk transfer streams to use the maximum available
	# bandwidth without affecting the latency of non-bulk (e.g. interactive)
	# streams.

	#!/bin/bash

	# As the "bufferbloat" folks have recently re-discovered and/or more widely
	# publicized, congestion avoidance algorithms (such as those found in TCP) do
	# a great job of allowing network endpoints to negotiate transfer rates that
	# maximize a link's bandwidth usage without unduly penalizing any particular
	# stream. This allows bulk transfer streams to use the maximum available
	# bandwidth without affecting the latency of non-bulk (e.g. interactive)
	# streams.

	#cloud-config
	---
	coreos:
	units:
	- name: update-fleet-metadata.service
	command: start
	content: \|-
	[Unit]
	Description=Update Fleet metadata tag
	Before=fleet.service

	#!/usr/bin/env ruby

	# Synchronizes ZFS filesystems.
	#
	# Takes three args: source pool, destination pool, and filesystem name.
	#
	# Syncs most recent snapshot of filesystem from source to destination pool,
	# using incremental transfer if possible.

	# Take a snapshot line from zfs list -t snapshot and emit a struct

	# jekyll-readtime
	# 2015 Ron Scott-Adams, Licensed under MIT:
	# https://tldrlegal.com/license/mit-license
	# Original work: https://gist.github.com/zachleat/5792681

	# Outputs the estimated time the average person might take to read the content.
	# 200 is a round figure based on estimates gathered from various studies.
	# http://www.ncbi.nlm.nih.gov/pubmed/18802819

	# Usage: {{ page.content \| readtime }}