If that admin has the ability to replace the kernel (maliciously or otherwise), the whole system can be compromised even if the kernel cannot be replaced.
We're not talking about server apps like sshd.. Obviously that would listen on 22. We're talking about random apps that call listen without your knowledge.
BTW that is absolutely false. While an already open (and active) point to point connection is relatively hard to compromise, an application that is listen()ing on a port can be compelled to accept data from any source, at will, and repeatedly.
This makes buffer overflow (or other remote exploits) attacks trivial to both test and execute successfully.
Granted, if it is a transient listen(), netstat -l won't catch it (e.g. something is required to trigger the listen), but long lived, persistent listen()s will show up.
No. 20 years ago, only 1 in 5 people were clueless about technical topics, so by and large, active posters in DIY tech forums knew what they were talking about.
And if they had problems and questions, they knew what information to provide in their posts.
Now, less than 1 in 5 participants have a clue.
4 out of 5 have no idea how to post a technical question, and no idea how to give people who might be able to help the context they need to give useful advice.
Bottom line: People on the 'net are universally more incompetent, which causes the few smart people left to get pissy and short tempered due them constantly being inundated by the same stupid questions posited by people who have no interest (let alone ability) to provide the needed context to facilitate a useful answer.
The delicate flowers demanding moderation only make things works, because it drives off anybody with a clue, so you're left with a forum filled with morons and griefers.
Slashdot Mirror
If that admin has the ability to replace the kernel (maliciously or otherwise), the whole system can be compromised even if the kernel cannot be replaced.
If your machine can be exploited to the point where the kernel can be replaced, preventing the kernel from being replaced is not going to help you.
Why do you use it? To what end?
I see absolutely no benefit to UEFI. What does it have to do at all with "business integration"?
listen() is fundamentally more dangerous than connect().
You use connect(), not listen()/accept()
Did you actually read my post?
I would not hire you for any networking job.
We're not talking about server apps like sshd.. Obviously that would listen on 22. We're talking about random apps that call listen without your knowledge.
There is a difference between calling listen() and connect().
BTW that is absolutely false. While an already open (and active) point to point connection is relatively hard to compromise, an application that is listen()ing on a port can be compelled to accept data from any source, at will, and repeatedly.
This makes buffer overflow (or other remote exploits) attacks trivial to both test and execute successfully.
Once more, for what reason should an app call listen()? Be specific.
Why should an app call listen()? For what operation?
Can you suggest a reason why a smartphone application should listen on a port without you knowing it?
This is exactly what netstat -l is good for.
https://play.google.com/store/...
Granted, if it is a transient listen(), netstat -l won't catch it (e.g. something is required to trigger the listen), but long lived, persistent listen()s will show up.
Just go to the source.
newatlas sucks - if you run an adblocker, it won't let you access any of their stories.
http://www.darpa.mil/news-even...
currently 40,000 years ago.
Only a complete moron would claim Gall-Peters has less distortion.
It sucks.
And no mention of Mariner 8/9?
I don't know where /. gets their editors, but they're definitely getting dumber and dumber as the years go by.
You guys hire complete morons now, huh?
Also, grats on the clickbait tactic of not telling us what the TLD actually is in the headline.
You suck.
Not the 70's or 80's
Long before that.
https://en.wikipedia.org/wiki/...
https://en.wikipedia.org/wiki/...
So get training. It isn't hard or expensive, and compared to police training, its orders of magnitude more effective.
Police are not a security force. They are not a peace keeping force. Their job is to catch criminals.
Everytown for Gun Safety has no interest whatsoever in "gun safety".
No. 20 years ago, only 1 in 5 people were clueless about technical topics, so by and large, active posters in DIY tech forums knew what they were talking about.
And if they had problems and questions, they knew what information to provide in their posts.
Now, less than 1 in 5 participants have a clue.
4 out of 5 have no idea how to post a technical question, and no idea how to give people who might be able to help the context they need to give useful advice.
Bottom line: People on the 'net are universally more incompetent, which causes the few smart people left to get pissy and short tempered due them constantly being inundated by the same stupid questions posited by people who have no interest (let alone ability) to provide the needed context to facilitate a useful answer.
The delicate flowers demanding moderation only make things works, because it drives off anybody with a clue, so you're left with a forum filled with morons and griefers.