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
| #!/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 |
| #!/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' |
| 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" |
