0xbl00d writes "Eweek.com is reporting a new Microsoft Word zero-day attack underway. Microsoft issued a security advisory to acknowledge the unpatched flaw, which affects Microsoft Word 2000, Microsoft Word 2002, Microsoft Office Word 2003, Microsoft Word Viewer 2003, Microsoft Word 2004 for Mac and Microsoft Word 2004 v. X for Mac. The Microsoft Works 2004, 2005 and 2006 suites are also affected because they include Microsoft Word. Simply opening a word document will launch the exploit. There are no pre-patch workarounds or anti-virus signatures available. Microsoft suggests that users 'not open or save Word files,' even from trusted sources."
by Anonymous Coward
on Tuesday December 05 2006, @10:07PM (#17123728)
Yes! Great idea! Just trust all of your internal documents to a random third party company with no privacy guarantees. But hey, at least they've made a vague "Do no evil" promise!!1!
Isn't it more likely the sales patter for Office 2007 will become of course, if you were using our latest version...? Not that I'm suggesting Microsoft engineered it, mind... but it might not be as bad for them as seems initially
The slashot summary is deceptive (probably deliberately). From TFA:
Do not open or save Word files that you receive from un-trusted sources or that you receive unexpectedly from trusted sources.
The point is that there is a danger that a trojan on someone else's machine could start spreading infected Word files inside a corporation, or just amongst friends. Note furthermore:
The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
It can't be triggered automatically, and limited accounts (like every Vista system) will be largely unaffected. (Because exploits will usually try to root the box or install something, both of which will be prevented.)
Also observe that Office 2007 isn't affected. Obviously MS is doing something right in the next generation of their products.
(Serious non-flaming post ahead so don't mark me troll before at least reading!)
Putting aside your Microsoft fanboy attitude of 'oh just buy the next version and all will be well!' lets look at this objectively. And for the sake of being kind I wont go into details of how painful this will be for business in general; Sticking to the simple points will do just find to point out how horrible this is.
> Do not open or save Word files that you receive from un-trusted sources or that you receive unexpectedly from trusted sources.
Now you sound new to the world of tech as you haven't been embittered against Microsoft so I'll give you a break on this one. End users have two types of authentication; 'This looks shiny' *click* and 'Oh I know this person' *click*. So in reality the summary is an effective warning and really if some one in a business gets a document saying AccountsNov06.doc who is to say it is expected or unexpected - some one sent you the accounts and a nice little social engineering spiel to lure you to the click. Yes boss, three bags full boss.
> The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
> It can't be triggered automatically, and limited accounts (like every Vista system) will be largely unaffected. (Because exploits will usually try to root the box or install something, both of which will be prevented.)
See previous post about *clicky*. If you boss tells you to deal with AccountsNov06.doc then you deal with AccountsNov06.doc and that usually, if I'm not mistaken, involves opening it for a start. Also largely unaffected; what does that really mean? There will be a box come up saying 'Click me like you usually do as I get in the way of every simple task' because let me tell you as a system administrator even I started clicking them without thinking after two hours of testing Vista. Finally on this topic users who have limited accounts is a joke - even with your AD locking down almost all of the system most places still allow execution of applications and scripts which may have decent root kitting abilities that bypass user rights - only high schools and net cafes go the whole nine yards.
And lastly you have the gem of saying Microsoft is great because their next product line isn't affected. I think the parent to this post addressed this point perfectly with the following:
> You mean like not releasing them yet?
Which points out the flaw in your argument very nicely. Still it is worth expanding for those unfamiliar with Office 2k7 in that a) it implements a new XML document format which has nothing to do with.doc so isn't affected and b) they have time to fix their.doc filter layer so this doesn't happen in the wild under 2k7 - in fact I'd almost wager a decent price that the current release of Office 2k7 floating around the MS offices has the flaw and if it doesn't I'd be raising questions that this was a stunt to force upgrades and kill off.doc faster.
Either way before you mouth off at Slashdot consider the topic and its implications to users and business first; there are many real Slashdot exaggerations that are stabs at Microsoft and this isn't one of them. Some times it is apt to say that Microsoft really did drop the ball.
Both of your examples are the same thing; Preschool children by definition have the mental capacity of preschool children. In any case I stand by my claim which is based on several years of observation of this very problem as I wanted to see how they could fail so badly at basic authentication and fall for scams/spams/etc.
Also it is nice that you have time and the interest to educate your clients and I commend you (please assume no sarcasm in that line). Unfortunately as per a generalisation I do not believe your case is common and then of no important to the claim. Also many sys admins are in the added disadvantage that those who break the system are equal to them in standing and prefer to run their own affairs as they are 'grown ups who can tell the difference between right and wrong'...And seriously what can you say against that? While I will say they are pre-school children when it comes to computer based personal authentication I would never say it to their faces as they simply wouldn't understand the context and scope it was meant in. You may reply that I'm not giving my users enough credit...Though that is another argument which I'm not going to go into.
Note that our users also contact us when they are in doubt...Though it is rare that a doubtful response comes back from their 'friend' or 'shiny' assessment of a seemingly (to them) authentic email.
The Slashdot summary is deceptive (probably deliberately).
It's probably closer to the mark than "receive unexpectedly". If someone in a corporation became infected, and they infect documents on a shared network location -- game over. Other users don't have to "receive" it via a classic-email virus, but rather they just have to go about their daily business. You touched on this yourself, and it is why this does basically mean "there be dragons" for all word files in corporations.
It can't be triggered automatically, and limited accounts (like every Vista system) will be largely unaffected.
Phew! Now that we know that the burgeoning community of Vista users will be "largely unaffected", we're safe! That comprises the set that downloaded and installed the RTM from MSDN, so at a minimum, around an installed base comparable to QNX.
In any case, "largely unaffected" is more deceptive than the Slashdot summary (which came right from Cnet) -- the risk of compromises nowadays are seldom that they'll reconfigure your drivers or repartition your drive, thus requiring admin rights (when was the last time a virus was actually maliciously destructive in such a manner?), but rather that they'll compromise data integrity/security. If Bob is a normal user, but he's in HR and thus has rights to HR information, then so does an exploit running as Bob the unprivileged numbers-monkey.
It's not really deceptive, I often get attachments from almost everyone I regularly correspond with without expecting them first. Am I supposed to now call or email everyone I know every time they send me something to confirm that they intended to?
As for being hardly affected, it simply says LESS affected. What's to prevent the trojan from taking over your Outlook client and using it to send spam and propagate itself to everyone you know as well. Doesn't take root to do that, nor countless other things.
Yes, you absolutely did. There are no exploits running around in the wild affecting Macs. You can't cite a single real-world example. Not a single one.
What you conveniently leave out when you cited the long-ago debunked Mac mini hack is that the Mac was previously configured to give anyone an account who requested one, including full SSH access to poke around. Even the readers at Digg tore this one apart. Hardly the typical situation.
None of them are zero-day exploits?
Absolutely correct. None of them are being exploited at all.
Checking one of the UNIX utility vulnerabilities (because these are the only ones that we know when they were discovered) the perl vulnerability was discovered in December 2005.
And yet nobody's exploiting it, because OS X's security prevents access. Next.
With that perl vulnerability, and probably others in the list, it was discovered in 2005 and Apple only get around to releasing a patch now.
Which should tell you just how "urgent" it was to fix something that wasn't really a problem in the first place.
Look at the list above from Apple; you would have had to screen e-mail for HTML, new fonts, turn off your wireless card, not use any Windows shares, not go to any links to web pages given in e-mails, not go to any suspect web pages, etc, etc.
Lies, lies, and more lies. 100% false in every way imaginable.
The only difference is that Apple don't post security bulletins giving people warning, that might damage sales.
Uh, they do post security bulletins.
Have fun having a false sense of security though.
Ah, the old "false sense of security" canard, despite the fact THERE IS NOT A SINGLE EXPLOIT RUNNING IN THE WILD THAT IS INTRUDING ON A SINGLE MAC. You can't cite a single one. Go for it.
Do you have any other skewed, sliced-and-diced "facts" you want to post that I can debunk? Any articles you want to cite without revealing the full situation behind them? Clearly, you have some chip on your shoulder against Macs, but your shortcomings don't change the fact that there is not a single trojan or virus running the wild for Macs. Not one.
Get a stone tablet and a chisel. Those will also translate Word documents as well as make handy weapons for when your Microsoft Account Manager pops into your office.
As will OpenOffice.org on all platforms. That's not the point - how on earth can someone code so sloppily that a WORD PROCESSOR has a serious security exploit?! And more importantly, what feature in aforementioned WORD PROCESSOR requires *anything* that could pose a security issue?
Maybe the notion of writing all my papers in HTML wasn't so insane after all... no more of these archaic "pages", and it would certainly be a more reliable way of turning in assignments than e-mail attachments. Take care of a formatting stylesheet once, and from there on it's just using the <p> tag to full appropriateness.
how on earth can someone code so sloppily that a WORD PROCESSOR has a serious security exploit?!
The usual reason - a local buffer created from the stack set to a fixed size. ie.
char cbuf[MAX_BUFFER];
I would guess that the Microsoft Word document file will be arranged using a chunk data format: file header followed by object headers with type, version, length, followed by binary data for that object In this way, unknown chunks can just be skipped over.
It would be no surprise that each programmer coding a particular object (formula, table) would assume that only they would be theonly one writing read/write routines for their particular object, and choose to use a local stack buffer to store the raw binary data, before converting it to the internal data structure.
When reading the document, they would just read the header as normal (type,version,length), then read the specified amount of object data without checking the validity of the length.
And it only takes one programmer to make this mistake in order to create a security vulnerability that compromises the entire application. Get the right type of data in the Word document, and you could theoretically load and execute some executable code stored the file.
Yeah, I really want to submit users to random hangs while the Java VM garbage collects itself. Not to mention that yes, speed does matter, so until you can actually show some evidence of real-life shrink-wrapped applications running just as fast on a VM as on the metal, I think we'll stick with C++ (trust me, repagination is a lot of work, and it's already bad enough in long documents).
Given the choice between random sub-second hangs and random crashes with occassional virus infection, I'll take the former any day. Besides, modern VMs compile everything to machine code prior to execution (JIT), so there shouldn't be any significant speed penalty to them - and there isn't, as far as I can tell.
And if you think Word's too complex and shouldn't be doing that much work, you know where to find notepad (or vi), but good luck making professional documents; I'm fairly certain that most of our 500 million customers will stick with Word.
I guess they'll be seeing a lot of exploits in the future too, then.
trust me, repagination is a lot of work, and it's already bad enough in long documents
I don't use a word processor, I use LaTeX, which seems to have much better layout rules than any version of Word I have seen. The document I am working on is around 200 pages. Compiling it (including invoking gnuplot to draw a load of graphs, pulling in a few code files and syntax highlighting them, constructing an index and bibliography, and making sure all cross-references are correct) takes 7 seconds of wall time on my current laptop, and most of that is time spent waiting for I/O.
Oh, and much of the typesetting code used by LaTeX is written as interpreted macros that are run by the TeX runtime system. If it were all hard-coded, even in Java, it would be even faster.
Earlier this year, I saw a demo of a typesetting system written in Smalltalk (and running in the Squeak VM) that represented every character as an object, with simple rules (e.g. stay next to next character, jump to next line if you are over the margin, jump to the end of line if there is only whitespace between you and the end of line). It ran very fast; he dragged an image across a multi-page document, and the text re-flowed around it, and the entire thing was written in a couple of pages of Smalltalk.
If pagination is slow in Word, then I can only imagine it's because the developers need replacing.
If I can't even open my friends' documents then what am I - as a manager to do?
I don't know where you got your MBA, but the low-hanging fruit is there to be picked - in simple terms, you need to synergize new communications opportunities by leveraging existing facilities. Incentivize your staff to maximally capitalize on the benefits of an approach which unifies the output of global arboreal facilities, exsting team-member dexterity and some pens.
When I first read your post, I seriously thought you were joking. Then I realized you weren't. You're crazy. Rewrite an app the size of OO.org (in any language)? Are you serious?
Then maybe OO.org devs should learn how to write proper C++ code. It doesn't have to be that way. And if you think that CLASS INHERITANCE is the only reason to use C++, then you don't know C++.
By the way, am I alone in thinking that it would be a good idea to have OpenOffice.org re-written in the Java language? The Java license is now very appealing.
Umm... I think some out of work java programmers are with you. Oh, and I think you've got the support of memory chip manufacturers and makers of quad core CPUs.
Could the problem be avoided by opening the any.doc files with OO.org? i'm assuming that the exploit will only work if the file is actually opened with word, so it would stand to reason that opening it with some other application would be safe. can anyone tell me why i'm wrong?
The Security Advisory doesn't say not to open any DOC files. It says:
Do not open or save Word files that you receive from un-trusted or that are received unexpected from trusted sources. This vulnerability could be exploited when a user opens a file.
Microsoft suggests that users 'not open or save Word files,' even from trusted sources."
[pause] You know what - Just to be safe, maybe you just shouldn't boot up any Windows PCs for a few days. And if you do: For god's sake, don't plug in a network cable.
And thus begins the torrent of Microsoft mocking posts. Get your mod-points out and set them to +5 Funny because the laughs are only just beginning. *sigh*
My final project for the semester is attached as a Word document. If you have any problems reading it, please let me know. Me and everyone else in your address book.
Don't have to worry about grading it. By the time you read this, I will have used the root-kit to grade it myself.
Nice porn, by the way! You dog! We'll make this our little secret.
How is one supposed to exercise caution when opening a Word document? Do click on it slowly and deliberately, or do you click it carefully after giving the PC a pat on the head...
That is nothing more than standard precautions that one should take anyway. If you aren't expecting an attachment, don't open it. If you are expecting it, and it is from a trusted source, go ahead.
Really? I get documents that I'm not expecting all the time. I never have any fears opening Latex documents from anybody. You Microsoft folks sure have funny security.
Zero day [wikipedia.org]: At the time the details of the exploit are published (or the patch is released), there already is an active exploit being circulated. I guess if you don't know exactly when the exploit was released it's a technically "less than or equal to zero-day" exploit, but that doesn't sound as sexy.
It means that there is a working exploit out there in the wild, which is using a vulnerability that was previously unknown to the security community / the software maker. That is, there was zero days warning.
Microsoft Recommends.. (Score:5, Funny)
Now might be a good time to try ... (Score:5, Informative)
Parent
Re:Now might be a good time to try ... (Score:5, Insightful)
Yes! Great idea! Just trust all of your internal documents to a random third party company with no privacy guarantees. But hey, at least they've made a vague "Do no evil" promise!!1!
Parent
Re:ITS A TRAP! (Score:5, Funny)
It's always worked in the past. Why change a winning formula?
Parent
Its a good thing (Score:4, Funny)
Microsoft is just taking the paperless office to the next level - the documentless office.
Parent
Re:Now might be a good time to try ... (Score:5, Insightful)
Not that I'm suggesting Microsoft engineered it, mind... but it might not be as bad for them as seems initially
Parent
Re:Microsoft Recommends.. (Score:5, Funny)
Parent
Re:Microsoft Recommends.. (Score:5, Funny)
Parent
Re:Microsoft Recommends.. (Score:5, Insightful)
A broken lock is a broken lock even if no one takes advantage of that fact.
Parent
Re:Microsoft Recommends.. (Score:4, Informative)
Also observe that Office 2007 isn't affected. Obviously MS is doing something right in the next generation of their products.
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
(Serious non-flaming post ahead so don't mark me troll before at least reading!)
Putting aside your Microsoft fanboy attitude of 'oh just buy the next version and all will be well!' lets look at this objectively. And for the sake of being kind I wont go into details of how painful this will be for business in general; Sticking to the simple points will do just find to point out how horrible this is.
> Do not open or save Word files that you receive from un-trusted sources or that you receive unexpectedly from trusted sources.
Now you sound new to the world of tech as you haven't been embittered against Microsoft so I'll give you a break on this one. End users have two types of authentication; 'This looks shiny' *click* and 'Oh I know this person' *click*. So in reality the summary is an effective warning and really if some one in a business gets a document saying AccountsNov06.doc who is to say it is expected or unexpected - some one sent you the accounts and a nice little social engineering spiel to lure you to the click. Yes boss, three bags full boss.
> The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
> It can't be triggered automatically, and limited accounts (like every Vista system) will be largely unaffected. (Because exploits will usually try to root the box or install something, both of which will be prevented.)
See previous post about *clicky*. If you boss tells you to deal with AccountsNov06.doc then you deal with AccountsNov06.doc and that usually, if I'm not mistaken, involves opening it for a start. Also largely unaffected; what does that really mean? There will be a box come up saying 'Click me like you usually do as I get in the way of every simple task' because let me tell you as a system administrator even I started clicking them without thinking after two hours of testing Vista. Finally on this topic users who have limited accounts is a joke - even with your AD locking down almost all of the system most places still allow execution of applications and scripts which may have decent root kitting abilities that bypass user rights - only high schools and net cafes go the whole nine yards.
And lastly you have the gem of saying Microsoft is great because their next product line isn't affected. I think the parent to this post addressed this point perfectly with the following:
> You mean like not releasing them yet?
Which points out the flaw in your argument very nicely. Still it is worth expanding for those unfamiliar with Office 2k7 in that a) it implements a new XML document format which has nothing to do with
Either way before you mouth off at Slashdot consider the topic and its implications to users and business first; there are many real Slashdot exaggerations that are stabs at Microsoft and this isn't one of them. Some times it is apt to say that Microsoft really did drop the ball.
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
Also it is nice that you have time and the interest to educate your clients and I commend you (please assume no sarcasm in that line). Unfortunately as per a generalisation I do not believe your case is common and then of no important to the claim. Also many sys admins are in the added disadvantage that those who break the system are equal to them in standing and prefer to run their own affairs as they are 'grown ups who can tell the difference between right and wrong'...And seriously what can you say against that? While I will say they are pre-school children when it comes to computer based personal authentication I would never say it to their faces as they simply wouldn't understand the context and scope it was meant in. You may reply that I'm not giving my users enough credit...Though that is another argument which I'm not going to go into.
Note that our users also contact us when they are in doubt...Though it is rare that a doubtful response comes back from their 'friend' or 'shiny' assessment of a seemingly (to them) authentic email.
Parent
Re:Microsoft Recommends.. (Score:5, Insightful)
It's probably closer to the mark than "receive unexpectedly". If someone in a corporation became infected, and they infect documents on a shared network location -- game over. Other users don't have to "receive" it via a classic-email virus, but rather they just have to go about their daily business. You touched on this yourself, and it is why this does basically mean "there be dragons" for all word files in corporations.
Phew! Now that we know that the burgeoning community of Vista users will be "largely unaffected", we're safe! That comprises the set that downloaded and installed the RTM from MSDN, so at a minimum, around an installed base comparable to QNX.
In any case, "largely unaffected" is more deceptive than the Slashdot summary (which came right from Cnet) -- the risk of compromises nowadays are seldom that they'll reconfigure your drivers or repartition your drive, thus requiring admin rights (when was the last time a virus was actually maliciously destructive in such a manner?), but rather that they'll compromise data integrity/security. If Bob is a normal user, but he's in HR and thus has rights to HR information, then so does an exploit running as Bob the unprivileged numbers-monkey.
Parent
Re:Microsoft Recommends.. (Score:5, Insightful)
As for being hardly affected, it simply says LESS affected. What's to prevent the trojan from taking over your Outlook client and using it to send spam and propagate itself to everyone you know as well. Doesn't take root to do that, nor countless other things.
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
Yes, you absolutely did. There are no exploits running around in the wild affecting Macs. You can't cite a single real-world example. Not a single one.
What you conveniently leave out when you cited the long-ago debunked Mac mini hack is that the Mac was previously configured to give anyone an account who requested one, including full SSH access to poke around. Even the readers at Digg tore this one apart. Hardly the typical situation.
Absolutely correct. None of them are being exploited at all.
And yet nobody's exploiting it, because OS X's security prevents access. Next.
Which should tell you just how "urgent" it was to fix something that wasn't really a problem in the first place.
Lies, lies, and more lies. 100% false in every way imaginable.
Uh, they do post security bulletins.
Ah, the old "false sense of security" canard, despite the fact THERE IS NOT A SINGLE EXPLOIT RUNNING IN THE WILD THAT IS INTRUDING ON A SINGLE MAC. You can't cite a single one. Go for it.
Do you have any other skewed, sliced-and-diced "facts" you want to post that I can debunk? Any articles you want to cite without revealing the full situation behind them? Clearly, you have some chip on your shoulder against Macs, but your shortcomings don't change the fact that there is not a single trojan or virus running the wild for Macs. Not one.
Next.
Parent
Re:Microsoft Recommends.. (Score:4, Funny)
Parent
Re:Microsoft Recommends.. (Score:4, Funny)
Parent
Re:Microsoft Recommends.. (Score:5, Insightful)
Maybe the notion of writing all my papers in HTML wasn't so insane after all... no more of these archaic "pages", and it would certainly be a more reliable way of turning in assignments than e-mail attachments. Take care of a formatting stylesheet once, and from there on it's just using the <p> tag to full appropriateness.
Parent
Re:Microsoft Recommends.. (Score:5, Informative)
The usual reason - a local buffer created from the stack set to a fixed size. ie.
char cbuf[MAX_BUFFER];
I would guess that the Microsoft Word document file will be arranged using a chunk data format:
file header followed by object headers with type, version, length, followed by binary data for that object
In this way, unknown chunks can just be skipped over.
It would be no surprise that each programmer coding a particular object (formula, table) would assume that only
they would be theonly one writing read/write routines for their particular object, and choose to use a local stack
buffer to store the raw binary data, before converting it to the internal data structure.
When reading the document, they would just read the header as normal (type,version,length), then read the specified
amount of object data without checking the validity of the length.
And it only takes one programmer to make this mistake in order to create a security vulnerability that compromises
the entire application. Get the right type of data in the Word document, and you could theoretically load and execute
some executable code stored the file.
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
Given the choice between random sub-second hangs and random crashes with occassional virus infection, I'll take the former any day. Besides, modern VMs compile everything to machine code prior to execution (JIT), so there shouldn't be any significant speed penalty to them - and there isn't, as far as I can tell.
I guess they'll be seeing a lot of exploits in the future too, then.
Parent
Re:Microsoft Recommends.. (Score:5, Interesting)
I don't use a word processor, I use LaTeX, which seems to have much better layout rules than any version of Word I have seen. The document I am working on is around 200 pages. Compiling it (including invoking gnuplot to draw a load of graphs, pulling in a few code files and syntax highlighting them, constructing an index and bibliography, and making sure all cross-references are correct) takes 7 seconds of wall time on my current laptop, and most of that is time spent waiting for I/O.
Oh, and much of the typesetting code used by LaTeX is written as interpreted macros that are run by the TeX runtime system. If it were all hard-coded, even in Java, it would be even faster.
Earlier this year, I saw a demo of a typesetting system written in Smalltalk (and running in the Squeak VM) that represented every character as an object, with simple rules (e.g. stay next to next character, jump to next line if you are over the margin, jump to the end of line if there is only whitespace between you and the end of line). It ran very fast; he dragged an image across a multi-page document, and the text re-flowed around it, and the entire thing was written in a couple of pages of Smalltalk.
If pagination is slow in Word, then I can only imagine it's because the developers need replacing.
Parent
Re:Microsoft Recommends.. (Score:4, Insightful)
You want LaTeX. If you're running KDE, you can't beat Kile [sourceforge.net] as an editor.
Parent
Looks like a long work day tomorrow (Score:5, Funny)
Oh, wait - I don't do anything anyway and my life revolves around Excel.
Nevermind.
Re:Looks like a long work day tomorrow (Score:5, Funny)
I don't know where you got your MBA, but the low-hanging fruit is there to be picked - in simple terms, you need to synergize new communications opportunities by leveraging existing facilities. Incentivize your staff to maximally capitalize on the benefits of an approach which unifies the output of global arboreal facilities, exsting team-member dexterity and some pens.
Parent
Re:Looks like a long work day tomorrow (Score:5, Funny)
very alone
Parent
Re:Looks like a long work day tomorrow (Score:4, Insightful)
Then maybe OO.org devs should learn how to write proper C++ code. It doesn't have to be that way. And if you think that CLASS INHERITANCE is the only reason to use C++, then you don't know C++.
Parent
Re:Looks like a long work day tomorrow (Score:5, Funny)
Parent
Re:Looks like a long work day tomorrow (Score:4, Funny)
Umm... I think some out of work java programmers are with you. Oh, and I think you've got the support of memory chip manufacturers and makers of quad core CPUs.
Parent
Re:Looks like a long work day tomorrow (Score:4, Funny)
>> That's a lot more than two words. Perhaps you should have used the preview button?
Never attended a presentation ? Thats actually a Powerpoint users notion of two words.
Parent
Lets see... (Score:5, Funny)
So let me get this straight... For the time being the only safe Word files are new files that other people don't need to open?
But hey, you saved a ton of money on retraining costs.
what about OO.org? (Score:5, Insightful)
Good Advice (Score:4, Funny)
Good general advice, really. They should put that on the Office packaging, like on a packet of cigarettes.
ant
Work-Around = OpenOffice (Score:5, Informative)
Re:Work-Around = OpenOffice (Score:4, Insightful)
Parent
Not open or save? (Score:4, Funny)
Misleading summary (Score:4, Informative)
2cv
Just to be safe.. (Score:5, Funny)
Re:Just to be safe.. (Score:4, Funny)
Parent
Obvious Response (Score:4, Insightful)
Oh, great! (Score:5, Funny)
Yet ANOTHER feature Word has that OpenOffice doesn't. :(
This aughta make FINALS more interesting... (Score:5, Funny)
My final project for the semester is attached as a Word document. If you have any problems reading it, please let me know. Me and everyone else in your address book.
Don't have to worry about grading it. By the time you read this, I will have used the root-kit to grade it myself.
Nice porn, by the way! You dog! We'll make this our little secret.
love,
toodles
Exercise caution... (Score:5, Funny)
we're all going to die.... (Score:5, Funny)
Re:Article Summary is Flamebait (Score:5, Insightful)
Really? I get documents that I'm not expecting all the time. I never have any fears opening Latex documents from anybody. You Microsoft folks sure have funny security.
Parent
Re:Article Summary is Flamebait (Score:5, Funny)
Parent
Re:Article Summary is Flamebait (Score:4, Funny)
Parent
Re:zero day (Score:4, Informative)
Parent
Re:zero day (Score:5, Informative)
Parent
Re:Bah, typical bullshit non-edited craptastic blu (Score:5, Funny)
Parent