├── amd64
│ ├── libglib1.2ldbl_1.2.10-19_amd64.deb
│ └── libgtk1.2_1.2.10-18.1_amd64.deb
├── i386
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Working Huawei E3372h-153 SETPORT mappings | |
replacing A1,A2 with FF turns off need for usb_modeswitch | |
AT^SETPORT="A1,A2;12,1,16,A1,A2" | |
^GETPORTMODE: TYPE: WCDMA: huawei,PCUI:0,MDM:1,NDIS:2,CDROM:3,SD:4, | |
AT^SETPORT="A1,A2;1,12,16,A1,A2" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# Hotplug trigger script. Put this in /etc/hotplug.d/iface, and ensure this file is backed up over upgrade. | |
[ "$ACTION" = ifup ] || exit 0 | |
[ "$INTERFACE" = wan ] || exit 0 | |
logger -t package_autoinstall "Checking for package autoinstallation due to $ACTION of $INTERFACE ($DEVICE)" | |
cd /root | |
./package_autoinstall.sh |
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.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
34T62-N84MB-7DQGY-G7XGT-YTQ63 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
DATE=`date -Idate` | |
USER="root" | |
HOSTS=("<host1>" ... "<hostn>") | |
commit_single_host_to_git () | |
{ | |
local host=${1} | |
local backup_filename="backup-${host}-${DATE}.tar.gz" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
USB_GPIO=21 | |
DELAY=1 | |
gpio_value="/sys/class/gpio/gpio${USB_GPIO}/value" | |
echo 0 > ${gpio_value} | |
sleep ${DELAY} | |
echo 1 > ${gpio_value} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
USER="" | |
SERVER_HOST="" | |
SERVER_PORT="22" | |
REMOTE_PORT="22" | |
LOCAL_PORT="1234" | |
IDENTITY=$(mktemp) | |
KNOWN_HOSTS=$(mktemp) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# All possible descrypt hashes of the password 'admin', using all possible salts. | |
# From https://github.com/roycewilliams/kens-salty-rainbow | |
# If you find a device that always uses one of these, let me know. | |
..xpoEyRReGzk | |
./nlIXYriZaB2 | |
.08iPeaCLti3E | |
.1fH80ykoJAyI | |
.23PstrXfk7Nw | |
.37vRhjo4ZP66 | |
.4nTonCOGSWyU |
OlderNewer