Then get LittleSnitch, it's asks for permission whenever there's port access. "Such and Such is receiving data on port 4242, allow or deny?"
Does it also do this on privileged ports? If so, that'd be annoying for a web server.
Then get LittleSnitch, it's asks for permission whenever there's port access. "Such and Such is receiving data on port 4242, allow or deny?"
It's configurable, according to your needs and preferences.Does it also do this on privileged ports? If so, that'd be annoying for a web server.Of course, for desktop use, that's cool.
It's configurable, according to your needs and preferences.
http://www.obdev.at/products/littlesnitch/index.html
Little Snitch only handles outgoing network connections on all network interfaces (AirPort, PPP, network cards, etc.). It intercepts and defers an application's network access until you decide to allow or deny the request, or it handles the request automatically based on an already defined rule.
Little Snitch does not intercept incoming connections. They can be blocked with the built-in firewall of Mac OS X. This firewall can be configured in System Preferences > Security > Firewall (or in System Preferences > Sharing > Firewall on Max OS X 10.4).
You read the messages before referring to other posts. I told before I read some of the open topics.
I don't care to spread windows viruses around; I would feel irresponsible and generally have a low opinion of those who do.
ClamXav is free and has detected many windows viruses I would have otherwise passed along to others.
It does not have to be a virus. What about a remote attacker? Since OS X uses BSD's ftpd and Apache's httpd, there exists a possibility of unauthorized remote access. There are plenty of exploits found in Apache and ftpd, and this could allow root access to the wrong person.
Wouldn't that be considered Hacking, not a virus?
Antivirus protection can't prevent hacking as fas as I know.
MacOS X has been around since 2001. That's nearly eight years and counting without realizing the remote attacker scenario. When do we stop waiting?... What about a remote attacker? Since OS X uses BSD's ftpd and Apache's httpd, there exists a possibility of unauthorized remote access. ...
Are you really?Sorry, ...
MacOS X has been around since 2001. That's nearly eight years and counting without realizing the remote attacker scenario. When do we stop waiting?
Are you really?![]()
I take it that you are laboring under the misconception that security is stagnant on UNIX-based systems. If so, then you are mistaken....
Either way, are you going to sit there and tell me that Unix systems are never (and never have been) compromised? Come on, OS X is based on a Unix-type system. It's not invincible. If you believe so, that's fine, but you're living a fantasy.
I take it that you are laboring under the misconception that security is stagnant on UNIX-based systems. If so, then you are mistaken.
The topic is worthy of a fairly long research (or state of the art) paper, and a thread in a discussion is not enough (unless it is a very long one and someone organizes it like a ... paper!)
When all's said and done, question is, "have we helped the original poster who needed help?"
![]()
Let me ask this though. What if you have Apache running or even FTP, and someone exploits those? They can gain root access that way without needing your password or anyone to type one. I've never heard anyone doing that on OS X, probably because most people have it off.
This subject like others have stated gets dragged up week after week & until theirs 100% proof that a virus is present in the wild i like the majority of Mac users think it is totally pointless to have a AV installed, you think differently thats your choice