Jonathan Seawright jseadragon

Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)

Errors, typos, something to say ?

If you want to add a link, comment or send it to me
Feel free to report any mistake directly below in the comment or in DM on Twitter @SwitHak

Other great resources

Royce Williams list sorted by vendors responses Royce List
Very detailed list NCSC-NL
The list maintained by U.S. Cybersecurity and Infrastructure Security Agency: CISA List

Requirements

maim
xclip

Set-up

Set this on your i3 config file ~/.i3/config

# Screenshots

Ubuntu 16.04 on Macbook Pro 10,1 with Encrypted Root

NOTE: This is for dual-booting OS X 10.11 with Ubuntu 16.04.

Install

Preparation in OS X

Resize OS X partition with Disk Utility.

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

Normally, when you diff an [Ansible vault][], all you see is gibberish.

$ git diff -- group_vars/all/vault.yml
diff --git a/group_vars/all/vault.yml b/group_vars/all/vault.yml
index 245ccf4..90bf9ee 100644
--- a/group_vars/all/vault.yml
+++ b/group_vars/all/vault.yml
@@ -1,111 +1,111 @@
 $ANSIBLE_VAULT;1.1;AES256

Provisioning and usage of unprivileged LXC containers via indirect login or script

As I've discovered, managing LXC containers is fairly straightforward, but when building out a system for provisioning out user maintained instances of NodeBB, it was imperative that unprivileged LXC containers were used, so that in the event of shell breakout from NodeBB followed by privilege escalation of the saas user, the root user in the LXC container would only be an unprivileged user on the host machine.

During the course of development, I ran into numerous blockers when it came to managing LXC containers in unexpected circumstances. Namely:

Using LXC in a subshell is not directly supported. This usually happens under one of the following two circumstances:
- After switching users via su or executing lxc-* commands as another user via sudo
- Executing lxc-* commands via a program, application, or script. In my case, a Node.js application.

	First install pip for Python2. Download the get-pip.py file from https://bootstrap.pypa.io/get-pip.py
	$ cd <download location>
	$ sudo -H python ./get-pip.py

	Installing pip also installs Python3
	To run Python3
	$ python3

	Install pip3 by just executing the same file as in the step above, but this time using Python3
	$ sudo -H python3 ./get-pip.py

	#!/usr/bin/env python

	# Tiny Syslog Server in Python.
	##
	# This is a tiny syslog server that is able to receive UDP based syslog
	# entries on a specified port and save them to a file.
	# That's it... it does nothing else...
	# There are a few configuration parameters.

	# create a ramdisk if you want to use stoe logs on the ram disk. (faster thant

	BASE_COMMIT=$(echo {\"diff_id\": ${DIFF_ID}} \| arc call-conduit differential.getdiff \| awk -v RS=',' -v FS=':' '$1~/\"sourceControlBaseRevision\"/ {print $2}' \| tr -d \")

	# Update repo (can be taken care of by jenkins too)
	git fetch --all
	git remote prune origin

	# We only want to test the diff so reset to base
	git reset --hard ${BASE_COMMIT}
	git clean -fdx

	/**
	* Return a timestamp with the format "m/d/yy h:MM:ss TT"
	* @type {Date}
	*/

	function timeStamp() {
	// Create a date object with the current time
	var now = new Date();

	// Create an array with the current month, day and time