Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+1 −1
Q&A What are the concrete security risks of forcibly terminating a process?

That sounds like bad design on the developers' part. There are many unavoidable ways a program may be terminated unexpectedly: Killed by an OOM killer Program crash Terminated by virus OS cra...

posted 8mo ago by matthewsnyder‭

Answer
#1: Initial revision by user avatar matthewsnyder‭ · 2023-09-13T16:51:29Z (8 months ago)
That sounds like bad design on the developers' part. There are many unavoidable ways a program may be terminated unexpectedly:

* Killed by an OOM killer
* Program crash
* Terminated by virus
* OS crash
* Computer lost power

If these really do introduce a security risk, then it's very bad news for the user because there's not much you can do to prevent them.

Generally, perhaps the program has some clean up to do. For example, may be an encrypted secret gets decrypted and saved on disk when it starts, and the exit procedure deletes the decrypted version. If you forcibly terminate, the deletion will never happen. This is of course an insane design, but that hasn't stopped Gnome in the past...