| defmodule MyApp do | |
| use Application | |
| def start(_type, _args) do | |
| import Supervisor.Spec, warn: false | |
| children = [ | |
| Plug.Adapters.Cowboy.child_spec(:http, MyApp.Router, [], [ | |
| dispatch: dispatch | |
| ]) |
$ ssh remote-host "epmd -names"
epmd: up and running on port 4369 with data:
name some_node at port 58769
Note the running on port for epmd itself and the port of the node you're interested in debugging. Reconnect to the remote host with these ports forwarded:
$ ssh -L 4369:localhost:4369 -L 58769:localhost:58769 remote-host
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
Inspired by "Parsing CSS with Parsec".
Just quick notes and code that you can play with in REPL.
By @kachayev
| -module(niftest). | |
| -export([add/2]). | |
| -on_load(init/0). | |
| init() -> | |
| ok = erlang:load_nif("./nif", 0). | |
| add(_, _) -> | |
| exit(nif_library_not_loaded). |
| -module(picoparser). | |
| -export([ str/0 | |
| , str/1 | |
| , str_/0 | |
| , seq/1 | |
| , any/1 | |
| , whatever/0 | |
| , many/1 | |
| , match/1 |
| # | |
| # OSX packet filter rules | |
| # References: | |
| # * https://gist.github.com/scy/8122924 | |
| # | |
| # The purpose of this config is to make sure that my system uses the | |
| # privateInternetAccess VPN connection for everything and not to communicate | |
| # unencrypted when the VPN connection goes down. Therefore, I block | |
| # everything on the physical interfaces except for ICMP, DHCP, DNS and the |
| module Hedis | |
| ( | |
| -- * Application classes | |
| HasRedis(..) | |
| -- * App-wrapped redis runner | |
| , redis | |
| -- * Re-export other stuff from "Database.Redis" | |
| , module R | |
| ) where |
You should never let passwords or private data be transmitted over an untrusted network (your neighbor’s, the one at Starbucks or the company) anyway, but on a hacker congress like the #30C3, this rule is almost vital.
Hackers get bored easily, and when they’re bored, they’re starting to look for things to play with. And a network with several thousand connected users is certainly an interesting thing to play with. Some of them might start intercepting the data on the network or do other nasty things with the packets that they can get.
If these packets are encrypted, messing with them is much harder (but not impossible! – see the end of this article). So you want your packets to be always encrypted. And the best way to do that is by using a VPN.
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
