This is just a dump of discoveries, experience, and general insights.
ℹ️ Does not contain any assembly related information.
ℹ️ A lot of this applies to 3D printers in general.
Divided into the following documentation, in order:
#!/usr/bin/env bash | |
echo 'Adding Dell repository...' | |
# https://www.dell.com/community/XPS/XPS-13-9300-Does-fingerprint-reader-work-on-linux/td-p/7514958 | |
sudo sh -c 'cat > /etc/apt/sources.list.d/focal-dell.list << EOF | |
deb http://dell.archive.canonical.com/updates/ focal-dell public | |
# deb-src http://dell.archive.canonical.com/updates/ focal-dell public | |
deb http://dell.archive.canonical.com/updates/ focal-oem public | |
# deb-src http://dell.archive.canonical.com/updates/ focal-oem public |
""" | |
Author: Matteo 'uf0' Malvica @matteomalvica | |
Tested with IDA 7.5 and Py3 | |
Original plugin: https://github.com/FSecureLABS/win_driver_plugin | |
""" | |
def getopvalue(addr): | |
"""Returns the value of the second operand to the instruction at `addr` masked to be a 32 bit value""" | |
return idc.get_operand_value(addr, 1) & 0xffffffff |
#!/bin/bash | |
# quick and dirty bash script to extract .gnu_debugdata section | |
# from ELF binaries to generate an IDC script that adds these | |
# names as symbols | |
# --rpw, 2020-06-21 | |
SYMBOLFILE=debugdata_symbols.elf | |
if [ $# -lt 1 ]; then | |
echo "you need to supply a path to a binary" |
#!/usr/bin/env python3 | |
"""A small example utility to demonstrate r2pipe scripting | |
by extracting resources from a file. | |
Written as an example for someone on IRC. | |
--Towel, 2019 | |
""" | |
import r2pipe |
# make sure You have installed the infinality patches | |
export INFINALITY_FT_FILTER_PARAMS="8 17 50 17 8" | |
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="0" | |
export INFINALITY_FT_FRINGE_FILTER_STRENGTH="55" | |
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="0" | |
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="0" | |
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH="20" | |
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH="0" | |
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH="0" |
These comments are based on a few years of experience working with WSL. It's based on this tutorial:
https://blog.ropnop.com/configuring-a-pretty-and-usable-terminal-emulator-for-wsl/
And are basically updates to make it more relevant.
In the past, to make the WSL run a command from cmd or somewhere else, you had to run the bash.exe
program from windows, which fired up bash (and always bash) in the WSL and made it execute a command.
# 75.0.3770.142 | |
0x04b58615 7626 => 9090 0x04b58615 | |
0x04b5861d 31c0488945 => 9090909090 0x04b5861d | |
Due to a beautiful bug in Chromium, it turns out you don't need this binary patch and can **enable** subpixel positioning by asking Chrome **to disable it**: https://bugs.chromium.org/p/chromium/issues/detail?id=824153#c39 | |
Needless to say, I won't be maintaining this gist any longer. |
For adding temporary logging to help understand behavior. For when it is impractical to use Frida to instrument Frida.
Choose one of these and copy-paste it into e.g. lib/interfaces/session.vala
,
then use log_event ("name='%s'", name);
to log.
When something appears to be hanging, try applying: x-async-debug.patch
.
diff --git a/fs/proc/cmdline.c b/fs/proc/cmdline.c | |
index 14a4c5887848..ebce46d998b0 100644 | |
--- a/fs/proc/cmdline.c | |
+++ b/fs/proc/cmdline.c | |
@@ -2,10 +2,13 @@ | |
#include <linux/init.h> | |
#include <linux/proc_fs.h> | |
#include <linux/seq_file.h> | |
+#include <asm/setup.h> | |
+ |