Messages - Tuxman [ switch to compact view ]

Pages: prev1 ... 440 441 442 443 444 [445] 446 447 448 449 450 ... 489next
2221
General Software Discussion / Re: Stop Windows from calling home
« on: January 05, 2010, 11:26 AM »
Did I say that?
I thought your second sentence referred to your first one? (I quoted both.)

2222
General Software Discussion / Re: Stop Windows from calling home
« on: January 05, 2010, 11:08 AM »
Also, saying that running a software firewall is nowhere near as good as a hardware firewall is laughable due to the fact that hardware firewalls are SOFTWARE based running embedded on a set of dedicated hardware. In most cases, systems running personal firewalls are faster than the hardware included in the average home user firewall/router.
So being fast is more important to you than being secure? You can't count that.
BTW, the point here is "dedicated hardware", separated from a probably contaminated system where you should not trust any software.

2223
Mini-Reviews by Members / Re: XYplorer File Manager
« on: January 05, 2010, 11:00 AM »
Total Commander is like foobar2000: You can spend hours customizing it, still it looks like something ugly that has been customized.

2224
General Software Discussion / Re: Stop Windows from calling home
« on: January 04, 2010, 10:43 PM »
Nice move ignoring the iptables link, which sounds like it could potentially be a lot worse than the cry-wolf XP bug.
Not ignoring it, but keeping the discussion on-topic.

too bad default user wasn't made non-admin alread in Win2k
AFAIK he still is not?

it shows that MS certainly aren't ignoring the problem any longer - and you get a lot of stuff with NT now that you don't get with linux unless manually choosing a kernel with SELinux patches.
Which is, at least, a giant step into the right direction after rolling backwards for years. Let's hope they'll stick with it.

Well, duh, isn't this what I've been saying all along?
Not quite, as we were still on "Personal Firewalls".  :P

Except for the "doesn't need paranoia" part... a packet filter isn't paranoia, it's an additional level of security.
... or maybe also insecurity. See, most people I know mix up "consider your system's security" with "install a security suite and everything is fine", and then they'll wonder why their system is fucked up.
Maybe I just know the wrong people.

 ;D

Hopefully it'll never be needed on neither hosts nor servers, but if you have a breach it can save your ass
So far I (personally) never had a problem that could have easier been fixed by installing a packet filter. Lucky me.

If you don't need something complex, why waste time developing it?
cmd.exe is complex but not mighty. "Scriptable" but not "flexible". For my own workstation(s) it is more than enough, but fiddling with config files without grep or something sounds hard.
(There is grep [with ls. love that.] for Windows, but I actually doubt that it is installed on common Windows servers.)

Apparently enough users wanted a more powerful shell, and MS responded with PowerShell. Haven't used it myself so I can't comment on it's quality.
To me, the PowerShell more looks like some .net command console, not a valid MinGW/Cygwin replacement. I really wish MS would consider making Windows POSIX-compatible by default for everyone, not only the high-class editions... would make life a lot easier.

...see a slight difference between those two statements?
Yep, I missed the "IMO" in my original posting. The statement is, basically, the same, but the second one seems to be more clearly or something. Sorry for fuzzy phrasing.  :D

2225
General Software Discussion / Re: Stop Windows from calling home
« on: January 04, 2010, 09:53 PM »
You've come up with one thing so far, which is more than three years old, limited to XP, and requires the ICS service to be on (which it isn't by default, as far as a lazy google says).
http://en.wiktionary.org/wiki/potential

And it's not like *u*x daemons haven't had their fair share of exploits during the years. Apache, BIND, wu-ftpd, whatnot. Also, both OS X and Linux kernels have had very interesting local privilege escalation during the recent months, some of which are present in several years worth of kernels... could that with a remote exploit in a single third-party service (or even something as a lowly PHP bug) and boom, you've got root. Non-Windows doesn't automagically equate secure - no matter what you run, you need competent server admins who keep their eyes open.
Some are "better" however.
Of course you can configure *ix to be insecure, of course you can even have a secure Windows XP server or something. The software running on the server is the bottleneck - and now we're on topic again. The one who installs and maintains the software is responsible for it to work properly. If he fails, not even a firewall of any kind can help him. If he succeeds, he doesn't need paranoia. There might be something in between. Does it really matter?

So what, really? Windows isn't unix, things work differently.
Now this is not a reason for having to use a rather mediocre shell, is it?

By this, you're saying that packet filters which require administrative privileges to configure are useless
... to me. Maybe there are some rare circumstances that might be easier to handle with something like a "packet filter". Using such does not necessarily make your system more secure, though.

Pages: prev1 ... 440 441 442 443 444 [445] 446 447 448 449 450 ... 489next
Go to full version