httrack example.com -O ./example.com -N100 −%i0 -I0 --max-rate 0 --disable-security-limits --near -v
httrack example.com -O ./example.com-3 -N100 -I0 -N "%p/%n%[month].%t" --max-rate 0 --disable-security-limits --near -v
package main | |
import ( | |
"crypto/aes" | |
"crypto/cipher" | |
"crypto/rand" | |
"fmt" | |
"io" | |
"net" | |
) |
/* | |
Go-Language implementation of an SSH Reverse Tunnel, the equivalent of below SSH command: | |
ssh -R 8080:127.0.0.1:8080 [email protected] | |
which opens a tunnel between the two endpoints and permit to exchange information on this direction: | |
server:8080 -----> client:8080 |
Convenient DeDRM Scripts | |
------------------------- | |
**NOTE**: read https://blog.quaintous.com/2021/02/16/remove-drm-from-ebooks/ to find out what this gist is good for. | |
* ./init.sh: extracts Adobe Digital Editions private key and required files to DeDRM. | |
* ./dedrm: removes DRM from given ebook (pdf/epub) | |
If you are using this for the first time, make sure that you have authenticated your Adobe Digital Editions (ADE) and run './init.sh'. Import any DRM-protected file into ADE and run 'dedrm.sh': |
#include <WiFi.h> | |
#include <SPIFFS.h> | |
#include <ESPAsyncWebServer.h> | |
#include <WebSocketsServer.h> | |
// Constants | |
const char *ssid = "ESP32-AP"; | |
const char *password = "LetMeInPlz"; | |
const char *msg_toggle_led = "toggleLED"; | |
const char *msg_get_led = "getLEDState"; |
I recently set up a host running Ubuntu 14.04 LTS, ubuntu-zfs, and PostgreSQL 9.3. Using the ZFS snapshot feature I was able to make a snapshot of the file system holding the PostgreSQL database, write the snapshot to a compressed file, transfer it to another Ubuntu 14.04 LTS host running ubuntu-zfs, restore it, and launch PostgreSQL using that data directory with all the data (seemingly) intact.
The database is very low-traffic, so I do not know how effective this strategy would be for a busier database.
I take no responsibility if you attempt this setup and it causes data loss or other issues. Use it at your own risk; this document is meant to explain a potential setup and open discussion about limitations and potential improvements.
/* | |
* robot.js | |
* | |
* You'll need three keys in order to unlock the | |
* Algorithm: the red key, the green key, and the | |
* blue key. Unfortunately, all three of them are | |
* behind human-proof barriers. | |
* | |
* The plan is simple: reprogram the maintenance | |
* robots to grab the key and bring it through |
/************* | |
* ambush.js * | |
************* | |
* | |
* Oh. Oh, I see. This wasn't quite part of the plan. | |
* | |
* Looks like they won't let you take the Algorithm | |
* without a fight. You'll need to carefully weave your | |
* way through the guard drones. | |
* |
/********************** | |
* fordingTheRiver.js * | |
********************** | |
* | |
* And there's the river. Fortunately, I was prepared for this. | |
* See the raft on the other side? | |
* | |
* Everything is going according to plan. | |
*/ |
/************* | |
* colors.js * | |
************* | |
* | |
* You're almost at the exit. You just need to get past this | |
* color lock. | |
* | |
* Changing your environment is no longer enough. You must | |
* learn to change yourself. I've sent you a little something | |
* that should help with that. |