- #Zonealarm free firewall 2018 full tutorial step by step Patch#
- #Zonealarm free firewall 2018 full tutorial step by step series#
Once you make such comments it does leave a reader to consider your point biased no matter what your platform of choice is. This site has turned into a poo flinging contest to see who is better at discrediting another poster. The term “zealot” is getting thrown around to much on forums in an attempt to antagonize other platform users. Microsoft has provided information on disabling the DCOM service here:įirst lets get this straight.
Is protecting the few (who apparently don’t read security mailing lists regularly enough to keep abreast of what services are being exploited) really worth the potential of widespread exploitation of vulnerabilities? Providing more information to the public on a particular vulnerability only eases the job of those exploiting a given vulnerability. The bulletin was originally disclosed in July of last year:įurther proof that Microsoft’s disclosures (regardless of the availability of the patch) as a general trend preceed widespread exploitation. dont give me that security through nondisclosure crap, many boxes could have been secured or at least firewalled off if the knowledge had surfaced public prior to ms patching it. this was over 9 months prior to microsoft releasing a patch. I know a few in RL and watched as they were showing me owning a remote box through this hole.
#Zonealarm free firewall 2018 full tutorial step by step Patch#
Long before blaster, long before microsoft released a patch for blaster, the rpc hole was known to script kiddies. Perhaps you’d have answered that if you’d have tried… reading harder? “Are the advantages of disclosure really worth sacrificing the potential time which could be used for developing and testing patches?” The question asked in my post was the following: The bottom paragraph was a pre-emptive response to those who prefer to spread FUD about Microsoft and unconditionally tout the virtues of (while providing an entirely one-sided and ultimately misleading view of) open source. The fact that you can point to one problematic set of patches in the many years in which open source has been in use does not your point prove.Ĭlearly you missed my point and focused merely on the bottom paragraph, simply because I used the word “zealot”.
#Zonealarm free firewall 2018 full tutorial step by step series#
Yes, however as has been reiterated by Darius and others throughout this thread, why disclose knowledge of a vulnerability which isn’t being exploited in the wild before a patch is available? This was the case exhibited by this series of vulnerabilities, and the case I was arguing. One other thing, the reasons why security through obscurity don’t work are well documented. Better yet, before releasing an OS certified as “complete/final” Microsoft should make sure there are no bugs or holes like the thousands that were present when XP was first released to the public. Microsoft needs to get their act together and provide reasonable fixes to security issues, bugs, etc. Making it seem tech support and security issues are not dealt with properly even though some popular Linux commercial distros such as the ones mentioned are well known for their security and support.
What’s suprising is Microsoft continually attempts to put down the Open Source community and Linux in general. Leaving their systems insecure for months while keeping it secret that there are gaping holes in IE, etc. I’m not trying to start a flame war but you have to wonder why companies such as Red Hat and Novel (SuSE) can release security patches with in hours and not weeks like Microsoft? Time and time again Microsoft has dissappointed not only businesses but home consumers. They take their time releasing security patches and who ends up suffering? Not Microsoft but instead the end user suffers because of their lazy assed attitude.
0 kommentar(er)
