Edit - Information Security Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

In some ways this model could actually be more secure against PID reuse than pure sequential, because it causes PID reuse to be extreamly common, and quickly grabbed, this has two effects 1) It means any software that incorrectly depends on PIDs not beign reused is more likely to fail observably and be patched, 2) The OS is likely to assign the PID to something other than what the attack wants before the attacker does, making attacks harder to pull off.

user1937198
– user1937198

2025-06-01 01:24:49 +00:00
Commented Jun 1, 2025 at 1:24

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »