Let's call the container docker_test1.
$ sudo lxc-create -t download -n docker_test1
...
Follow the prompts on the screen to set up the new container.
| #!/usr/bin/env python | |
| # Author: Guillermo Cespedes <dev.dertin@gmail.com> | |
| # pip install requests http barnum | |
| import requests | |
| import http.cookies | |
| import json | |
| from barnum import gen_data |
| #!/bin/bash | |
| # needs openssl 1.1+ | |
| # needs `basez` https://manpages.debian.org/testing/basez/base32hex.1.en.html | |
| # (but something else that decodes the base64 and re-encodes the raw key bytes | |
| # to base32 is probably fine too) | |
| ##### generate a key | |
| openssl genpkey -algorithm x25519 -out /tmp/k1.prv.pem |
This configuration is provided AS-IS and as an example/reference for those who do not find a working configuration for themselves. It is not always kept up to date and no support is provided.
Assuming:
example.orgturn.example.org1.2.3.410.11.12.13ThisIsASharedSecret-ChangeMeThe following is a writeup of the challenge 'multiple-styles' from the manticore wiki.
If we were to run the command manticore multiple-styles, manticore would begin an automatic analysis of the binary, and would eventually figure out the necessary inputs to reach any code path. However, as this can take an exceptionally long time (depending on the complexity of the binary), we will do some manual analysis of the binary in order to speed things up. Below is an annotated disassembly of the main function, produced by Binary Ninja.
Here is how to create a cloud-init disk image and OS disk image suitable for configuring into a libvirt domain file.
In my case I am naming my domain (a.k.a. virtual machine or VM) xenial with a static IP address of 192.168.0.101.
The filenames "network-config" and "user-data" files are arbitrary, so they can be named with a prefix for the domain, etc.
First, get the cloud image and convert into QCOW2 format:
qemu-img convert -O qcow2 xenial-server-cloudimg-amd64-disk1.img xenial-server-cloudimg-amd64-disk1.qcow2
This is an example realtime data visualization method using Zeppelin, NiFi and Kafka together.
Since NiFi 1.1.0, it provides components to act as a WebSocket server. This example contains a Zeppelin notebook paragraph which uses %angular interpreter to establish a WebSocket connection with NiFi, and draw a pie chart using D3, refreshed automatically as it received updated data from NiFi in realtime manner.
And also, a NiFi template to run a WebSocket server, which exposes latest data for the pie chart. The data can be passed through a Kafka topic.