December 2018
I made this claim on twitter recently and many people wanted me to go into more detail.
Lots of privacy tech in bitcoin like coinjoin, coinswap, tumblebit and Lightning Network require many entities to come together to agree to make certain kinds of transactions. This creates a requirement that the right resources (coins) have to be in the right place,
| # not an exhaustive list | |
| nsurlsessiond "icloud sync" | |
| fseventsd "macos file system events" | |
| WindowServer "macos windows" | |
| DisplayLinkManager "macos driver" | |
| configd "macos dynamic configuration" | |
| displaypolicyd "macos process" | |
| CommCenter "macos keychain" | |
| kernel_task "macos kernel" |
I've never had great understanding of launchctl but the deprecation of the old commands with launchctl 2 (10.10) has been terrible as all resources only cover the old commands, and documentation for Apple utilities is generally disgracefully bad, with launchctl not dissembling.
Mad props to https://babodee.wordpress.com/2016/04/09/launchctl-2-0-syntax/ which contains most details
Internally, launchd has several domains, but launchctl 1 would only ask for service names,
apt-get install python-pip
pip install shadowsocks
sudo ssserver -p 443 -k password -m aes-256-cfb --user nobody -d start
| socat TCP-LISTEN:<localport> SOCKS4A:localhost:<host>:<remoteport>,socksport=9050 | |
| # for example, to ssh into secret.shell.server.org via tor, do: | |
| $ socat TCP-LISTEN:22222 SOCKS4A:localhost:secret.shell.server.org:22,socksport=9050 & | |
| $ ssh localhost -p 22222 |
| #!/usr/bin/env python | |
| import csv | |
| import datetime | |
| import os | |
| import os.path | |
| import re | |
| import sys | |
| import time | |
| import urllib2 |
Contributed by Fabien Loudet, Linux SysAdmin at Rosetta Stone
Tired of always having to enter your SSH key passphrase when logging in to remote machines?
Here comes ssh-agent. Enter the passphrase once and it will keep it in memory for you
Using ssh-agent in your shell session:
##git mergetool
In the middle file (future merged file), you can navigate between conflicts with ]c and [c.
Choose which version you want to keep with :diffget //2 or :diffget //3 (the //2 and //3 are unique identifiers for the target/master copy and the merge/branch copy file names).
:diffupdate (to remove leftover spacing issues)
:only (once you’re done reviewing all conflicts, this shows only the middle/merged file)
