Multiple keys must be generated to get the final master key.
- Generate the composite key.
- Generate the transformed key from the composite key.
- Generate the master key from the transformed key.
| ּ_בּ | |
| בּ_בּ | |
| טּ_טּ | |
| כּ‗כּ | |
| לּ_לּ | |
| מּ_מּ | |
| סּ_סּ | |
| תּ_תּ | |
| ٩(×̯×)۶ | |
| ٩(̾●̮̮̃̾•̃̾)۶ |
| * g o a t s e x * g o a t s e x * g o a t s e x * | |
| g g | |
| o / \ \ / \ o | |
| a| | \ | | a | |
| t| `. | | : t | |
| s` | | \| | s | |
| e \ | / / \\\ --__ \\ : e | |
| x \ \/ _--~~ ~--__| \ | x | |
| * \ \_-~ ~-_\ | * | |
| g \_ \ _.--------.______\| | g |
| #include <stdint.h> | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #ifndef BUFFER | |
| #define BUFFER 4096 | |
| #endif | |
| uint8_t msg[BUFFER]; | |
| /* CRC-32, eg. ethernet */ |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width,initial-scale=1"> | |
| <title>title</title> | |
| <link rel="stylesheet" href="style.css"> | |
| <script src="script.js"></script> | |
| </head> | |
| <body> |
| "use strict"; | |
| /* | |
| tumblr-downloader.js - a Node.js script to download all media files posted in | |
| a Tumblr blog, most recent first. | |
| Usage: | |
| node tumblr-downloader.js | |
| Options - domain to download from, API key, and so on - are exposed below. |
I’m currently working (I’m just at the beginning, and I’m quite slow) on a personal project that will use Keepass files (kdb and kdbx).
I tried to find some documentation about .kdb and .kdbx format, but I didn’t find anything, even in the Keepass official website. I you want to know how these file formats are structured, you must read Keepass’s source code. So I wrote this article that explains how Keepass file format are structured, maybe it will help someone.
Network namespaces are an important component of containerization in Linux. A network namespace (netns) allows a running process to see different network interfaces, routes, and firewall rules from the rest of the system. There are a number of use cases for network namespaces, such as running multiple servers, testing/staging environments and providing isolation of services.
We begin by creating a generic systemd service for creating a named network namespace. I add the following to /usr/lib/systemd/system/netns@.service. In systemd, the @ mean the service takes a parameter which is passed to the unit via %i. E.g, we can run sudo systemctl start netns@webserver.service.
| #include <stdint.h> | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| // munged from https://github.com/simontime/Resead | |
| namespace sead | |
| { | |
| class Random | |
| { |
| -- happy avril 14th :))))))))))))))))))))))))))))))))))))))) | |
| do | |
| let bars = 4 | |
| key = "8" | |
| righthand = "[[4 -3] [0 _ _ _ _ _ 0]] [[-3, -8] [7 5 4 0]]" | |
| lefthand = "[0 9 12 16] [4 12 16 19] [5 12 17 19] [2 12 17 16]" | |
| d1 $ slow bars | |
| $ stack [ | |
| n (righthand + key + "<24 36>/2"), |