← Back to context Comment by QGQBGdeZREunxLe 4 days ago https://news.ycombinator.com/item?id=50108872 4 comments QGQBGdeZREunxLe Reply IncreasePosts 4 days ago Unless there's a bug where jellyfin or plex decides to execute a random exe it tries to index, exploitation seems unlikely. dawnerd 4 days ago And even then you should be running in a container at least. dawnerd 4 days ago That’s been a thing for years. No one is actually running the exes, or at least they shouldn’t be. Its such a simple thing to prevent too… russelg 4 days ago Simply put, skill issue. Never ran into anything like this when using reputable private trackers and indexers.
IncreasePosts 4 days ago Unless there's a bug where jellyfin or plex decides to execute a random exe it tries to index, exploitation seems unlikely. dawnerd 4 days ago And even then you should be running in a container at least.
dawnerd 4 days ago That’s been a thing for years. No one is actually running the exes, or at least they shouldn’t be. Its such a simple thing to prevent too…
russelg 4 days ago Simply put, skill issue. Never ran into anything like this when using reputable private trackers and indexers.
Unless there's a bug where jellyfin or plex decides to execute a random exe it tries to index, exploitation seems unlikely.
And even then you should be running in a container at least.
That’s been a thing for years. No one is actually running the exes, or at least they shouldn’t be. Its such a simple thing to prevent too…
Simply put, skill issue. Never ran into anything like this when using reputable private trackers and indexers.