This is far from being a humiliation. The OSCE was asked by Secretary of State Colin Powell to monitor the upcoming election.
Furthermore, this isn't the first time they have monitored an election in the U.S. They monitored both the 2002 midterm elections and the California gubernatorial recall election.
To delete the hidden administrative shares for all root partitions and volumes (such as C$) and the system root folder (ADMIN$) and to prevent Windows from re-creating them, add an AutoShareWks DWORD value to the following registry key, and then set its value data to 0:
Even if it did not, deleting the root drive admin share and some others breaks Windows in various and sundry ways because even some local services rely on these admin shares.
Most home users do not need or use these services.
Can you show me one site that says anyone survived the Hindenburg? IMO that's just a whole load of too much fire + big fall to be survivable.
Almost 2/3 of the people on board survived. There was a History Channel show about the accident. A teenage crew member who worked in the galley even managed to recover his watch intact from the wreckage the day after the accident.
Fortunately, Microsoft doesn't manufacture my VoIP terminal.
Yes they do. It's called Windows XP.
Microsoft will provide SIP support on PCs with Windows XP and Windows Messenger, on smart devices with Windows CE 4.0, on the server with Windows Server 2003 and in other embedded devices with Windows XP Embedded, enabling unprecedented levels of interoperability for essentially any type of communications on essentially any device.
Well, having read all of the Harry Potter books aloud to my two sons, I think I might enjoy something a little different and oriented more towards adults.
Try something by Gregory Maguire. The Maguire book everybody has heard of is Wicked, and is still an interesting read, even if the book is a little over-hyped.
I helped develop a system about 8 years ago that used RSA SecureIDs to log on to the system. The SecureID card or fob, in AOL's case, has a small computer in it which continuously executes an algorithm to generate a sequence number. The card is a self-contained system that automatically stops working after 4 years. I'm not sure if this is due to the battery being drained, or something to do with the algorithm used.
During logon, the user enters their user ID and the sequence number from their card. Since the sequence number changes every 10 seconds, the user has ten seconds to enter the current sequence number when they log in. If they don't make it in ten seconds, the login is not allowed, and they have to enter the next sequence number. There is a small "bar graph" next to the sequence number that tells the user exactly how much time they have left to enter the number.
Our system used the model of SecureID with the built in keypad. The system we used was different from the AOL system in that you entered a PIN into the card, and the card would then tell you what the correct sequence number you should enter was. The SecureID AOL chose to use always displays the sequence number, and you enter it and your password when you log on. The SecureID system we used is more secure, because someone can't use a keylogger to get your password, and then steal your card.
The sequence number is then authenticated against a server (called ACE) that is able to calculate the next sequence number for any card that it knows about. When logging in, the card's version of the sequence number is compared to the ACE server's version of the sequence number, and if it matches, the login is allowed. The ACE logon sequence can be integrated into any application using a fairly simple API. For our application, we integrated the ACE API with NSAPI for use with Netscape servers.
Now, here's the problem. The algorithm is not without its faults. Sometimes the card and the server disagree on what the next sequence value is. This can happen easily if you don't enter the sequence number within the 10 second time limit a number of times, or the sequence number changes just as you finish entering it. When this happens, the card is considered "skewed", and there is a sequence of operations that need to be performed to "unskew" the card, that consist of having the user enter the currently displayed sequence number a number of times. If there is a problem unskewing the card, the user gets locked out. A user can also be locked out if their card is skewed too many times.
Skewing happens often enough to be annoying from a technical support point of view. We had to deal with it quite often with our application, and we did not have more than 200 users. Our users were used to dealing with security, and this type of hardware was not new to them (i.e. experts). Now think about how many cluless users AOL is going to have for this service, and how many people are going to mess up when unskewing their card. This is going to be a technical support nightmare.
there are four or five hacks out there working on spec scripts for an episode of LAX based on this, and the executive producer probably thought, as his plane was routed to another airport "Hmmm, ripped from the headlines..."
In this episode, an angry mob of late passengers kills the technician who was supposed to reset the computer. The episode will be used to launch CSI: Los Angeles.
Chris Finke
920 Delaware St SE #3003
Minneapolis, MN 55414
Dear Chris,
Thank you for posting your home address in a public forum. Now we know where you live. Do you have any idea what we are going to do to you? Do you? We're going to...
SEND YOU UNSOLICITED COMMERCIAL JUNK MAIL!!!!!
MUH, HA, HA, HA!
Sincerely,
The International Brotherhood of Spammers and Unsolicited Bulk Email Advertisers
Well, I am just outraged! Why does the FTC want me to put paper towels on spammers? Are they going to microwave them or something? Furthermore, why does it have to be Bounty, in particular? I know it's supposed to be the, "quicker picker-upper", but, come on, can I at least use a bargain brand like Marcal? This is just insane...
What?!?! A reward offered by the government for acts deemed beneficial to the state...?
As many have said, just load all of your pages without the leading [section] on [section].slashdot.org, and you'll get Slashdot green. Its not that hard. When you look at t page, go to the location bar, remove the section and reload.
Your condescending attitude notwithstanding, if you'd actually read my post, you'd know I already know how to do that.
I know, "it's not that hard", but the point is that I shouldn't have to do that in order to read an article without hurting my eyes. I am suggesting that maybe it should be changed so that Slashdot always uses a plain default if the user wants it.
Go take a look at games, think about how much worse it is and how much longer it's existed, then think about how likely it is that any of the/. editors actually cares enough to do anything in response to the complaints.
Yes, Games is a little annoying too. The difference, however, is that the beige-on-white is hard to read, and painful. Games just doesn't affect me that way, because the darker purple provides some contrast.
It would be nice if there was a option in the preferences somewhere that would "force all pages to be Slashdot green". That way, we wouldn't have to keep removing "it" from the URLs of stories, or changing it to something more imaginative.
We're hoping to move to XHTML in the future (sometime within the next year, for sure, I hope) but like everything else it goes on our priority list based on resource-cost and benefit. There are bugs that need to be squashed, meaningful features to be added, and performance improvements we need to put into place that come first.
Like changing the IT colors to something that doesn't cause blindness? (please oh please oh please oh please...)
I believe the reason that extensions keep breaking in new versions is that the XPCOM object model keeps changing. Until that's nailed down, extensions will continue to need periodic updating.
I went through the process of upgrading all my extensions yesterday when I upgraded to Firefox 1.0PR, and you know what the most common reason for an extension not working was?
The fscking author used a maxVersion field of "0.9.3". Once this is changed, most of the extensions I use run fine.
Furthermore, I think this is possibly compounded by Firefox not handling a maxVersion like "0.9+" correctly, or possibly not understanding that "0.10" is after "0.9". I'm not sure, but that's what seems to be happening.
The worse part is that most of the extension authors don't have releases yet that fix this annoying little problem.
Slashdot Mirror
This is far from being a humiliation. The OSCE was asked by Secretary of State Colin Powell to monitor the upcoming election.
Furthermore, this isn't the first time they have monitored an election in the U.S. They monitored both the 2002 midterm elections and the California gubernatorial recall election.
So, uh, quit your bitchin'.
Probably not, since the OSCE is based in Vienna, Austria.
Only because you didn't RTFM.
Even if it did not, deleting the root drive admin share and some others breaks Windows in various and sundry ways because even some local services rely on these admin shares.Most home users do not need or use these services.
Almost 2/3 of the people on board survived. There was a History Channel show about the accident. A teenage crew member who worked in the galley even managed to recover his watch intact from the wreckage the day after the accident.
I'd just like to point out that 66% of the people on board the Hindenburg survived.
I'm not saying that more people couldn't have been saved, I'm just pointing out that the number of survivors is a lot higher than most people think.
Yes they do. It's called Windows XP.
http://www.microsoft.com/windowsxp/evaluation/feaThere's also this to worry about:
http://www.jasomi.com/press/NW_MS_Article.pdf
I'd just like to point out that there has been exploits for the phone system since the days of Captain Crunch.
Secondly, there are already exploits for Cisco VOIP phones.
Lastly, the viruses he's talking about would exploit defects in the code by sending malformed RTP packets or SIP headers.
I myself have managed to accidentally crash an IAD by sending a malformed ATM packet with G711 voice data in it, so DOS attacks are even easier.
This article sounds more like another company trying to promote their "solution in search of a problem."
I totally agree with you there. This sounds like scaremongering in an attempt to get VC funding.
Yeah, only if she's five-three!
- Sir Mixalot
Try something by Gregory Maguire. The Maguire book everybody has heard of is Wicked, and is still an interesting read, even if the book is a little over-hyped.
So what you're saying is that the tokens come with a "Happy Ending", right?
Well, she gives good head anyway, but that's probably because hers is detachable.
Never attribute to malice that which can be explained by incompetence.
During logon, the user enters their user ID and the sequence number from their card. Since the sequence number changes every 10 seconds, the user has ten seconds to enter the current sequence number when they log in. If they don't make it in ten seconds, the login is not allowed, and they have to enter the next sequence number. There is a small "bar graph" next to the sequence number that tells the user exactly how much time they have left to enter the number.
Our system used the model of SecureID with the built in keypad. The system we used was different from the AOL system in that you entered a PIN into the card, and the card would then tell you what the correct sequence number you should enter was. The SecureID AOL chose to use always displays the sequence number, and you enter it and your password when you log on. The SecureID system we used is more secure, because someone can't use a keylogger to get your password, and then steal your card.
The sequence number is then authenticated against a server (called ACE) that is able to calculate the next sequence number for any card that it knows about. When logging in, the card's version of the sequence number is compared to the ACE server's version of the sequence number, and if it matches, the login is allowed. The ACE logon sequence can be integrated into any application using a fairly simple API. For our application, we integrated the ACE API with NSAPI for use with Netscape servers.
Now, here's the problem. The algorithm is not without its faults. Sometimes the card and the server disagree on what the next sequence value is. This can happen easily if you don't enter the sequence number within the 10 second time limit a number of times, or the sequence number changes just as you finish entering it. When this happens, the card is considered "skewed", and there is a sequence of operations that need to be performed to "unskew" the card, that consist of having the user enter the currently displayed sequence number a number of times. If there is a problem unskewing the card, the user gets locked out. A user can also be locked out if their card is skewed too many times.
Skewing happens often enough to be annoying from a technical support point of view. We had to deal with it quite often with our application, and we did not have more than 200 users. Our users were used to dealing with security, and this type of hardware was not new to them (i.e. experts). Now think about how many cluless users AOL is going to have for this service, and how many people are going to mess up when unskewing their card. This is going to be a technical support nightmare.
So, that's what we're doing wrong! I'll go deploy the unflawed software right now.
Thanks, I wish I had thought of that.
In this episode, an angry mob of late passengers kills the technician who was supposed to reset the computer. The episode will be used to launch CSI: Los Angeles.
LICK IT! LICK IT!
Dear Chris,
Thank you for posting your home address in a public forum. Now we know where you live. Do you have any idea what we are going to do to you? Do you? We're going to...
Sincerely,The International Brotherhood of Spammers and Unsolicited Bulk Email Advertisers
Well, I am just outraged! Why does the FTC want me to put paper towels on spammers? Are they going to microwave them or something? Furthermore, why does it have to be Bounty, in particular? I know it's supposed to be the, "quicker picker-upper", but, come on, can I at least use a bargain brand like Marcal? This is just insane...
What?!?! A reward offered by the government for acts deemed beneficial to the state...?
Oh.
Nevermind...
Your condescending attitude notwithstanding, if you'd actually read my post, you'd know I already know how to do that.
I know, "it's not that hard", but the point is that I shouldn't have to do that in order to read an article without hurting my eyes. I am suggesting that maybe it should be changed so that Slashdot always uses a plain default if the user wants it.
Yes, Games is a little annoying too. The difference, however, is that the beige-on-white is hard to read, and painful. Games just doesn't affect me that way, because the darker purple provides some contrast.
It would be nice if there was a option in the preferences somewhere that would "force all pages to be Slashdot green". That way, we wouldn't have to keep removing "it" from the URLs of stories, or changing it to something more imaginative.
It's now over half a million.
Like changing the IT colors to something that doesn't cause blindness? (please oh please oh please oh please...)
Alright, it's make fun of Techefnet's comments day! Here we go...
Thats so unfear.
Techefnet does not fear the undead, but he sure unfears the dead!
That sucked. Damn. Forget I said anything...
I went through the process of upgrading all my extensions yesterday when I upgraded to Firefox 1.0PR, and you know what the most common reason for an extension not working was?
The fscking author used a maxVersion field of "0.9.3". Once this is changed, most of the extensions I use run fine.
Furthermore, I think this is possibly compounded by Firefox not handling a maxVersion like "0.9+" correctly, or possibly not understanding that "0.10" is after "0.9". I'm not sure, but that's what seems to be happening.
The worse part is that most of the extension authors don't have releases yet that fix this annoying little problem.
You did remember to save your MBR before you overwrote it, right?
Set the blocksize to 446 if you don't want the partition table.Now you can restore the MBR with:
Again, set bs to 446 if you didn't save the partition table.If you want to create a new Windows MBR, try one of the following:
On Windows 95/98/ME use a boot disk, and then type:
On Windows 2000/XP boot the OS CD, select, "recovery console", and type: