Skip to content

Instantly share code, notes, and snippets.

consul.*.runtime.*
name="consul_runtime"
type="$2"
host="{{ inventory_hostname }}"
consul.runtime.total_gc_pause_ns
name="consul_runtime_total_gc_pause_ns"
type="$2"
host="{{ inventory_hostname }}"

WannaCry|WannaDecrypt0r NSA-Cybereweapon-Powered Ransomware Worm

  • Virus Name: WannaCrypt, WannaCry, WanaCrypt0r, WCrypt, WCRY
  • Vector: All Windows versions before Windows 10 are vulnerable if not patched for MS-17-010. It uses EternalBlue MS17-010 to propagate.
  • Ransom: between $300 to $600. There is code to 'rm' (delete) files in the virus. Seems to reset if the virus crashes.
  • Backdooring: The worm loops through every RDP session on a system to run the ransomware as that user. It also installs the DOUBLEPULSAR backdoor. (source: malwarebytes)
  • Kill switch: If the website www.iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com is up the virus exits instead of infecting the host. (source: malwarebytes). This domain has been sinkholed, stopping the spread of the worm.

SECURITY BULLETIN AND UPDATES HERE: https://technet.microsoft.com/en-us/library/security/ms17-010.aspx https://blog.malwarebytes.com/threat-analysis/2017/05/the-worm-that-spreads-wanacrypt0r/

@pradeepchhetri
pradeepchhetri / README.md
Created May 4, 2017 17:56 — forked from polvi/README.md
HDFS of Kubernetes

Easiest HDFS cluster in the world with kubernetes.

Inspiration from kimoonkim/kubernetes-HDFS

kubectl create -f namenode.yaml
kubectl create -f datanode.yaml

Setup a port-forward to so you can see it is alive:

@pradeepchhetri
pradeepchhetri / installation-deb.log.md
Last active February 20, 2017 19:35
Riemann installation on Debian 8 and CentOS 7
root@debian8:~# dpkg -l | grep systemd
ii  libsystemd0:amd64              215-17+deb8u6               amd64        systemd utility library
ii  systemd                        215-17+deb8u6               amd64        system and service manager
ii  systemd-sysv                   215-17+deb8u6               amd64        system and service manager - SysV links
root@debian8:~# cat /run/systemd/generator.late/riemann.service
# Automatically generated by systemd-sysv-generator
Traceback (most recent call last):
File "nix_run_setup.py", line 8, in <module>
exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))
File "setup.py", line 72, in <module>
'Topic :: Utilities',
File "/nix/store/2sw5h60dms3ym4nasg4vldv2rn2m5swl-python-2.7.13/lib/python2.7/distutils/core.py", line 111, in setup
_setup_distribution = dist = klass(attrs)
File "/nix/store/g6689bpmb9wiyxsnk53vdy82kk3xfkfd-python2.7-bootstrapped-pip-9.0.1/lib/python2.7/site-packages/setuptools/dist.py", line 318, in __init__
_Distribution.__init__(self, attrs)
File "/nix/store/2sw5h60dms3ym4nasg4vldv2rn2m5swl-python-2.7.13/lib/python2.7/distutils/dist.py", line 287, in __init__
@pradeepchhetri
pradeepchhetri / git-dmz-flow.md
Created January 18, 2017 10:01 — forked from djspiewak/git-dmz-flow.md
Git DMZ Flow

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

  • Two developers working on independent features must never be blocked by each other
    • No code freeze! Ever! For any reason!
  • A developer must be able to base derivative work on another developer's work, without waiting for any third party
  • Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
  • Developers must be able to work on multiple features simultaneously, or at lea
@pradeepchhetri
pradeepchhetri / nn_from_scratch.py
Created August 27, 2016 08:03 — forked from sthware/nn_from_scratch.py
A partially-refactored, variable-name-expanded, heavily commented version of Britz's "Neural Network from scratch" code.
#!/usr/bin/env python
## NAME
## Neural Network from scratch
##
## DESCRIPTION
## A partially-refactored, variable-name-expanded, heavily commented version
## of Denny Britz's code. Original blog post:
## http://www.wildml.com/2015/09/implementing-a-neural-network-from-scratch/
##
$ dig +short api.twilio.com
prod-api-88703523.twilio.com.
prod-api-us1-308668521.us-east-1.elb.amazonaws.com.
54.210.154.224
54.85.119.182
54.88.47.86
54.175.50.42
54.209.197.21
107.23.47.27
52.2.38.199
; -*- mode: clojure; -*-
; vim: filetype=clojure
(logging/init {:file "riemann.log" :console true})
(tcp-server {:tls? false
:key "test/data/tls/server.pkcs8"
:cert "test/data/tls/server.crt"
:ca-cert "test/data/tls/demoCA/cacert.pem"})
(defn maintenance-mode?
"Is Riemann currently in maintenance mode?"
[]
; Take an expression representing a query for maintenance mode
(->> '(and (= :host nil)
(= :service "maintenance-mode"))
; Search the current Riemann core's index for any matching events
(riemann.index/search (:index @core))
; Take the first match
first