|
Steve, the issue is that with Windows Messenger working as designed, with the original default settings, anyone anywhere could pop a message up onto your screen. Your machine was just their personal billboard and you couldn't stop it until you could find the settings. The settings to stop it were obfuscated. There was no damage inflicted except that a dozen or more pop ups per minute made your machine unusable on the internet. The point is that there was no patch for this flaw because it was designed to work that way. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@xxxxxxxxxxxx --------------------------------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: Friday, September 12, 2003 09:54:55 To: Midrange Systems Technical Discussion Subject: RE: New M$ vulnerability patch for Windows -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Adam Lang Sent: Friday, September 12, 2003 9:42 AM To: Midrange Systems Technical Discussion Subject: Re: New M$ vulnerability patch for Windows >Here is a good example. the Windows Messenger Service. People can >interface it over the internet and display pop ups on your computer. It >isn't a "bug" so there is no patch to prevent it. You actually need to >either uninstall windows messenger or have a firewall to block the ports. other than a buffer overrun flaw in Windows Messenger Service, why would a user need to block access to it? If the protocol server, even FTP, does what it is designed to do, why does access to it have to be completely blocked? I just question if we are all overreacting because we are not aware of the details of how things work. -Steve _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. .
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.