-Lock down the registry with permissions
-Change hard drive permissions to authenticated users instead of everyone
-Do NOT use administrator all the time
-Use the run as service to run as administrator when needed
-Use Steve Gibson's Socket Lock to prevent the berkely sockets form being abused
-Subscribe to Microsoft's Security Bulletins
-Turn off all unnecessary services
-Use Group Policy editor to clear swap file on shut down and do not enumerate SAM for anonymous users
-Enable Full security auditting
-Disable NetBIOS of TCP/IP (DNS will handle names for you)
-Unbind file and printer sharing if it's enabled
-Disable IP forwarding (Let a physical router handle the routing)
-Use double NIC cards if the server is also on a LAN
-Use N-tiering if the server is on a LAN
-Change the name of the Administrator account
-Turn of the DCOM interface so it's not listening on TCP port 135
-If you plan on using Internet Explorer, set security settings to maximum if possible
-Use a restricted user account (NOT power user)
-Use a packet sniffer and monitor to check performance and traffic
-Disable ActiveX controls and plugins if possible
-Lock the server up and administer it remotely if possible
-Set password complexity requirements and force password changes and require a different password for at least the next two password changes
-Close any mail relays you might have open
-Avoid using programs that use mail relays
-Have a regular backup plan
-Have a disaster recovery plan
-If the server cannot be secured, put a camera in the room if possible
-Clear the last user name of the last logged in user (Group policy editor)
-Use fault tolerant equipment
-Make sure the guest account is disable (disabled by default)
-Develop a patching schedule
-Enable the recovery console option for emergency recovery [cd rom drive letter]:\i386\winnt32/cmdcons
-Make sure that unused ports on your router are closed
-Implement ACLs if applicable
NT 4.0 can be a bit of a bear when it comes to drivers. You might need to check the board number on your card as not all drivers work on all board numbers. Ie, my es1370 has board number CT4700. But there are drivers that won't work with that board. The chipset is still es1370 and the card is still a SB PCI 128, but because of board differences, only certain drivers work.
Has sabotage been ruled out? There's nothing worse than your own people turning their backs on you. For all we know, someone who worked on the project might've been bribed into sabotaging the server.
Mail Washer lets you preview your mail BEFORE you download it. And it automatically ignores images and shows paths of links. It also has heuristics to detect viruses.
A memory dump is a blue screen. And most memory dumps in an NT/NT based environment are due to hardware or driver problems. Programs run at ring 3 in their own memory spaces.
Windows 9x blue screens could also be caused by hardware or drivers but were usually due to bad memory management, direct access to hardware and everything running at ring 0.
It wouldn't be the only layer of security if people didn't run as administrator all the time. And Microsoft totally wastes the benefits of NTFS in XP home because administrator is the default user! There's also EFS which seems to go unnoticed in the Windows world.
The Federal Government is probably Microsoft's biggest customer. As if the anti-trust case wasn't warped enough, Microsoft aiding SCO and SCO going after the Feds is even more twisted. MS and the government have one serious dysfunctional marriage. Of course, this could flare up the anti-trust meter if SCO actually wins and the government has to switch to um ahem Microsoft.
The FTC will surely scrutinize Microsoft over this one. You can't just buy a multi-billion dollar company without the government knowing about it. I have a feeling that the FTC will make things difficult for Microsoft. This won't be a simple hand shake, done deal kind of acquisition.
The downfall of the Internet will occur only in an apocolyptic scenerio such as a nuclear holocaust or an asteroid striking Earth. And groups like the RIAA and MPAA are like the government. They refuse to admit one thing: They are ultimately powerless to stop what goes over the wires. Abolition of anything can easily create a counteracting effect. As far as viruses, worms and spam are concerned, IPv4 leaves the door open to header forging and email address spoofing. IPv6 is supposed to stop that. But last the I checked, its code wasn't thoroughly tested and it could take years to implement.
High speed connections do make you more vulnerable to infections IF you don't secure your system. Simply hooking into the Internet without protection obviously can lead to disaster. But Windows XP's firewalling is a sign of things to come. Firewalls and virus scanners will be so common that for anyone not to have them would be a shock.
When the Viking satellite took a picture of the famous "Face On Mars," scientists figured it was just a rock formation. But NASA revealed pictures of it to the public in an attempt to spark in interest in the space program. And the response was incredible. Books, conspiracy theories and other things were devoted to it. The people wanted the truth about the Face on Mars and NASA delivered it. The so-called Face On Mars was really just a Mesa.
I'm sure that many people will think that the UFO really is extraterrestial in nature, even though it most likely is not. But if it gets the public more interested in Mars, it might be worth some publicity.
There's always the possibility of drama in the work place and feelings can get hurt. It's not impossible for this drama to leak into your personal life, especially if some of the same things are happening in both places.
As a result, you will be forced to deal with situations where you may end up hurting feelings or get hurt feelings. But the complexity of family involvement can result in business being taken in a very personal way. The concept of,"It's nothing personal; just business" could easily be defeated in this kind of situation simply due to you having multiple relationships with the people you're working with. One relationship is family and/or lover. And the other is coworker and/or employee. This juggling of relationships might be aided with a bit of diplomacy. You might want to allow your intellect to override your emotions as well to maintain stability with the relationships. But be careful as intellect can be cold and insensative.
The quote "it's all in the family" could be silently echoed by employees who aren't related to you. This could result in potential problems later down the road.
There's also the issue of a family crisis and how it could be handled without hendering business.
I used to have a cgi script that would send IE users to a spoofed IE error on my site. I think I was losing too much traffic for using it though http://www.silentchaos.com/ie_error.html
I never said I liked Outlook or MS products for that matter. Like I said, there's too much software being handled by one company and that leaves room for alot of gaps. And when Microsoft decided to take security seriously, they were already too late. They let things go for so long that it could take them years to get everything locked down. I'm afraid alot of that is going to be answered with upgrades which could create more holes than they're supposed to fix.
It shows that Microsoft is taking things more seriously. And maybe next time, maybe they'll catch more potential problems before they're discovered. If MS were to actually break itself up into smaller companies, it wouldn't have to worry about keep tabs on so much stuff. I know it won't do that, but I think it would be alot more efficient. When it comes to patches, Microsoft is like a giant. Someone hits it on the leg, so it has to look down and find the source of the attack and fix it. But at the same time, someone could be attacking it on the back and neck.
The PM of Canada had better have something to back that up with. That's a very serious allegation to make, especially against a multinational corporation or even its contractors. Will the FTC play a part in the investigation?
Microsoft spends entirely too much time trying to make the desktop look pretty and not enough time trying to make things more stable and more secure.
The ever-growing resource usage in Windows is also linked to a big security affliction of the OS. Integrating apps creates some serious problems. A) It uses signficantly more resources; B) It puts the entire OS's security at risk; C) It leaves the user with no option to uninstall them and D) It makes securing the OS more difficult and problematic.
And to top things off, web integration is found throughout the OS. Web integration causes drag and latency because IE has to render the content of the windows. Personally, I find it stupid and a waste of resources. And other companies including Intuit, Symantec, McAffee and others have followed suit with their programs' GUIs. And now Microsoft is doing something with XAML and XML from what I understand. And this has been incorporated into the GUI as well.
Microsoft has a history of system requirements increasing as newer Windows and NT-based versions have been released. Not suprisingly, the GUI gets clunkier and has more clutter with each new release.
Did you see ATI or nVidia providing drivers for Linux years ago? Linux's acceptance has earned it the recognition it needs from big time hardware manufacturers. Sure the drivers might not be open source, but at least they exist. And companies like IBM embracing Linux could act as a catalyst for future hardware support.
Slashdot Mirror
Microsoft was simply the main promoter...
-Lock down the registry with permissions -Change hard drive permissions to authenticated users instead of everyone -Do NOT use administrator all the time -Use the run as service to run as administrator when needed -Use Steve Gibson's Socket Lock to prevent the berkely sockets form being abused -Subscribe to Microsoft's Security Bulletins -Turn off all unnecessary services -Use Group Policy editor to clear swap file on shut down and do not enumerate SAM for anonymous users -Enable Full security auditting -Disable NetBIOS of TCP/IP (DNS will handle names for you) -Unbind file and printer sharing if it's enabled -Disable IP forwarding (Let a physical router handle the routing) -Use double NIC cards if the server is also on a LAN -Use N-tiering if the server is on a LAN -Change the name of the Administrator account -Turn of the DCOM interface so it's not listening on TCP port 135 -If you plan on using Internet Explorer, set security settings to maximum if possible -Use a restricted user account (NOT power user) -Use a packet sniffer and monitor to check performance and traffic -Disable ActiveX controls and plugins if possible -Lock the server up and administer it remotely if possible -Set password complexity requirements and force password changes and require a different password for at least the next two password changes -Close any mail relays you might have open -Avoid using programs that use mail relays -Have a regular backup plan -Have a disaster recovery plan -If the server cannot be secured, put a camera in the room if possible -Clear the last user name of the last logged in user (Group policy editor) -Use fault tolerant equipment -Make sure the guest account is disable (disabled by default) -Develop a patching schedule -Enable the recovery console option for emergency recovery [cd rom drive letter]:\i386\winnt32 /cmdcons
-Make sure that unused ports on your router are closed
-Implement ACLs if applicable
NT 4.0 can be a bit of a bear when it comes to drivers. You might need to check the board number on your card as not all drivers work on all board numbers. Ie, my es1370 has board number CT4700. But there are drivers that won't work with that board. The chipset is still es1370 and the card is still a SB PCI 128, but because of board differences, only certain drivers work.
Has sabotage been ruled out? There's nothing worse than your own people turning their backs on you. For all we know, someone who worked on the project might've been bribed into sabotaging the server.
Mail Washer lets you preview your mail BEFORE you download it. And it automatically ignores images and shows paths of links. It also has heuristics to detect viruses.
A memory dump is a blue screen. And most memory dumps in an NT/NT based environment are due to hardware or driver problems. Programs run at ring 3 in their own memory spaces. Windows 9x blue screens could also be caused by hardware or drivers but were usually due to bad memory management, direct access to hardware and everything running at ring 0.
It wouldn't be the only layer of security if people didn't run as administrator all the time. And Microsoft totally wastes the benefits of NTFS in XP home because administrator is the default user! There's also EFS which seems to go unnoticed in the Windows world.
The Federal Government is probably Microsoft's biggest customer. As if the anti-trust case wasn't warped enough, Microsoft aiding SCO and SCO going after the Feds is even more twisted. MS and the government have one serious dysfunctional marriage. Of course, this could flare up the anti-trust meter if SCO actually wins and the government has to switch to um ahem Microsoft.
404 not found.
Um. Okay. That's a figure of speech I'm not quite familiar with.
This was proven almost 3 years ago. And the terrain on Mars isn't exactly flat, either.
The FTC will surely scrutinize Microsoft over this one. You can't just buy a multi-billion dollar company without the government knowing about it. I have a feeling that the FTC will make things difficult for Microsoft. This won't be a simple hand shake, done deal kind of acquisition.
And it doesn't matter how screwed up the system is. You're not going to be praised. You're going to be punished.
The downfall of the Internet will occur only in an apocolyptic scenerio such as a nuclear holocaust or an asteroid striking Earth. And groups like the RIAA and MPAA are like the government. They refuse to admit one thing: They are ultimately powerless to stop what goes over the wires. Abolition of anything can easily create a counteracting effect. As far as viruses, worms and spam are concerned, IPv4 leaves the door open to header forging and email address spoofing. IPv6 is supposed to stop that. But last the I checked, its code wasn't thoroughly tested and it could take years to implement. High speed connections do make you more vulnerable to infections IF you don't secure your system. Simply hooking into the Internet without protection obviously can lead to disaster. But Windows XP's firewalling is a sign of things to come. Firewalls and virus scanners will be so common that for anyone not to have them would be a shock.
Sorry for the double post Was really just a mesa
When the Viking satellite took a picture of the famous "Face On Mars," scientists figured it was just a rock formation. But NASA revealed pictures of it to the public in an attempt to spark in interest in the space program. And the response was incredible. Books, conspiracy theories and other things were devoted to it. The people wanted the truth about the Face on Mars and NASA delivered it. The so-called Face On Mars was really just a Mesa. I'm sure that many people will think that the UFO really is extraterrestial in nature, even though it most likely is not. But if it gets the public more interested in Mars, it might be worth some publicity.
There's always the possibility of drama in the work place and feelings can get hurt. It's not impossible for this drama to leak into your personal life, especially if some of the same things are happening in both places. As a result, you will be forced to deal with situations where you may end up hurting feelings or get hurt feelings. But the complexity of family involvement can result in business being taken in a very personal way. The concept of,"It's nothing personal; just business" could easily be defeated in this kind of situation simply due to you having multiple relationships with the people you're working with. One relationship is family and/or lover. And the other is coworker and/or employee. This juggling of relationships might be aided with a bit of diplomacy. You might want to allow your intellect to override your emotions as well to maintain stability with the relationships. But be careful as intellect can be cold and insensative. The quote "it's all in the family" could be silently echoed by employees who aren't related to you. This could result in potential problems later down the road. There's also the issue of a family crisis and how it could be handled without hendering business.
I used to have a cgi script that would send IE users to a spoofed IE error on my site. I think I was losing too much traffic for using it though http://www.silentchaos.com/ie_error.html
I never said I liked Outlook or MS products for that matter. Like I said, there's too much software being handled by one company and that leaves room for alot of gaps. And when Microsoft decided to take security seriously, they were already too late. They let things go for so long that it could take them years to get everything locked down. I'm afraid alot of that is going to be answered with upgrades which could create more holes than they're supposed to fix.
It shows that Microsoft is taking things more seriously. And maybe next time, maybe they'll catch more potential problems before they're discovered. If MS were to actually break itself up into smaller companies, it wouldn't have to worry about keep tabs on so much stuff. I know it won't do that, but I think it would be alot more efficient. When it comes to patches, Microsoft is like a giant. Someone hits it on the leg, so it has to look down and find the source of the attack and fix it. But at the same time, someone could be attacking it on the back and neck.
Just because the subsidary was Canadian doesn't mean that HQ couldn't have had something to do with it.
But HP is an American company.
The PM of Canada had better have something to back that up with. That's a very serious allegation to make, especially against a multinational corporation or even its contractors. Will the FTC play a part in the investigation?
Microsoft spends entirely too much time trying to make the desktop look pretty and not enough time trying to make things more stable and more secure. The ever-growing resource usage in Windows is also linked to a big security affliction of the OS. Integrating apps creates some serious problems. A) It uses signficantly more resources; B) It puts the entire OS's security at risk; C) It leaves the user with no option to uninstall them and D) It makes securing the OS more difficult and problematic. And to top things off, web integration is found throughout the OS. Web integration causes drag and latency because IE has to render the content of the windows. Personally, I find it stupid and a waste of resources. And other companies including Intuit, Symantec, McAffee and others have followed suit with their programs' GUIs. And now Microsoft is doing something with XAML and XML from what I understand. And this has been incorporated into the GUI as well. Microsoft has a history of system requirements increasing as newer Windows and NT-based versions have been released. Not suprisingly, the GUI gets clunkier and has more clutter with each new release.
Did you see ATI or nVidia providing drivers for Linux years ago? Linux's acceptance has earned it the recognition it needs from big time hardware manufacturers. Sure the drivers might not be open source, but at least they exist. And companies like IBM embracing Linux could act as a catalyst for future hardware support.