#openprocess
Linux is often far behind Windows in implementing APIs for things that ought to be simple. Example task: Given a process ID of a process that is not a descendant, wait until it terminates.

Linux: pidfd_create()+poll(). Linux 5.2 (2019)

Windows: OpenProcess() + WaitForSingleObject(). NT 3.1 (1993)
August 18, 2025 at 2:46 AM
“The #4opens are difficult to mainstream precisely because they redistribute power.

- #opendata challenges information monopolies.
- #opensource challenges technological dependency.
- #openstandards challenge platform lock-in.
- #openprocess challenges hidden governance.

These are practical […]
Original post on hachyderm.io
hachyderm.io
August 3, 2026 at 12:09 PM
The tech is plumbing. The political/social idea is much simpler - commons by default, private by exception. People and content participates in open flows.

#opendata
#opensource
#openprocess
#openstandards

The #4opens are the practical framework for making this work. Keep it simple. Keep it […]
Original post on mastodon.social
mastodon.social
September 12, 2026 at 10:51 AM
My basic stance has not changed: I just keep leaving personal logs, calmly and continuously. But the side effects are becoming huge. Observation, feedback, discovery, and unexpected connections are emerging from the logs themselves. #AI #Logging #OpenProcess
June 12, 2026 at 8:33 PM
You left out @yvesengler.bsky.social because...? Every leadership candidate deserves a seat at the table & the establishment continuing to sideline a campaign thats raised thousands of $s & signed up many members is concerning. NPP welcomed Yves and Tony & invited the rest #ndp #openprocess #cdnpoli
November 2, 2025 at 5:55 PM
The basic design is solo-operable. Even without reactions, the logs keep accumulating as personal records and future data. But when reactions arrive, the observation range expands outward, and the experiment becomes broader. It is not dependency. It is extension. #AI #Logging #OpenProcess
June 12, 2026 at 8:38 PM
Pokémon exists because one kid loved catching bugs.
I made a short documentary about how that childhood hobby eventually led to games, trading cards, and world championships.

www.youtube.com/watch?v=wNwP...
#Pokemon #GameDevelopment #Nintendo #GameHistory #Documentary #Animation #OpenProcess
How Bug Collecting Created Pokémon Tournaments
YouTube video by Open Process
www.youtube.com
August 8, 2026 at 5:40 PM
5️⃣ Debugging infrastructure is attack surface.

Features like OpenProcess and VEH are documented OS abilities; treating them as threats strengthens client resilience.
September 2, 2026 at 7:00 AM
2️⃣ Cheat Engine starts with an allowed Windows handle.

OpenProcess grants VM read/write/operation; later calls change memory from outside the target's context.
August 27, 2026 at 7:01 AM
EvilPsst - Tamper with the EventLog process without an OpenProcess call:

github.com/nothingspeci...
GitHub - nothingspecialforu/EvtPsst: EvtPsst
EvtPsst. Contribute to nothingspecialforu/EvtPsst development by creating an account on GitHub.
github.com
October 26, 2023 at 2:53 AM
Pull conflict into shared space (#openprocess #4opens #trustflows)

Poison thrives in private channels, so you gently but consistently move things:

from DMs → into group threads
from whispers → into meetings
from vague → into specific

This doesn’t eliminate conflict, it grounds it. Sunlight […]
Original post on mastodon.social
mastodon.social
April 22, 2026 at 7:44 AM
Breaking Windows Defenses: New KslDsys BYOVD Attack Extracts LSASS Credentials With Zero API Calls + Video

Introduction The Local Security Authority Subsystem Service (LSASS) remains the crown jewel of Windows credential storage, traditionally protected by API monitoring that flags suspicious…
Breaking Windows Defenses: New KslDsys BYOVD Attack Extracts LSASS Credentials With Zero API Calls + Video
Introduction The Local Security Authority Subsystem Service (LSASS) remains the crown jewel of Windows credential storage, traditionally protected by API monitoring that flags suspicious access attempts. A newly ported Bring Your Own Vulnerable Driver (BYOVD) technique leverages a Microsoft-signed kernel driver to read LSASS memory through physical memory access—completely bypassing OpenProcess, ReadProcessMemory, and every auditable API call that security tools typically monitor.
undercodetesting.com
April 2, 2026 at 10:28 AM
This blogpost demonstrates how an attacker could tamper with the EventLog Process without an OpenProcess call to the EventLog process itself.

nothingspecialforu.github.io/EvtPsstBlog/
testert01 Blog
nothingspecialforu.github.io
October 31, 2023 at 8:37 PM
Havoc C2 BOF port of the KslD.sys BYOVD technique. Credential extraction from lsass via physical memory, no OpenProcess, no auditable API calls
https://t.co/r6keieUuf1

— from @ipurple (https://x.com/ipurple/status/2073736025071865918)
GitHub - Muz1K1zuM/kslkatz_bof: Havoc C2 BOF port of the KslD.sys BYOVD technique. Credential...
t.co
July 5, 2026 at 11:56 AM