attawayinc

Debloating Nox

Nox, despite being the most feature-filled Android emulator, has a lot of negativity surrounding it due to their antics when it comes to making income off of their program. It is known for running repeated advertisments in the background, calling home and passing along system information (outside of your Android instance) as well as a vast amount of potentially sensitive data in an encrypted payload back to their multitude of servers. With the following preventitive measures, we can stop a majority of this happening as well as greatly improve the overall performance.

Download and Install a fresh copy of Nox. The latest version is fine (for now). If you already have it installed, that is fine too. No need to reinstall.
Enable Root Mode on Nox by clicking the gear icon and then checking the Root Startup box.
Install a new Launcher from the Play Store. ANYTHING but Nox's default. I suggest [Nova Launcher](https://play.google.com/s

Setup multiple git identities & git user informations

/!\ Be very carrefull in your setup : any misconfiguration make all the git config to fail silently ! Go trought this guide step by step and it should be fine 😉

Setup multiple git ssh identities for git

Generate your SSH keys as per your git provider documentation.
Add each public SSH keys to your git providers acounts.
In your ~/.ssh/config, set each ssh key for each repository as in this exemple:

GENERATORS:

Text Content Generator - http://www.lipsum.com
Favicon Generator - http://tools.dynamicdrive.com/favicon
Data Generator - https://mockaroo.com/
Mobile Mockup Generator - https://mockuphone.com
Logo Generator - https://www.logaster.com
UUID Generator - https://www.uuidgenerator.net/
Hash Generator - https://passwordsgenerator.net/sha256-hash-generator/
Ultimate Code Generator - https://webcode.tools/

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

	### Preseed for Ubuntu 16.04.3 LTS
	# Derived from: https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

	### Localization
	# Preseeding only locale sets language, country and locale.
	d-i debian-installer/locale string en_US.UTF8
	d-i localechooser/supported-locales multiselect en_US.UTF-8
	d-i console-setup/ask_detect boolean false
	d-i keyboard-configuration/xkb-keymap select GB

	# Run a development Elastic and Kibana quickly

	# Create a docker network for both containers to communicate
	docker network create elastic

	# Use OSS versions (the default ones include x-pack, that has to be configured, I couldn't get it working out of the box)
	# Name your Elastic container and make it use the network your created
	docker run --name smd-elastic -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" --network=elastic -d docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.2

	# Reference the name you gave to the Elastic container in the env variable and also make it use the network you created

	MIT License

	Copyright (c) 2018 Noel Bundick

	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:

	# ---- Base Node ----
	FROM node:carbon AS base
	# Create app directory
	WORKDIR /app

	# ---- Dependencies ----
	FROM base AS dependencies
	# A wildcard is used to ensure both package.json AND package-lock.json are copied
	COPY package*.json ./
	# install app dependencies including 'devDependencies'

	# Based on blogpost https://www.codelitt.com/blog/my-first-10-minutes-on-a-server-primer-for-securing-ubuntu/

	# Update and upgrade all
	sudo apt-get update
	sudo apt-get upgrade -y

	# install packages
	sudo apt-get install ufw fail2ban unattended-upgrades libpam-google-authenticator -y

	# Setup ufw

	# set the base image to Debian
	# https://hub.docker.com/_/debian/
	FROM debian:latest

	# replace shell with bash so we can source files
	RUN rm /bin/sh && ln -s /bin/bash /bin/sh

	# update the repository sources list
	# and install dependencies
	RUN apt-get update \