Verifying that +byrongibson is my openname (Bitcoin username). https://onename.com/byrongibson
I hereby claim:
- I am byrongibson on github.
- I am byrongibson (https://keybase.io/byrongibson) on keybase.
- I have a public key whose fingerprint is 45A7 4AB0 B07F F974 A05A F5F4 2CA8 ECDB EB0E 0CB7
To claim this, I am signing this object:
NOTE: 534 stars, 106 forks. I love you all. Please contribute tips and edits back to this cheat sheet -- email's will.sargent@gmail.com and you can treat gists like git repositories and send git diffs.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# in /usr/share/xsessions | |
[Desktop Entry] | |
Name=Xmonad GNOME | |
Comment=Tiling window manager | |
TryExec=/usr/bin/gnome-session | |
Exec=gnome-session --session=xmonad | |
Type=XSession |
Meetup: http://www.meetup.com/SF-Bitcoin-Devs/events/175021632/
Original slides: http://www.slideshare.net/ukd1/bitcoin-ops-security-primer
####I Recommendations
- Fix Heartbleed immediately, check the blogs of all services you use for updates on their patching process. http://heartbleed.com/
- Use Cloudflare till you can afford your own security operation
- Enable email DKIM/SPF
- Account state graduation - accounts start with minimal priviledges and earn priviledges over time as trust develops
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FROM base | |
MAINTAINER Brian L. Troutwine "brian@troutwine.us" | |
RUN apt-get update | |
RUN apt-get install -y curl | |
RUN curl -O https://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb | |
RUN dpkg -i erlang-solutions_1.0_all.deb | |
RUN apt-get update |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## The Problem | |
Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.) | |
## The temptingly easy but ultimately wrong solution: | |
Alter the port the script talks to from 8000 to 80: | |
}).listen(80); |