Various notes for using MKVToolNix.
mkvinfo
lists all elements contained in an MKV container file.
mkvinfo container.mkv
version: "3.1" | |
services: | |
spark-master: | |
image: bde2020/spark-master:2.4.0-hadoop2.7 | |
container_name: spark-master | |
ports: | |
- "8080:8080" | |
- "7077:7077" | |
environment: | |
- INIT_DAEMON_STEP=setup_spark |
// PoC code to demonstrate clipboard monitoring in Windows | |
// using an event-based listener. | |
#include <stdio.h> | |
#include <Windows.h> | |
#define CLASS_NAME L"MY_CLASS" | |
#define WINDOW_NAME L"MY_WINDOW" | |
LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam) { | |
HANDLE hClipData = NULL; |
awk 'NF {sub(/\r/, ""); printf "%s\\n",$0;}' cert-name.pem |
The ssh way | |
Assuming that you have ssh on your ubuntu box. | |
Minikube user: docker password: tcuser | |
First run kubectl proxy & to expose the dashboard on http://localhost:8001 | |
Then expose the dashboard using ssh's port forwarding, executing: | |
ssh -R 30000:127.0.0.1:8001 $USER@192.168.0.20 |
System version | Expected number of burnt fuses (retail) | Expected number of burnt fuses (non-retail) | |
---|---|---|---|
1.0.0 | 1 | 0 | |
2.0.0-2.3.0 | 2 | 0 | |
3.0.0 | 3 | 1 | |
3.0.1-3.0.2 | 4 | 1 | |
4.0.0-4.1.0 | 5 | 1 | |
5.0.0-5.1.0 | 6 | 1 | |
6.0.0-6.1.0 | 7 | 1 | |
6.2.0 | 8 | 1 | |
7.0.0-8.0.1 | 9 | 1 |
#!/bin/bash | |
MINIKUBE_IP=$(minikube ip) | |
MINIKUBE_KEY_LOCATION=${HOME}/.minikube/machines/minikube/id_rsa | |
STARTING_PORT=8080 | |
CURRENT_PORT=${STARTING_PORT} | |
for servicename in $*; do | |
HIGH_PORT=$(kubectl get svc ${servicename} -o custom-columns=':spec.ports[*].nodePort' | tail -n1) | |
if echo $HIGH_PORT | grep -q ,; then |
// | |
// Ref = src | |
// https://www.blackhat.com/docs/eu-17/materials/eu-17-Liberman-Lost-In-Transaction-Process-Doppelganging.pdf | |
// | |
// Credits: | |
// Vyacheslav Rusakov @swwwolf | |
// Tom Bonner @thomas_bonner | |
// | |
#include <Windows.h> |
Tested on Windows 10 x64, Anniversary Update
17.09.2017
Set up an OpenVPN connection following this guide
Generate a TA key and place it in the same folder as the other certificates/keys:
The documentation is okay, but it has some holes, and I had to read it many many times and play with the API myself to "get it" in terms of implementation. So here is a guide that I hope will help someone along the way.
DISCLAIMER: This is by no means the canonical or the most secure way to do this. Below are my findings upon my reading of the docs and the spec. But I might be wrong, very wrong.
This gist is meant to complement the documentation in https://getkong.org/plugins/oauth2-authentication/.
The Resource Owner Password Credentials Grant makes sense if we want to authenticate users who are using our trusted 1st party applications of our own service. (However, you might not want to trust your JavaScript SPA with your refresh token, and maybe you need to store that refresh token in the server on behalf of the SPA if you are paranoid about security. Disclaimer: I am not a security expert)