Husse wrote:Hm - a little war going on?
Perhaps this could be boiled down to
D1Wayne claiming that nasty things could happen if you work on it (not at the beginning though)
marcus0263 and scorp123 stating that you really have to work so hard to achieve the bad things that they really don't happen
It proves a theory ... but putting a this into practice & reality is a different thing altogether. As I wrote in my earlier posting: Yes, there can be Linux viruses. But are they in the wild? NO. There once was some stupid worm that would attack PHP pages, but that hardly doesn't count as "virus" as this thing no matter what it did could never ever compromise the entire OS.D1Wayne wrote: proof of concept, proves they vulnerability,
Totally harmless compared to what a real hacker can do to your network if he finds a way in ...D1Wayne wrote: the bug mentioned earler, is proof, that 1 digruntle person on adevelopemnt team could easily sabotage a project.
Or it rather illustrates that certain companies better check their procedures again and how the hell infected Windows machines were allowed to access a critical production areaD1Wayne wrote: the link was simply to illustrate how easy it would be to slip in malicious or faulty code.
Bingo!! But what most (Ex- ?) Windows people don't get is that *nix has it's fair share of vulnerabilities ... of course it has, it would be foolish to claim the opposite. But those vulnerabilities just ain't virusesmarcus0263 wrote: As for the argument about "*nix's just not being popular", well what do the big banks, government defense systems etc. critical and financial systems run?
scorp123 wrote:Bingo!! But what most (Ex- ?) Windows people don't get is that *nix has it's fair share of vulnerabilities ... of course it has, it would be foolish to claim the opposite. But those vulnerabilities just ain't virusesmarcus0263 wrote: As for the argument about "*nix's just not being popular", well what do the big banks, government defense systems etc. critical and financial systems run?
Let's talk about foolish UNIX admins not placing their servers behind properly configured firewalls, let's talk about stupid wannabe admins never taking care of patching their systems, let's talk about running some wacky and ugly hacks on your web server that a third-party company developed for your company -- your boss insists that this piece of cow dung has to be installed on your server despite the fact that this thing is opening too many TCP ports and yet nobody could so far really tell you why precisely those ports have to be open, let's talk about buffer overflows, stupid admins running root shells in "screen" and leaving those shells open for months ... let's talk about stupid users running unknown software that does funny things such as firewall hole punching (Hamachi anyone? Or Skype? Very Happy ) ... Let's talk about reverse SSH tunnels that could be easily used as backdoors, let's discuss manipulated daemons that do a lot more than what they're supposed to do, let's touch the topic of angry ex-employees who know too much about your corporate network's topology and all the daemons that run on each of your servers and who got too many unsettled scores to settle .... Let's talk about all this and the tune suddenly changes: *This* is the stuff UNIX people like marcus or me are afraid of ... if there is any such thing, then it's stuff like *THIS* .... But not "viruses"
Sanchopinky wrote: "Detected hit from 192.168.1.42"
Is linux still safe from that?
Users browsing this forum: Bing [Bot], DTJ and 34 guests