start new:
tmux
start new with session name:
tmux new -s myname
If: | |
- you add and commit with the wrong email address in git, and | |
- your remote has a hook set up to prevent you from pushing with the bad address | |
Then you need to amend the author of your commit before push can succeed: | |
1. fix your email address in git config: | |
$ git config user.name "Your Name" |
#!/usr/bin/env ruby | |
#require 'active_support/secure_random' | |
require 'rexml/document' | |
wapiti_path = '/home/bperry/tools/wapiti/trunk/src/' | |
sqlmap_path = '/home/bperry/tools/sqlmap/' | |
wapiti_report_path = '/home/bperry/tmp/wapiti_report_' + rand(99999).to_s + '.xml' |
#!/bin/bash | |
## SecurityCenter Backup Script | |
# | |
# This script is intended to create backups of all of the SecurityCenter data | |
# on a daily/weekly/monthly/etc. basis. This is intended to be run as a cronjob | |
# and expect the SysAdmin to have configured the root@localhost mail alias to | |
# route through their email system in-case of errors. An example of how to run | |
# this as a cronjob is below: | |
# | |
# 1 45 * * * root /opt/scripts/backups/sc-backup.sh |
Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.
This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016
# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
# Add the following to your shell init to set up gpg-agent automatically for every shell | |
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
source ~/.gnupg/.gpg-agent-info | |
export GPG_AGENT_INFO | |
else |
This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.
I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.
The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone