- Monterey : https://apps.apple.com/fr/app/macos-monterey/id1576738294?mt=12
- Catalina : https://apps.apple.com/us/app/macos-catalina/id1466841314?mt=12
- Mojave : https://apps.apple.com/us/app/macos-mojave/id1398502828?mt=12
- High Sierra : https://apps.apple.com/us/app/macos-high-sierra/id1246284741?mt=12
- Sierra : https://apps.apple.com/us/app/macos-sierra/id1127487414?mt=12
- El Capitan : https://apps.apple.com/us/app/os-x-el-capitan/id1147835434?mt=12
- Big Sur https://apps.apple.com/us/app/macos-big-sur/id1526878132?mt=12
I've spent the day trying to get this setup working with GitHub and given the number of gotcha's I encountered, it seemed like a good idea to document how I finally got this working with as few hacks as possible. There's a lot of documentation out there (some of it old and misleading) and committing here for posterity will help me remember this when I inevitably need to do this again.
Passwords are simply not enough these days. Regardless of the company, breaches (and the associated Personally Identifiable Information harvested) are a matter of not if, but when. There are a number of things you can do to protect yourself, but being on the tin-foil-hat side of paranoia, means there are a few Commandents that I adhere to (and recommend for other folks)[Insert link to Fight Club Rules for the Secure Internet].
That being said, if you use 2-factor authentication and have committed to using a hardware token such as the Yubikey, then you're already ahead of the curve. The problem is that wh
From: http://web.archive.org/web/20160904174444/http://andreafrancia.it/2010/03/understanding-the-output-of-rsync-itemize-changes.html | |
As you may know the rsync's --delete options if misused could make severe damage. | |
To prevent this you can use the --itemize-change and the --dry-run options to figure out how the command will behave before launching the real one. | |
The output will be something like that: | |
.d..t..g... ./ | |
.f...p.g... Something.pdf |
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 operatore@146.148.22.123 | |
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 "ConfigFormat.h" | |
#include <string.h> | |
const struct ConfigFormatField *ConfigFormatGetFieldByName(const struct ConfigFormat *Format, const char *Name, void *Structure) | |
{ | |
static struct ConfigFormatField Field; | |
for (size_t n = 0; n < Format->num_members; n++) { | |
if (strcmp(Name, Format->names[n]) != 0) { | |
continue; |
#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.