Archive for the ‘*nix-tools’ Category
Posted by jpluimers on 2025/02/21
Interesting: [Wayback/Archive] ufrisk/MemProcFS: The Memory Process File System
MemProcFS is an easy and convenient way of viewing physical memory as files in a virtual file system.
Easy trivial point and click memory analysis without the need for complicated commandline arguments! Access memory content and artifacts via files in a mounted virtual file system or via a feature rich application library to include in your own projects!
Analyze memory dump files, live memory via DumpIt or WinPMEM, live memory in read-write mode from virtual machines or from [Wayback/Archive] PCILeech [Wayback/Archive] FPGA hardware devices!
It’s even possible to connect to a remote LeechAgent memory acquisition agent over a secured connection – allowing for remote live memory incident response – even over higher latency low band-width connections! Peek into Virtual Machines with [Wayback/Archive] LiveCloudKd or [Wayback/Archive] VMWare!
Use your favorite tools to analyze memory – use your favorite hex editors, your python and powershell scripts, WinDbg or your favorite disassemblers and debuggers – all will work trivally with MemProcFS by just reading and writing files!
On Windows, there is even the cool tool [Wayback/Archive] evild3ad/MemProcFS-Analyzer: MemProcFS-Analyzer – Automated Forensic Analysis of Windows Memory Dumps for DFIR:
Read the rest of this entry »
Posted in *nix, *nix-tools, Power User, Windows | Tagged: DFIR, memoryforensics, memprocfs | Leave a Comment »
Posted by jpluimers on 2025/02/20
For my link archive: [Wayback/Archive] How to send raw network packets in Python with tun/tap
I never really played around with tun and tap, so this is a nice opportunity to do so. I know they were the base for VPN on Linux, but just now I learned TUN/TAP are not available on nx, but also on Windows. Cool!
Via [Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “how to send raw network packets in Python with tun/tap …”
--jeroen
Posted in *nix, *nix-tools, Development, Ethernet, Hardware, Linux, Network-and-equipment, Power User, Python, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2025/02/14
Running Kubernetes containers on Windows means taking into account a different can of worms than running them on Linux.
For example [Wayback/Archive] Fun with Windows Containers – Popping Calc explains about the various isolation levels and privileges (through runAsUserName) and this helpful advice:
Read the rest of this entry »
Posted in *nix, *nix-tools, Cloud, Containers, Docker, Infrastructure, Kubernetes (k8n), Power User, Windows | Leave a Comment »
Posted by jpluimers on 2025/01/21
Sometimes the XKCD episodes are hard to get, so I wanted a Bookmarklet to navigate to [Wayback/Archive] explain xkcd.
Here is the regular expression to change the domain name part if it matches: [Wayback/Archive] regex101: build, test, and debug regex: VI34VW with this generated sed code:
Read the rest of this entry »
Posted in *nix, *nix-tools, Bookmarklet, Development, JavaScript/ECMAScript, Power User, Scripting, sed, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2024/12/27
A while ago there was an interesting point of using tiered md to both obtain low read latency and write safety on the Google Cloud Platform in [Wayback/Archive] How Discord Supercharges Network Disks for Extreme Low Latency
It is an interesting approach to universally tune performance within the sketched boundaries, but raised some questions as their aim was improving ScyllaDB performance and Unix-like platforms on Google Cloud Platform can supports ZFS.
In this case Discord wanted to improve their ScyllaDB that was already read/written from GCP Persistent Storage and used tiered md to improve that.
Read the rest of this entry »
Posted in *nix, *nix-tools, Cloud, GCP Google Cloud Platform, Google, Hardware, Infrastructure, NVMe, Power User, RAID, SSD | Leave a Comment »
Posted by jpluimers on 2024/12/13
This is from years ago, but I forgot to schedule it, so here it is:
Problem on an E20 (enlightenment using lightdm) image:
- LEAP 15.2 did reach Graphical Target
- Image [Wayback]
openSUSE-Leap-15.2-ARM-E20-raspberrypi3.aarch64-2020.07.08-Build1.34.raw.xz [Wayback] .packages [Wayback] .raw.xz.sha256 [Wayback] [Wayback] .raw.xz.sha256.asc
- Tumbleweed did not.
- Image [Wayback]
openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2020.08.15-Snapshot20200904.raw.xz [Wayback] .packages [Wayback] .raw.xz.sha256 [Wayback] [Wayback] .raw.xz.sha256.asc
Parts of the chat transcript:
Read the rest of this entry »
Posted in *nix, *nix-tools, LEAP, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2024/12/02
Sometimes the best information is outside vendor forums. I think it is the case for this Reddit thread: [Wayback/Archive] Regarding updating Tumbleweed; what is the best way to do it? Appper, zypper dup, zypper up. Which one am i supposed to use? Should i be worried about the vendor changes? And why do i get a message when using ‘zypper up’ saying “The following 35 package updates will NOT be installed”? : openSUSE
Note that specific to openSuSE Tumbleweed you should prefer zypper distr-upgrade over zypper update as per [Wayback/Archive] TUMBLEWEED zypper dup default behavior changed: what is the difference to zypper up?
Be aware this thread is about Tumbleweed, the method to update is byusing dup since it’s a new snapshot. At this point it’s your choice toupdate or not depending on your requirements. If your running out ofkernel modules supplied by third parties, then your tied to theirschedule…. Using zypper up will in the long term create more issuesas well as not supported.
This is especially true as --no-allow-vendor-change has been the default for zypper dist-upgrade for almost a decade now: [Wayback/Archive] PSA: Tumbleweed: –no-allow-vendor-change now default zypper dup behaviour : openSUSE
Read the rest of this entry »
Posted in *nix, *nix-tools, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
The Wiert Corner - irregular stream of stuff 