Lake Chan StoneMoe

Download docker-compose.yml to dir named sentry
Change SENTRY_SECRET_KEY to random 32 char string
Run docker-compose up -d
Run docker-compose exec sentry sentry upgrade to setup database and create admin user
(Optional) Run docker-compose exec sentry pip install sentry-slack if you want slack plugin, it can be done later
Run docker-compose restart sentry
Sentry is now running on public port 9000

https://docs.docker.com/compose/compose-file/#env_file

Transmission Blocklist

The Transmission torrent client has an option to set a Blocklist, which helps protect you from getting caught and having the DMCA send a letter/email.

It's as simple as downloading and installing the latest client:

https://transmissionbt.com/download/

朴素VPN：一个纯内核级静态隧道

由于路由管控系统的建立，实时动态黑洞路由已成为最有效的封锁手段，TCP连接重置和DNS污染成为次要手段，利用漏洞的穿墙方法已不再具有普遍意义。对此应对方法是多样化协议的VPN来抵抗识别。这里介绍一种太简单、有时很朴素的“穷人VPN”。

朴素VPN只需要一次内核配置（Linux内核），即可永久稳定运行，不需要任何用户态守护进程。所有流量转换和加密全部由内核完成，原生性能，开销几乎没有。静态配置，避免动态握手和参数协商产生指纹特征导致被识别。并且支持NAT，移动的内网用户可以使用此方法。支持广泛，基于L2TPv3标准，Linux内核3.2+都有支持，其他操作系统原则上也能支持。但有两个局限：需要root权限；一个隧道只支持一个用户。

朴素VPN利用UDP封装的静态L2TP隧道实现VPN，内核XFRM实现静态IPsec。实际上IP-in-IP隧道即可实现VPN，但是这种协议无法穿越NAT，因此必须利用UDP封装。内核3.18将支持Foo-over-UDP，在UDP里面直接封装IP，与静态的L2TP-over-UDP很类似。

创建一个朴素VPN

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

	using namespace System.Management.Automation

	Register-ArgumentCompleter -CommandName ssh,scp,sftp -Native -ScriptBlock {
	param($wordToComplete, $commandAst, $cursorPosition)
	$knownHosts = Get-Content ${Env:HOMEPATH}\.ssh\known_hosts `
	\| ForEach-Object { ([string]$_).Split(' ')[0] } `
	\| ForEach-Object { $_.Split(',') } `
	\| Sort-Object -Unique

	# For now just assume it's a hostname.

	using System;
	using System.Security.Cryptography;

	// ReSharper disable SuggestVarOrType_SimpleTypes - BCL rules
	namespace Crypto
	{
	/// <summary>
	/// Simple implementation of ECIES (Elliptic Curve Integrated Encryption Scheme) based on http://www.secg.org/sec1-v2.pdf, section 5.1
	/// Things not implemented:
	/// - Encoding parameters using compressed points; only uncompressed points are used