cool fallout backgrounds:
wget https://w.wallhaven.cc/full/{g8/wallhaven-g8kdke.png,lm/wallhaven-lmodop.png,ym/wallhaven-yml9ll.png,j5/wallhaven-j5jdjp.png}archlinux yay hook using "--editor":
~ $ cat ~/.local/bin/yay-pkgbuild-editor.sh
#!/bin/bash
# AMD moment
PKGBUILD_PATH="$1"
PKGBUILD_DIR=$(dirname "$PKGBUILD_PATH")
sed -i \
-e 's/: "${_per_gov:=no}"/: "${_per_gov:=yes}"/' \
-e 's/: "${_tcp_bbr3:=no}"/: "${_tcp_bbr3:=yes}"/' \
-e 's/: "${_processor_opt:=}"/: "${_processor_opt:=native}"/' \
-e 's|"\${_patchsource}/all/0001-cachyos-base-all.patch")|"\${_patchsource}/all/0001-cachyos-base-all.patch"\n "0001-XXX-Restore-old-vblankoff-behavior-for-dgpu.patch")|' \
"$PKGBUILD_PATH"
cp ~/Downloads/0001-XXX-Restore-old-vblankoff-behavior-for-dgpu.patch "$PKGBUILD_DIR/"
cd "$PKGBUILD_DIR" && updpkgsums
exec subl "$PKGBUILD_PATH"
~ $ yay --editor ~/.local/bin/yay-pkgbuild-editor.sh --editmenu --answeredit A --answerclean A --answerdiff N --mflags --skipinteg linux-cachyos
This media is not supported in your browser
VIEW IN TELEGRAM
ffmpeg, vibrant glitch with audio shift:
ffmpeg -stream_loop -1 -i "1.mp4" -stream_loop -1 -i "2.ogg" -filter_complex "[0:v]trim=duration=12,setpts=PTS-STARTPTS, \
hue=H='2*PI*t*3':s=3:enable='gte(t,5)', \
negate=enable='gte(t,5)'[v]; \
[1:a]atrim=start=9:duration=12,asetpts=PTS-STARTPTS,volume=2.8,bass=g=12:f=100[a]" -map "[v]" -map "[a]" -c:v libx264 -c:a aac -t 12 "vibrant_glitch.mp4"
⚡1
This media is not supported in your browser
VIEW IN TELEGRAM
ffmpeg glow effect glitch:
ffmpeg -stream_loop -1 -i "1.mp4" -stream_loop -1 -i "2.ogg" -filter_complex "[0:v]trim=duration=12,setpts=PTS-STARTPTS,split=2[base][glitch]; \
[glitch]gblur=sigma=20:enable='gte(t,5)', \
hue=H='2*PI*t*2':s=2:enable='gte(t,5)'[glitcheffect]; \
[base][glitcheffect]blend=all_mode=screen:all_opacity=0.7:enable='gte(t,5)'[v]; \
[1:a]atrim=start=9:duration=12,asetpts=PTS-STARTPTS,volume=2.7,bass=g=12:f=100[a]" -map "[v]" -map "[a]" -c:v libx264 -c:a aac -t 12 "happy_glitch_original_audio.mp4"
Media is too big
VIEW IN TELEGRAM
freaked interfaces №47
seems modern UWP/XAML notepad adding garbage to the buffer
discover all domains/subdomains a company uses by cert & form proper list:
Useful for generating DNS PBR lists for sites.
curl -s "https://crt.sh/?q=google.com&output=json" | jq -r '.[] | .common_name, .name_value' | sed 's/^\*\.//' | sort -u | grep -E '^[a-zA-Z0-9.-]+$'
Useful for generating DNS PBR lists for sites.
👏1
This media is not supported in your browser
VIEW IN TELEGRAM
Run clean temp chromium in docker native under X11:
there FF dckr laying around
docker run --rm -it --name "chromium-$(date +%s)" --security-opt apparmor:unconfined --cap-add=SYS_ADMIN --net host --device /dev/input --device /dev/snd --device /dev/dri -v "$HOME/Downloads:/downloads" -v "/tmp/chromium-docker:/data" -e PUID="$(id -u)" -e PGID="$(id -g)" -e DISPLAY="$DISPLAY" -e XAUTHORITY="${XAUTHORITY:-$HOME/.Xauthority}" -v "${XAUTHORITY:-$HOME/.Xauthority}:${XAUTHORITY:-$HOME/.Xauthority}:ro" -v /tmp/.X11-unix:/tmp/.X11-unix:ro -v /dev/shm:/dev/shm -v "$HOME/.config/pulse:/home/ubuntu/.config/pulse:ro" -v /etc/machine-id:/etc/machine-id:ro -v "${XDG_RUNTIME_DIR:-/run/user/$(id -u)}/pulse:${XDG_RUNTIME_DIR:-/run/user/$(id -u)}/pulse:ro" -v "${XDG_RUNTIME_DIR:-/run/user/$(id -u)}/bus:${XDG_RUNTIME_DIR:-/run/user/$(id -u)}/bus:ro" -v /var/lib/dbus/machine-id:/var/lib/dbus/machine-id:ro -v /run/dbus:/run/dbus:ro -v /run/udev/data:/run/udev/data:ro -v /etc/localtime:/etc/localtime:ro andrewmackrodt/chromium-x11🤮2
Sys progs debugging Tips & Tricks:
strace is very handy dynamic analysis tool, but extremely verbose.
There how you can tame strace filtering using
For example, if you have a program like:
which executing some programs inside and you're curious about what it's actually trying to do with which argument?
cc this example and try this:
Output will be like so:
telling us that the "./a.out" prog actually made 2 execve calls, the "/usr/bin/ls" program with "/usr" as its argument was running using shell "/bin/sh".
-- Be careful when making inferences about the user/kernel boundary if only a subset of system calls are being monitored. The default is trace=all. strace(1) man.
----
Also, there multiple ways to search|list syscalls:
0.
1.
2.
----
strace is very handy dynamic analysis tool, but extremely verbose.
There how you can tame strace filtering using
trace= param:For example, if you have a program like:
#include <stdlib.h>
int main() { system( " ls /usr " ); };
which executing some programs inside and you're curious about what it's actually trying to do with which argument?
cc this example and try this:
cc 1.c
strace -f -e trace=execve,execveat,fork,vfork,clone,clone3,exit_group ./a.out
Output will be like so:
...
[pid 27862] execve("/bin/sh", ["sh", "-c", "--", " ls /usr "], 0x7ffd668ba8e8 /* 64 vars */) = 0
...
[pid 26344] execve("/usr/bin/ls", ["ls", "/usr"], 0x55edbcf792b0 /* 64 vars */) = 0
...
telling us that the "./a.out" prog actually made 2 execve calls, the "/usr/bin/ls" program with "/usr" as its argument was running using shell "/bin/sh".
-- Be careful when making inferences about the user/kernel boundary if only a subset of system calls are being monitored. The default is trace=all. strace(1) man.
----
Also, there multiple ways to search|list syscalls:
0.
grep exec /usr/include/sys/syscall.h /usr/include/bits/syscall.h /usr/include/asm/unistd*.h
1.
echo '#include <sys/syscall.h>' | cpp -dM | grep exec
2.
ausyscall --dump | grep exec
----
👍1🤔1