More like any company that outsources and doesn't perform internal quality control of what they are reselling should be made criminal in this instance of reselling to governmental agencies. Buy a Cisco, throw it in a private LAN sandbox, fire up Wireshark. Rinse, lather, repeat. Yawn...
Not sensationalizing are we? I would call wreaking havoc something like when Windows NT 4.0 Service Pack 6 was released. Back in the day our corporate IT didn't deploy service packs in a testbed to ensure things were copacetic. Instead they remotely deployed them to all branch sites. Coming into work the next day and see most servers' TCP/IP stacks were broken as a result made for a busy day managing our site's help desk. Thank God for Service Pack 6a!
I must say that over the years their service pack releases have been much more stable and reliable. And it's like that Mac/PC ad Apple has out. With all of the different hardware and software combinations out there how can any service pack expect to be 100% spot on? Of course it's not Mac's fault...
Yeah, I know about all of the Notes database, forms, etc. Unless they have drastically improved the product since I last admined it those capabilities are far from amazing...
Prior Planning Prevents Piss Poor Performance. This shouldn't be taken as a Micr$oft bash as much as an example of poor planning. After having administered both Lotus Notes and Microsoft Exchange I can say that ditching Notes for Exchange isn't a bad move. But doing so without planning out the migration path is.
Any large scale project should involve a considerable outside contracting firm that would have automated measures in place. You could even plug in a server appliance before your front end Exchange servers that would automatically archive off mail messages being sent to/from the White House staffers.
Another example of US government being inept. Just look to how the US air traffic control centers still operate with equipment that is so outdated that some units are out of commission because they can't order vacuum tubes to service them...
I administered a VINES/Streettalk network back in the mid-1990's. The directory services were indeed NDS before Novell has NDS and AD before Microsoft had AD. I recall that we also communicated with Netware networks too back then. Interoperations were a bit clumsy, but then again back in the day interoperations were always less than ideal. The idea of a single sign-on for Banyan was great. Better than creating a user account on each and every Netware server that a user would attach to back in the days of Netware 3.x.
Reminds me of the old "Saturday Night Live" skit with the gangsters all talking in the bar/restaurant. Wasn't Jon Lovitz some guy named Tommy Two-times? "Gotta pick up the papers. Pick up the papers." Or perhaps it's similar to more profound autism. Rain Man definitely knows it's time for Wapner. Time for Wapner...
They should have had the Thing using one of the prototype iPhones in the first Fantastic Four movie when he was trying to call his girlfriend..."Damn buttons!!!"
A MySQL cookbook reminds me of something I would use in college while learning to live flat broke. Great ways to spice up the old Hamburger Helper, Macaroni and Cheese, etc. You gotta be kidding me. The last time I checked out MySQL was a couple of years ago and then there were so many gotchas I wondered how heavy CRUD production apps could consider such a DB. It's like the MySQL designers figured rather than enforce data integrity and reject invalid transactions they would just kinda guess what you wanted and then put something into the DB on your behalf.
In more detail this feature is something akin to an Object Inspector, something that has been a part of Smalltalk languages for probably 20 years in a GUI form. Funny thing, seeing how Visual Studio 2005 has an Object Browser, which is another throwback to the System/Object Browser feature of various Smalltalks dating back to Smalltalk-80:-)
This seems to be a promising area. The collaborative and distributed basis of the Internet makes good for companies spread out and mobile employees. Has anyone had a time to check out a service called Dabble DB? This is more of a database web app, but really is just a step up from a tweaked-out online spreadsheet. I have a 30 day test drive going using it and so far it seems to be a good resource for sure.
As many have pointed out this has been vaporware thus far, since for about a year and a half there's been no production release. Only news releases.
Another point is that the display looks wasted due to the widget set and also rather restrictive in terms of vertical resolution. It reminds me of the old Handheld Pocket PC's that were out there 5-6 years ago. I tried porting a couple of handheld apps I had running on other platforms and trying to utilize that 200-odd pixel vertical space was a major PITA. They keyboard looks nice, though. But the display. Oy!
...a PC whose only crime is running Windows while connected to the internet...
Actually it's a PC who is running Windows with open Microsoft Networking ports open while connected to the Internet. Big difference. There are many holes over the years that have been exposed with the NT LAN Manager networking stack that have led to these ports being blocked at the firewall as standard practice. Going back to 1997 from what I recall someone could open up an anonymous IPC$ pipe with an NT box and create their own admin account. Things have improved since then, but anyone who has these ports up and listening on the Internet is an idiot. Back in 2000 my company got its first DSL router for Internet acccess. Even that hardware came with an option just called "Microsoft Networking" blocks.
Of course patch your boxes. Keep them updated. This would avoid some local host getting something propagated through your LAN/WAN. But as for the Internet aspect, God knows people should have learned. Ports 137, 138, 139, and 445 should be nowhere to be found from the Internet!
The DNS client vulnerability still puzzles me. From reading the advisory it appears as if the malicious party would have to be on a subnet between the DNS client and the DNS server. If this is the case exploiting this via the Internet might be a bit tough. But internally, a company that uses DNS could get rocked since the DNS clients and servers would likely be on the same LAN/WAN. Just thinking out loud...
The sysadmins are the ones stuck back in the server rooms trying to patch boxes, install new server software, script out client software pushes, working with network backups, etc. I froze my ass of in a 60 degree meat locker for 4 years doing all of this, plus administering the ACD phone system and managing all of my direct reports. It's not like I was hiding back there playing Freecell...
Back about 7 years ago I was IT Manager of a major call center for a wireless provider. The centers were definitely redundant in that there were walls of UPS'es plus even building generator interaces so a truck could pull up outside and plug into the building to provide power as long as there was diesel gasoline available. This does smell fishy...
You sir, as a loyal Anonymous Coward are likely going to remain suspicious of every government's activity. Oh yeah, forgot. You are also going to:
1) Hate Microsoft. 2) Love Linux. 3) Be a Java or C++ code monkey. 4) Live in your parent's basement/grandmother's garage. 5) Not have a steady girlfriend.
Slashdot Mirror
Come to think of it I believe the Mayans did have some building art depicting a huge BSOD with some hexidecimal apocrapha...
As a person supporting said software/hardware, I certainly cannot echo that sentiment :-/
Just goes to show..."Ain't no future in yo frontin'."
So that's why my crappy Linksys wifi access points have to be rebooted every week or so. Damn commies!!!
More like any company that outsources and doesn't perform internal quality control of what they are reselling should be made criminal in this instance of reselling to governmental agencies. Buy a Cisco, throw it in a private LAN sandbox, fire up Wireshark. Rinse, lather, repeat. Yawn...
Not sensationalizing are we? I would call wreaking havoc something like when Windows NT 4.0 Service Pack 6 was released. Back in the day our corporate IT didn't deploy service packs in a testbed to ensure things were copacetic. Instead they remotely deployed them to all branch sites. Coming into work the next day and see most servers' TCP/IP stacks were broken as a result made for a busy day managing our site's help desk. Thank God for Service Pack 6a! I must say that over the years their service pack releases have been much more stable and reliable. And it's like that Mac/PC ad Apple has out. With all of the different hardware and software combinations out there how can any service pack expect to be 100% spot on? Of course it's not Mac's fault...
Yeah, I know about all of the Notes database, forms, etc. Unless they have drastically improved the product since I last admined it those capabilities are far from amazing...
Prior Planning Prevents Piss Poor Performance. This shouldn't be taken as a Micr$oft bash as much as an example of poor planning. After having administered both Lotus Notes and Microsoft Exchange I can say that ditching Notes for Exchange isn't a bad move. But doing so without planning out the migration path is. Any large scale project should involve a considerable outside contracting firm that would have automated measures in place. You could even plug in a server appliance before your front end Exchange servers that would automatically archive off mail messages being sent to/from the White House staffers. Another example of US government being inept. Just look to how the US air traffic control centers still operate with equipment that is so outdated that some units are out of commission because they can't order vacuum tubes to service them...
Stop it already. You're killing me...
Actually 20,000,000 posts. Of course in honor of the fencepost effect I wonder if t he first post was #0?
I administered a VINES/Streettalk network back in the mid-1990's. The directory services were indeed NDS before Novell has NDS and AD before Microsoft had AD. I recall that we also communicated with Netware networks too back then. Interoperations were a bit clumsy, but then again back in the day interoperations were always less than ideal. The idea of a single sign-on for Banyan was great. Better than creating a user account on each and every Netware server that a user would attach to back in the days of Netware 3.x.
Reminds me of the old "Saturday Night Live" skit with the gangsters all talking in the bar/restaurant. Wasn't Jon Lovitz some guy named Tommy Two-times? "Gotta pick up the papers. Pick up the papers." Or perhaps it's similar to more profound autism. Rain Man definitely knows it's time for Wapner. Time for Wapner...
They should have had the Thing using one of the prototype iPhones in the first Fantastic Four movie when he was trying to call his girlfriend..."Damn buttons!!!"
Glad that he overcame that acute health crisis. That likely was just a case of tonsil stones. Roffles!!!
A MySQL cookbook reminds me of something I would use in college while learning to live flat broke. Great ways to spice up the old Hamburger Helper, Macaroni and Cheese, etc. You gotta be kidding me. The last time I checked out MySQL was a couple of years ago and then there were so many gotchas I wondered how heavy CRUD production apps could consider such a DB. It's like the MySQL designers figured rather than enforce data integrity and reject invalid transactions they would just kinda guess what you wanted and then put something into the DB on your behalf.
In more detail this feature is something akin to an Object Inspector, something that has been a part of Smalltalk languages for probably 20 years in a GUI form. Funny thing, seeing how Visual Studio 2005 has an Object Browser, which is another throwback to the System/Object Browser feature of various Smalltalks dating back to Smalltalk-80 :-)
This seems to be a promising area. The collaborative and distributed basis of the Internet makes good for companies spread out and mobile employees. Has anyone had a time to check out a service called Dabble DB? This is more of a database web app, but really is just a step up from a tweaked-out online spreadsheet. I have a 30 day test drive going using it and so far it seems to be a good resource for sure.
Another point is that the display looks wasted due to the widget set and also rather restrictive in terms of vertical resolution. It reminds me of the old Handheld Pocket PC's that were out there 5-6 years ago. I tried porting a couple of handheld apps I had running on other platforms and trying to utilize that 200-odd pixel vertical space was a major PITA. They keyboard looks nice, though. But the display. Oy!
Wish I had mod points. +1 fo shizzle...
Actually it's a PC who is running Windows with open Microsoft Networking ports open while connected to the Internet. Big difference. There are many holes over the years that have been exposed with the NT LAN Manager networking stack that have led to these ports being blocked at the firewall as standard practice. Going back to 1997 from what I recall someone could open up an anonymous IPC$ pipe with an NT box and create their own admin account. Things have improved since then, but anyone who has these ports up and listening on the Internet is an idiot. Back in 2000 my company got its first DSL router for Internet acccess. Even that hardware came with an option just called "Microsoft Networking" blocks. Of course patch your boxes. Keep them updated. This would avoid some local host getting something propagated through your LAN/WAN. But as for the Internet aspect, God knows people should have learned. Ports 137, 138, 139, and 445 should be nowhere to be found from the Internet!
The DNS client vulnerability still puzzles me. From reading the advisory it appears as if the malicious party would have to be on a subnet between the DNS client and the DNS server. If this is the case exploiting this via the Internet might be a bit tough. But internally, a company that uses DNS could get rocked since the DNS clients and servers would likely be on the same LAN/WAN. Just thinking out loud...
The sysadmins are the ones stuck back in the server rooms trying to patch boxes, install new server software, script out client software pushes, working with network backups, etc. I froze my ass of in a 60 degree meat locker for 4 years doing all of this, plus administering the ACD phone system and managing all of my direct reports. It's not like I was hiding back there playing Freecell...
Wait a second here while I err... fires up Microsoft Vista Codename Nietzche desktop
Back about 7 years ago I was IT Manager of a major call center for a wireless provider. The centers were definitely redundant in that there were walls of UPS'es plus even building generator interaces so a truck could pull up outside and plug into the building to provide power as long as there was diesel gasoline available. This does smell fishy...
You sir, as a loyal Anonymous Coward are likely going to remain suspicious of every government's activity. Oh yeah, forgot. You are also going to:
1) Hate Microsoft.
2) Love Linux.
3) Be a Java or C++ code monkey.
4) Live in your parent's basement/grandmother's garage.
5) Not have a steady girlfriend.