Slashdot Mirror


Few of OOXML's Flaws Have Been Addressed

I Don't Believe in Imaginary Property writes "IBM's Rob Weir has done a study on how many flaws were addressed by the OOXML Ballot Resolution Meeting. So far, using a random sampling technique, he has yet to find a flaw that was addressed, making the upper bound a paltry 1.5%. Even so, he's found a number of new flaws, including a security vulnerability: OOXML stores passwords in database connection strings in plain text. At least there were no mistakes on five of the first twenty five random pages he reviewed."

162 comments

  1. Corruption. by twitter · · Score: 5, Insightful

    Why fix flaws when you can buy voters?

    --

    Friends don't help friends install M$ junk.

    1. Re:Corruption. by Anonymous Coward · · Score: 2

      Hey, if the voters are selling cheap, why not?

    2. Re:Corruption. by Almahtar · · Score: 1

      Oh, I dunno... morals? Just throwin' it out there.

    3. Re:Corruption. by L4t3r4lu5 · · Score: 1

      Morality is for the working class.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    4. Re:Corruption. by Almahtar · · Score: 1

      I pity you.

  2. Office 2007 by number6x · · Score: 4, Interesting

    Do any of these flaws exist in Office 2007?

    If not, why are they in the OOXML proposed standard. If the standard does not describe the OOXML format used by Microsoft, then what does it describe?

    Why can't they just document the format that they use and get this over with? Or are they doing all this for show, and there is no real substance in OOXML?

    1. Re:Office 2007 by corsec67 · · Score: 4, Insightful

      Or are they doing all this for show, and there is no real substance in OOXML?

      The reason MS is bothering with ISO is because a few places have started to require that documents be stored in an ISO defined format.

      The problem is that having a true ISO defined format means that you open yourself up to competition, so MS wants to get their format defined as ISO certified without allowing any competition.

      --
      If I have nothing to hide, don't search me
    2. Re:Office 2007 by Naughty+Bob · · Score: 1

      Let's not look a gift horse in the mouth. If MSFT had corrected the flaws, they'd probably be able to crowbar their 'standard' through the relevant hoops.

      As it is, a true, open, unencumbered standard will instead prevail.

      --
      "Be light, stinging, insolent and melancholy"
    3. Re:Office 2007 by Basilius · · Score: 5, Insightful

      There are no existing implementations of the proposed OOXML standard, so whether Office 2007 has the same defects or not is sort of irrelevant. MSFT has stated that they will not be implementing the standard as proposed, but will be going a different direction. And, given the nature of parts of the standard, nobody BUT Microsoft can fully implement it.

      The mere fact that there ARE no implementations of OOXML, however, should be a giant, florescent, waving red flag. No standards body should adopt a standard that cannot and will not be implemented by the proposers.

    4. Re:Office 2007 by flymolo · · Score: 1

      Some of these are flaws in the specification. Like not explaining ranges or the description of a field being a URL, but the type any string. It comes down to the spec was written post hoc, and Office 2007 probably isn't run through a spec compliance test suite.

      The database connection flaw may not be in Office either, because Office may force System DSNs rather than real connection strings.

      --
      "Sometimes it's hard to tell the dancer from the dance." --Corwin Of Amber in CoC
    5. Re:Office 2007 by belmolis · · Score: 3, Insightful

      Indeed. And the lack of existing implementations makes OOXML all the more inappropriate for the fast track process, which is intended for existing de facto standards, meaning (a) widely implemented and (b) with broad consensus in the relevant field.

    6. Re:Office 2007 by UnknowingFool · · Score: 2, Insightful

      As far as I know even Office 2007 can't do OOXML well.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    7. Re:Office 2007 by peragrin · · Score: 4, Insightful

      If MSFT fixed the flaws with OOXML then there wouldn't be a problem.

      it's not that OOXML is bad, it is that OOXML is broken and MSFT is trying to ram it through anyways. there is nothing there that can't be fixed. MSFT however doesn't want it fixed because OOXML 2010 is just around the corner and it won't be the same as OOXML 2007. Also OOXML 2010 becomes a defaco standard even though it isn't ISO certified since it is marketed as OOXML.

      this is how MSFT works if you don't know this then go back and look at the past 30 years of how MSFT treats it's customers, vendors, and slaves.

      --
      i thought once I was found, but it was only a dream.
    8. Re:Office 2007 by prshaw · · Score: 1

      >> The mere fact that there ARE no implementations of OOXML, however, should be a giant, florescent, waving red flag.

      Using this logic C++ would never have become the language it is today. It may never have become a language at all.

    9. Re:Office 2007 by TropicalCoder · · Score: 5, Interesting

      You'll remember Stéphane Rodriguez who gave us Microsoft Office XML formats? Defective by design back in August, 2007?

      Since then, in February, 2008 he produced The truth about Microsoft Office compatibility and Typical B.S. in technical articles about OOXML and now Bad surprise in Microsoft Office binary documents : interoperability remains impossible Thursday, March 13, 2008.

      These blogs are at the same level of depth as Rob Weir's latest blog, and demonstrate that Microsoft's policies as detailed below continue to this day.

      From OOXML is defective by design...

      "Mr Bill Gates in person sent in 1998 a memo to the Office product group (led by Steven Sinofsky at the time), memo undisclosed to the public thanks to the IOWA consumer case :"

      From: Bill Gates

      Sent: Saturday, December 5 1998

      To: Bob Muglia, Jon DeVann, Steven Sinofsky

      Subject : Office rendering

      One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company.

      We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities.

      Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy Windows.

      I would be glad to explain at a greater length.

      Likewise this love of DAV in Office/Exchange is a huge problem. I would also like to make sure people understand this as well.

      -----------


      Clearly the word is getting out about the problems in OOXML. Stéphane Rodriguez notes at the bottom of OOXML - Defective by design:

      Update : this article was Slashdotted on Sunday 26 of August.

      Update2 : this article is taking 300,000 hits a day, and is making it all around the world in all kinds of sites. My web host provider was so angry at the peak in traffic that he threatened to cut me off, so I had to redirect to a blog site such as Google's blogger to host the article.

      Update3 : wednesday august 29, added a new section on Document security

      Update4 : friday august 31, added more content to sections US English and Windows dates

      Update5 : sunday september 2, added a quick comparison between ODF and ECMA 376

    10. Re:Office 2007 by Anonymous Coward · · Score: 1, Insightful

      Even if they fixed the flaws in the standard, they would not fix them in Office. They would still claim to support an open standard. Competitors would still have to support the actual format, rather than the one defined in the standard.

    11. Re:Office 2007 by Naughty+Bob · · Score: 1

      If MSFT fixed the flaws with OOXML then there wouldn't be a problem.
      Pop quiz, hot shot! Reconcile your statement above with your statement below.

      this is how MSFT works if you don't know this then go back and look at the past 30 years of how MSFT treats it's customers, vendors, and slaves.
      For bonus points, explain how what you say is a reply to my post.

      Standards need to be open, unencumbered by patents, and as easy to implement by third parties as they are by the originators. MSFT has failed in these basic requirements.
      --
      "Be light, stinging, insolent and melancholy"
    12. Re:Office 2007 by Anonymous Coward · · Score: 0
      it's not that OOXML is bad,

      Jury is still out regarding that part. But OOXML definitely is unnecessary: there is already OpenDoc (OOo) which is a standard that is implemented and supported by multiple vendors, and seems to do rather good a job in what it's meant to do. Really, it's one of better document format standards I have read through (and this was 4 years ago or so, which means it has had chance to further mature). It's implement by almost _all_ vendors, save one big one...

      So here's hoping that OOXML will get recognized obsolete as it is.

    13. Re:Office 2007 by Breakfast+Pants · · Score: 1

      C++ only became an ISO standard in 1998.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    14. Re:Office 2007 by prshaw · · Score: 1

      And from what I remember there was not a fully compliant implementation of the standard when it came out. And not for several years afterwards. I seem to recall one or two companies that did have a real close frontend, but they were not 100%.

      It was a fun time trying to write portable c++ code that would compile on Sun, VMS, Windows, and AIX at the time.

    15. Re:Office 2007 by harlows_monkeys · · Score: 1

      Stéphane Rodriguez lost all credibility when he edited an OOXML spreadsheet file by hand, changed the XML so that it was no longer legal according to the schema, and then proclaimed that it was a flaw in OOXML that Excel found an error in the document.

    16. Re:Office 2007 by TropicalCoder · · Score: 1

      Stéphane Rodriguez lost all credibility when he edited an OOXML spreadsheet file by hand, changed the XML so that it was no longer legal according to the schema, and then proclaimed that it was a flaw in OOXML that Excel found an error in the document.

      Brilliant piece of misrepresenting an experiment made to illustrate a point, then dismissing everything this man has said. Congratulations on your rhetoric! Or perhaps you aren't that brilliant, and simply did not understand the article. For those who don't know what the parent is referring to, he is most likely referring to original Aug. 2007 article "Broken by Design", where Rodriguez demonstrates how badly engineered the design of OOXML is. There are so many interdependencies that a tiny change will require a complete "recompilation" of the document to be done by the code parsing the XML.

    17. Re:Office 2007 by TheRealSlimShady · · Score: 1
      it's not that OOXML is bad, it is that OOXML is broken and MSFT is trying to ram it through anyways

      I'm not sure how Microsoft is trying to "ram it through" - Microsoft are following the ISO process for standards that are developed externally (i.e. not developed inside ISO). That process is called fast track, and it's how ISO deals with "existing" standards.

    18. Re:Office 2007 by harlows_monkeys · · Score: 1

      Incorrect. All that was required for the update he wanted to do was either (1) updating two locations, not one, or (2) removing one file. The spreadsheet file stores some extra information as an optimization to allow spreadsheets to load faster (basically, information on calculation chains).

      Here is a thorough point-by-point response to Rodriguez's points.

      BTW, it is interesting to note the comments when this was discussed on Brian Jones' blog. Note that he lets Rodriguez comment, even though Rodriguez is strongly against OOXML to the point of rudeness.

      That's a pattern I see on most of the pro-OOXML blogs I've read. They let the other side come in and have its say. They often even link to the opposing arguments. You go read Jones' blog, for example, and the impression you get is that it is written by someone strongly in favor of OOXML, but who wants to be fair and make sure all arguments are heard. He's confident that if that happens, he'll win.

      That's sure not how the anti-OOXML blogs operate. They often turn off comments completely. They don't link to opposing blogs. They mostly just attack, and the attacks are often factually incorrect. And when they do actually post a valid technical flaw in OOXML, half the time ODF has the same technical flaw, but that never seems to bother them. I sure don't get the impression from, say, Weir's blog or Sutor's blog that I'm reading the writings of someone who wants to be fair and present a winning technical argument.

    19. Re:Office 2007 by TropicalCoder · · Score: 1

      We know about you and your buddy Miguel. What's your agenda, you guys - anyhow? Your support for Microsoft flies in the face of all logic. You think this world will somehow be a better place when there is only One Microsoft Way? - for document formats, on the desktop, on the Net? I'm not going to take the bait, and I don't have the detailed knowledge to rebut this. Nor will I call you a Microsoft shill or a troll. I don't know who you are, and for all I know, if I met you, maybe I would like you. You are welcome to your point of view and any advantages you gain from from this. This world is big enough for us all. Live long and prosper!

    20. Re:Office 2007 by Anonymous Coward · · Score: 1, Insightful

      Why? Because ODF is competition, and the only response MS knows to competition is to extinguish it wherever they see it. When organisations the world over start look as if they're going to mandate use of ODF because it's a standard, that means they're also mandating the use of non-MS products. MS aren't going to add meaningful ODF support to Office until they've *really*, *really* lost this fight, because that would be the thin end of a very big wedge indeed, allowing people to start to move off Windows seats and onto alternatives, and they *really* don't want people thinking that way, because the amount of money they stand to lose is astronomical. So MS want to keep the softwear seats, come what may, and they're not remotely interested in helping their customers meet their business needs if that threatens MS profits.

      In summary, whenever ODF rears its head as a threat, MS want to be able to point to OOXML and say "OOXML is a standard already, and all your people are already using it - you don't need another". They don't care that it's a standard that no-one else will be able to support even if they want to, because they know that most of the people making the actual decisions not only won't remotely understand the technical issues, but also will have no interest doing so - after all, "a standard is a standard, isn't it?". And MS will point to all the "extra" money that moving to a "different" standard will cost. And the guys who understand what total BS the argument really is, and why it means that, say, ten years from now the organisation won't be able to read the documents it produces today, will have a massively difficult job on their hands to even make the execs understand what the arguments are, let alone to actually win them. And meanwhile, MS will carry on raking the money in from their monopoly, and doing whatever they can to keep it that way.

    21. Re:Office 2007 by Anonymous Coward · · Score: 0

      MS are not only not going to fix the flaws in OOXML to make it usable, they positively *need* it to be unusable. Having competitive products supplanting Office is not what MS is about. This whole play is about killing competition - keep control of the product space, get the magic "standard" tag for whatever incompatible rubbish they've pushed out so far, and do so in a way that no-one else can actually emulate. The possibility that it might actually come off is positively an MS exec's wet dream.

    22. Re:Office 2007 by Ernesto+Alvarez · · Score: 1

      I don't think buying voters, setting very short deadlines for comments, and stuffing meetings is standard procedure.

    23. Re:Office 2007 by aproposofwhat · · Score: 1
      The database connection flaw is serious, but not just because it is stored in plain text.

      It is serious because it is in an open standard, and even if it were encrypted or obfuscated in some way, the way to reverse that encryption or obfuscation would have to be documented too (so that others can implement it properly).

      The very act of embedding an ODBC connection string rather than a DSN in an open document format is what is wrong here - not the fact that it's in plain text.

      --
      One swallow does not a fellatrix make
  3. Who said said OOXML is a "superb standard" ?? by Dara+Hazeghi · · Score: 0

    I can't remember that guy's name , but it just occurred to me that Microsoft could have paid him big $$$ to say that. Think about it... a highly respected member of the open source community says that OOXML is a superb standard! What a great way to garner support! Think it's not possible? We know that Microsoft heavily bribed all the banana republics that joined ISO as voting members.

    --
    Left 404: Why the RIGHT is WRONG
    1. Re:Who said said OOXML is a "superb standard" ?? by Naughty+Bob · · Score: 1

      It was Miguel 'The Mexican quisling' de Icaza.

      I don't think payment is necessary though, given enough people in any subset, you'll always be able to find the one that doesn't get it.

      --
      "Be light, stinging, insolent and melancholy"
    2. Re:Who said said OOXML is a "superb standard" ?? by pipatron · · Score: 3, Informative

      It was Miguel de Icaza, and he is paid money indirectly from Microsoft since he works for Novell.

      One of the reasons I stopped using GNOME, I don't want anything to do with the Mono project.

      --
      c++; /* this makes c bigger but returns the old value */
  4. Re:Whatever by Anonymous Coward · · Score: 5, Funny

    Ballmer is that you?

  5. huh? by trybywrench · · Score: 4, Interesting

    This may be off topic but why exactly are there database connection strings in a document format?

    --
    I came to the datacenter drunk with a fake ID, don't you want to be just like me?
    1. Re:huh? by Shados · · Score: 4, Informative

      Because people actually do work with Office Suites, and they are an integral part of the workflow and ecosystem of significant companies IT.

      For example, a spreadsheet is often the favored client for an OLAP system, and complex spreadsheets will get reused a lot, so connection strings may be part of the overall "application" that the document has become.

      People like me and (probably) you tend to use documents as just that: documents. But in the big boy's world, they're far more important than that.

    2. Re:huh? by Anonymous Coward · · Score: 0

      Because MSSQL Server connection strings are too big to be memorized.

    3. Re:huh? by jfclavette · · Score: 2, Informative

      They're there for data bindings to databases, which can be used for anything from mass mailing clients to generate a list of items with pricing.

      I'd be interested in what is the alternative to storing them in plaintext in the document format. See, the database is going to be wanting that password, and it must be stored somewhere in the document in a stand-alone way or remembered by the user. If you encrypt it, you need to provide the keys in the same document or use a constant well-known key across all instance of the software. Hardly good security. The users might be willing to remember them, and I'm sure that's an option. In a lot of instances, credentials stored as plaintext with read-only permissions on specific tables is a fine solution, and you can do the security at the file access rights level. I would hardly call that a 'security hole'.

    4. Re:huh? by Anonymous Coward · · Score: 0

      It certainly is on-topic. If you have ever dug around through a Microsoft API, you will be surprised by the amount of obscure or redundant features. I would expect unusual things to be found in a format created in Redmond.

      (note: not trying to be flame bait, I'm sure the other guys have bloat. I just see an unusually large amount of bloat when doing programming work with Microsoft technology on my windows box)

    5. Re:huh? by Yetihehe · · Score: 1

      Just in case you need to pull data from database to calculate some data in your document (for example presentation which shows a list of current clients, not list of clients available at the moment of making this presentation).

      --
      Extreme Programming - Redundant Array of Inexpensive Developers
    6. Re:huh? by Ed+Avis · · Score: 1

      +1

      It is not a security flaw to store passwords in plain text - or at least, 'encrypting' them with some fixed algorithm gives no security benefit. At best it's security through obscurity.

      In fact, it's surprisingly sensible of Microsoft to recognize this, given the 'compressible encryption' and other non-security security nonsense they provide in other products.

      --
      -- Ed Avis ed@membled.com
    7. Re:huh? by RobBebop · · Score: 2, Informative

      But in the big boy's world, they're far more important than that.

      I acknowledge that hooking documents into databases to subvert them into workflow process template beasties is a common practice, but I think the simple question "Why are there database passwords in the document?" kind of highlights that this is a bad practice.

      If security is a concern, "Document Applications" are a mistake.

      This also violates the (good) Model/View/Controller software architectural model by kludging the view and controller together in the same product. And - despite claims that it cuts development time in half and saves a business money - it is a disaster to maintain and costs significantly more to re-write when opportunities to upgrade to better Office Productivity Suites arise.

      Unless you WANT to periodically rewrite your companies homespun IT applications, you should probably avoid hitching your Office Documents to Databases.

      --
      Support the 30 Hour Work Week!!!
    8. Re:huh? by trybywrench · · Score: 1

      For example, a spreadsheet is often the favored client for an OLAP system, and complex spreadsheets will get reused a lot, so connection strings may be part of the overall "application" that the document has become.

      I guess so but i figured the document itself would name the data resources it needs and it would be up to the application to actually connect and retrieve the data. I wonder if the document itself can initiate a connection and execute a command. It basically does a "select" to pull data in, can it do a "drop" as well? Seems it wouldn't be hard to put something together that appends a 'drop table' to the document. ..maybe this is the root of all the office macro security issues, i have no idea, these kinds of integrated documents aren't my specialty obviously.

      --
      I came to the datacenter drunk with a fake ID, don't you want to be just like me?
    9. Re:huh? by Simon+(S2) · · Score: 1

      I'd be interested in what is the alternative to storing them in plaintext in the document format.

      We use Kerberos to authenticate the user with the database, and something like Row Level Security or/and Database Roles for authorization on the actual data. That's actually the only secure way I know of (and that I use) to connect to a database from an office document.
      --
      I just don't trust anything that bleeds for five days and doesn't die.
    10. Re:huh? by Simon+(S2) · · Score: 1

      This also violates the (good) Model/View/Controller software architectural model by kludging the view and controller together in the same product.

      No, not really. Think a simple mailmerge with data from the database. There is no Controller, only a model (the DB) and the View (the document). You fetch the data from the database and mailmerge it.
      --
      I just don't trust anything that bleeds for five days and doesn't die.
    11. Re:huh? by Rich0 · · Score: 1

      I think it depends on your needs. If the access is read-only and the data isn't sensitive then the embedded string isn't a problem.

      I'd say that in my experience users actually having accounts on database servers is pretty uncommon. Most applications just connect to the database using an obfuscated password, or they have a business-logic tier that does the data manipulation.

      I agree completely that single-user database accounts are far more secure, but they can be a lot more difficult to maintain and as a result they don't get used much.

    12. Re:huh? by RobBebop · · Score: 2, Interesting

      This also violates the (good) Model/View/Controller software architectural model by kludging the view and controller together in the same product.

      No, not really. Think a simple mailmerge with data from the database. There is no Controller, only a model (the DB) and the View (the document). You fetch the data from the database and mailmerge it.

      Yes, I have read that a compelling reason to stick to Microsoft Office is the ability to Mailmerge, which is fine. I have never gone through the hoops to perform a Mailmerge, so bare with me. My belief is that the whole purpose to send the date (in the database) through the document (which is the controller) to a printer (where it can be viewed). This simple/trivial application actually does separate Data/View/Controller.

      Saying there is no controller is like saying there is no spoon. Just because it is disguised amongst the cruft of a larger, more complicated application doesn't mean it isn't there.

      --
      Support the 30 Hour Work Week!!!
    13. Re:huh? by Simon+(S2) · · Score: 1

      I'd say that in my experience users actually having accounts on database servers is pretty uncommon.

      I agree. Usually users in an enterprice are stored on an LDAP server.

      Most applications just connect to the database using an obfuscated password, or they have a business-logic tier that does the data manipulation.

      That's also true, but in a sane environment you have your users/accounts on an LDAP server and Authenticate them against it (usually with Kerberos tickets).

      ctrl+c ctrl+v from Oracle Security and Identity Management:
      "If your infrastructure is like most, you have an LDAP server that stores your user identities, roles and privileges for the purpose of authenticating your users against their application. The LDAP server also gives you a place to centrally manage your users and the ability to apply a consistent security policy to all of your applications. The LDAP server also gives you the ability to easily delegate administration tasks to others.
      Traditionally, database authentication is done by creating database schema users in the database itself. These schema users have their user identities, passwords, roles and privileges stored in the database. When the user logs into the database either directly using SQLPlus or through some application, the users credentials and privileges are checked inside the database. This model creates fragmented administrative control of users that access their applications. Every database you have creates a new administrative management point and a potential for fragmented administration and security policies in your corporate infrastructure.
      A better model would be to have these users created as "Enterprise Users" in the OID LDAP server. This model allows you to have your users authenticate against the LDAP server and to apply a consistent security policy for all of your users accessing your databases and database applications. It is also an easier way of managing users and their access to applications. This model also limits the number database schema user accounts in the database to just those that are actually administering the database."
      --
      I just don't trust anything that bleeds for five days and doesn't die.
    14. Re:huh? by Anonymous Coward · · Score: 0

      Using VB, VBA, and now .NET, anything the user can do, the code in the worksheet can do. It defaults to not running them in the newer versions of Office, but that can be easily bypassed by the user turning off all the warnings. Create a filesystem object, and start deleting stuff. Create a database object and start screwing with the data. This is fairly useful for a lot of people, but it has lots and lots and lots of drawbacks involving malicious programs and such. At my office, we do road/bridge/building work. The easiest way to keep track of things like rebar/conduit/water pipe/etc in a design is to store it in a database and use excel to import/export the data, calculate quantities, create summaries of quantities and then display them on our drawings.

    15. Re:huh? by Anonymous Coward · · Score: 0

      That would make sense, wouldn't it? A credential vault associated with the application, separate from the document. Otherwise you are mixing database credentials with mobile documents and code on an application platform which is periodically attacked by macro viruses on a global scale.

    16. Re:huh? by AJWM · · Score: 1

      There is no Controller, only a model (the DB) and the View (the document). You fetch the data from the database and mailmerge it.

      Who or what is "you" in this case? That's the Controller. Something has to control which data is selected from the model and how it is viewed. There's always a controller, but sometimes it's horribly intertwined with one or both of the other parts.

      --
      -- Alastair
    17. Re:huh? by Simon+(S2) · · Score: 1

      I think we are really getting philosophical here, but there is no controller. You (the office document) fetch the data from the DB. So, office document = view and DB = model. There is no controller. The definition of controller I have is: "Processes and responds to events, typically user actions, and may invoke changes on the model." - The office document does not do that. It only displays the data.

      --
      I just don't trust anything that bleeds for five days and doesn't die.
    18. Re:huh? by dkf · · Score: 1

      I think we are really getting philosophical here, but there is no controller. You (the office document) fetch the data from the DB. So, office document = view and DB = model. There is no controller. The definition of controller I have is: "Processes and responds to events, typically user actions, and may invoke changes on the model." - The office document does not do that. It only displays the data. I disagree. There's a Controller. It's the trivial default one implemented by the viewing application. (Of course, it only really gets interesting when you start pushing changes in the document back at the database; that's when you start to build a controller of substance...)
      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    19. Re:huh? by colinrichardday · · Score: 1

      No, thank you. I prefer to have certain files be marked as nonexecutable. I just sleep better that way.

    20. Re:huh? by Tony · · Score: 1

      This also brings up two other problems with the practice of document-applications: islands of data, and programming errors.

      I have seen more programming errors in spreadsheets being used a database management systems than in any other code. And I don't know how many times I've seen the exact same analysis being done by two different secretaries (in the same office!) using spreadsheets they wrote themselves. Each of them. Separately. "Oh, it only took me a couple of weeks."

      I think calling it the "big-boys world" is right. They're definitely big boys. The kind with pull-up diapers rather than the tape-on kind.

      --
      Microsoft is to software what Budweiser is to beer.
    21. Re:huh? by Anonymous Coward · · Score: 0

      You're mistaking the business need for the technical solution. Just because you need to do something, it doesn't mean there's only one way to do it. Embedded passwords are BAD.

    22. Re:huh? by Hillgiant · · Score: 1

      Viruses. Malware. Botnets. Whathaveyou.

      --
      -
    23. Re:huh? by Shados · · Score: 1

      WTF does MVC have to do with it? There are douzans of UI design patterns. MVC Type 2 (the one you're thinking of) is a popular one, especially because of the like of Struts and Rails, but the vast majority of (even well designed) apps don't follow it... There's so many other good ones. MVC Type 2 is just a freagin design pattern, and a semi-obsolete one at that (that people follow semi-blindly because its been around for so long), its not the holy grail of software architecture model (its not even one!)

      That being said, in the case I was presenting, they would only be a view, since all they do is send events to the backend, which will act as the controller (the server) and the model (the OLAP).

      Office document applications are an integral and essential part of a complete enterprise application, and aren't any harder to maintain or develop than any other kind of integration. And i'm talking about when its done the real way, not the "lets make a spreadsheet to save 5 minutes" deal. (As a note, usually you can select if the password is in the document or not...it ALLOWS it for convenience, usually with development...but when I access our Sharepoint/Team foundation server documents that need the database, I get asked for the password, and its sent over a trusted connection, not clear).

    24. Re:huh? by aproposofwhat · · Score: 1

      I'm not just any controller, I'm the Fat Controller, you insensitive clod!

      --
      One swallow does not a fellatrix make
    25. Re:huh? by marcosdumay · · Score: 1

      In other words, some big boys dislike creating requirements, and so, waste companies' money writing badly designed software by themselves instead of working on what they were hired to do.

      On the good side, they are rarer than Dilbert would let one think.

  6. Re:Whatever by Anonymous Coward · · Score: 0

    I doubt it - the poster repeated "blah" only one time.

  7. Plaintext passwords by Anonymous Coward · · Score: 0

    They're stored in plaintext.

    So what?

    http://developer.pidgin.im/wiki/PlainTextPasswords

    The fact that it's plaintext is meaningless. If the computer is encrypting them and can decrypt them for use, they're as good as plaintext anyway.

    There isn't even security through obscurity. Seriously.

  8. Re:Whatever by deepershade · · Score: 1

    Does the poster have a chair?

  9. Re:Small bias? by Anonymous Coward · · Score: 2, Insightful

    A 100% ad hominem attack on Slashdot gets modded up unquestioned. Who would have thought?

  10. enough is enough by BroadbandBradley · · Score: 4, Interesting

    how long will it take people to shrug off this death grip of MS and realize that it's costing billions in productivity? I received an XLS file of contacts yesterday and I figured I'd try using Outlook to import it into an address book so I could then sync to other things like Gmail. Outlook choked and recommended assigning values to the columns using another MS product - MS Excel. SO, I saved the file as CSV, and imported using Thunderbird which gave me an easy dialog to match up name,email, phone, website..and so on. Worked great! then I used thunderbird to open the second file and it remembered the previous adjustments and everything was already lined up! Awesome stuff and I wasn't prompted to buy any other products!

    I'm seriously considering wiping all the PC's in my office and advising the staff to just learn Ubuntu to avoid this whole MS deathgrip. None of the staff are advanced users except my web guy who codes in a text editor anyhow. FMS.

  11. Re:Small bias? by pembo13 · · Score: 2, Funny

    Sucks that you can't read the article and assess the level of the bias he displays for yourself.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  12. Re:Small bias? by cyxs · · Score: 5, Insightful

    Everyone has a bias but if he gives you the information that he used to form his opinion about something then you can read what he says and what he did and form your own opinions. He is giving detailed examples of what he found. He isn't just say "Everything is fine" or "They have WMD", he is giving how he comes to his opinion and showing you the facts.

    Yes his company maybe bias in not wanting the format approved, but does that make what he says less true? The facts speak the truth.

  13. Re:Small bias? by misleb · · Score: 1

    Just because there's no love between MS and IBM as corporations doesn't mean that an IBM employee can't do an unbiased assessment. Also, it isn't like IBM is trying to compete directly with OOXML or something. So what's the basis for this suggestion of bias?

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  14. What's the point? Who is going to follow this? by pembo13 · · Score: 3, Insightful

    As I understand it, Microsoft isn't going to follow this standard. If Microsoft isn't going to follow this standard, then it is useless for OpenOffice, NeoOffice, KOffice, etc. to follow this standard. Or is this going to be for Office 2k10 or something?

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    1. Re:What's the point? Who is going to follow this? by MLCT · · Score: 4, Insightful

      MS doesn't care about anyone following it (since even they themselves aren't going to). All they are doing it for is so they can claim that MS Office uses an open ISO standard, OOXML (even though it won't use the ISO passed standard) so that governments, businesses and buyers are not scared away from their products.

      As with everything MS does it is all about control and money. They have observed the fights that took/are taking place at various governmental and state levels over the mandatory use of an open standard - and they see that it is a threat to their monopoly, hence they have strategised to nullify the problem without giving up any of their control. The whole thing is a rate 10 sham. And if anyone ever wants to know why a lot of people don't trust MS then this is a perfect example of it - the process and the mockery they are making of it is frankly satirical.

    2. Re:What's the point? Who is going to follow this? by Anonymous Coward · · Score: 0

      I still don't get it. Right now, MS doesn't support an ISO certified standard, and they are trying to get an ISO certificate for OOXML. If they manage to do that, since they don't support OOXML nor plan to, they still won't support any ISO certified standard. So, what's the point? They can as easily claim "hey, we support ODF, and it's ISO certified" while twiddling their thumbs.

    3. Re:What's the point? Who is going to follow this? by johannesg · · Score: 3, Interesting

      You are absolutely spot on, and what's worse, we can also confidently predict the next step: governments and organisations will be falling over themselves to proclaim their support for OOXML, since it is "an ISO standard". Then they will happily sign their soul over to Microsoft because they have a product that implements this standard, while at the same time disallowing OpenOffice and other office packets because they are not fully compatible with MS Office.

      Then we will tell them that Microsoft is actually not implementing their own damn standard correctly, and we will be laughed away - after all, Microsoft *IS* the standard, so how could it be incorrect?

      And it will all be business as usual...

      The whole thing makes me intensely sad. By the way, we had some articles about the Dutch government requiring open formats a while ago. I professed severe scepticism at the time. Let me give you a little update on that one, then: as it is, the new desktops are required to support a very wide range of technologies that can ONLY be fullfilled by having MS Office on MS Windows. So although the government requires open standards, it also requires Active Directory, for example. And guess what they are buying? Yes, that's right: MS Office on MS Windows. But, we are told, in the next round (in 2011 or so), there will definitely be an opportunity for Linux "because in this round we are already ensuring compatibility".

      As I said, business as usual.

    4. Re:What's the point? Who is going to follow this? by harlows_monkeys · · Score: 1

      As I understand it, Microsoft isn't going to follow this standard

      They've explicitly committed to supporting it in whatever form it is in if/when ISO approves it.

    5. Re:What's the point? Who is going to follow this? by tsa · · Score: 1

      I heard somewhere Apple is working on an implementation of OOXML for their office suite.

      --

      -- Cheers!

  15. Re:test by Anonymous Coward · · Score: 0, Funny

    failed

  16. Re:Small bias? by Mongoose+Disciple · · Score: 0

    Sucks that you can't read the article and assess the level of the bias he displays for yourself.

    I did. He's not shy about his hatred and utter contempt for OOXML and all things Microsoft.

    Which, fine, he's entitled to his opinion, but I'm not dumb enough to think that his pseudo-scientific Nth post about why OOXML is trash is less biased than the (N-1)th post.

  17. Re:Small bias? by Mongoose+Disciple · · Score: 1, Offtopic

    So what's the basis for this suggestion of bias?

    Spend five minutes looking at the article and the page it's on. To his credit, it's not something he tries to hide.

    Exhibit A: a link in his sidebar to an article which refers to OOXML as "the document format from Hell."

  18. So he wants security through obscurity... by Rakishi · · Score: 2, Insightful

    Even so, he's found a number of new flaws, including a security vulnerability: OOXML stores passwords in database connection strings in plain text. And how will the format magically produce the plain text password again when the database asks for it... oh wait it can't unless it's easily recoverable in plain text form. It's also not like the "encryption" mechanism would be documented and it's not like someone would have to read that very documentation to know even where the password is stored... oh wait.

    Anyone who claims that it's more secure to obscure the password in a well known and trivially reversible way instead of simply storing it in plain text is not someone I trust to analyze security.
    1. Re:So he wants security through obscurity... by tigre · · Score: 1

      The one thing it does help prevent is accidental disclosure of passwords. If the contents of the file are exposed, but not the key to unobfuscating the contents, then there is a significant security benefit.

    2. Re:So he wants security through obscurity... by Anonymous Coward · · Score: 0

      And how will the format magically produce the plain text password again when the database asks for it... It could prompt for another password that could be used to decrypt the database password or the entire connection string. Not providing an option to do so is a clear flaw in the format.
    3. Re:So he wants security through obscurity... by Mista2 · · Score: 1

      If you don't want to use password for authentication, then you'd need to support certificates, but I don't think ODBC in windows can do this, so I guess it's not in MS's format. Certificates could also be minted and added to the document and then used to encrypt the password using PGP or similar, but MS continues down the x.400 certificate route meaning getting signed certs is expensive, or you have to set up a PKI infrastructure. Makes it harder. Nothing about adding security is simple or without complexity 8) Hell MS managed to encrypt WMA, and all the HD video content in memory, and then use tilt-bits to detect tampering in video drivers, but I guess it would be too much to ask for them to protect my data as well as Hollywoods.

    4. Re:So he wants security through obscurity... by BlueParrot · · Score: 1

      Here's the encrypted key to one of my documents. It is stored in the document itself:

      $2$gJT/A1qk$CyM4Z4UleBaoMyruOx9Ku

      Now you may start to guess what pass phrase to use to recover the plain text. Have fun...

    5. Re:So he wants security through obscurity... by Anonymous Coward · · Score: 0

      Remember that the password needs to be used to connect to a database, so the format needs a way to decrypt it to its original form. Given that, the standard must define a way to restore the pass phrase. Since the format is open, we can have access to that algorithm.

      So, provide us with the algorithm, and we'll guess your pass phrase in no time.

    6. Re:So he wants security through obscurity... by Dutch+Gun · · Score: 1

      If an "encrypted" key is stored in the document, then the format itself must be reversed by the local bits on the machine using a standardized algorithm, correct? Otherwise, the document isn't interoperable. So, you've just given out your password, with the only difference being that now it probably takes someone more work to uncover the passphrase. Worse, users are likely under the impression that the key is actually secure.

      Oh, and your passphrase is:

      $2$gJT/A1qk$CyM4Z4UleBaoMyruOx9Ku
      I don't understand security stuff

      --
      Irony: Agile development has too much intertia to be abandoned now.
    7. Re:So he wants security through obscurity... by 10101001+10101001 · · Score: 1

      I think you're missing the author's point. Generally speaking, it is always a bad idea to store a plain text password in a file. Further, any time that it *is* done, special security precautions should take place to insure that those passwords aren't leaked to people who shouldn't have access to them. Now, if the document format absolutely needs access to the plain text passwords (something I doubt), there's at least two major options available.

      Option one is to encrypt the whole document, requiring a user provided password to the file. There are various problems with option one. The biggest of which is, simply encrypting the file doesn't resolve the issue of possibly leaking passwords. After all, I might edit a file 20 times, and over the course of 20 edits, I might end up adding some database sources, deleting some, and adding others. Without clarification in the format on the proper security procedure (like, whether it's okay to, say, cache user credentials for further edits), it's quite possible that as a user I might believe I can give a document to someone with the required password and since all sensitive databases are no longer used, no sensitive user credentials are contained within.

      Option two is to merely include a very long list of security procedures to take care of such eventualities. That means including requirements such as notifying the user when passwords are stored, notifying the user of *all* passwords that are stored, and allowing the user to completely remove passwords in some specification allowable fashion (it sounds like the format might require the password and not including them would be undefined behavior...but removing the whole database reference is probably undesirable, so what's the "standard" thing to do?).

      Now, the only real argument that can be made is that OOXML was written with the security consideration that documents that contain such information would never be released to people who don't already have access to said information. Of course, that's a bullshit argument, since ISO document standards are precisely designed for the distribution of information between entities who shouldn't be sharing such information. So, not taking such security considerations is a security vulnerability. And unless it's fixed, it means that anyone who cares about security should avoid OOXML.

      --
      Eurohacker European paranoia, gun rights, and h
    8. Re:So he wants security through obscurity... by mattpalmer1086 · · Score: 1

      Nice straw man. Of course, if a password was simply "obscured" in a "well known and trivially reversible way", then yes, gosh, that wouldn't provide any protection at all.

      But Rob Weir didn't make that claim. He just pointed out that plain text passwords were being stored in the document format, and that this is a security risk - which it is. It may be fine in some circumstances - but in all the other ones, where it isn't fine, there is no other mechanism provided by the standard.

      Now, if a password were to be encrypted *properly*, then it wouldn't be trivially reversible, without knowing the secret key. Of course, now you have to deal with how to get the secret key - but again, there is no mechanism defined in the standard to do such thing or to allow such a method to be defined. So you are left with plain text passwords, or nothing.

      Oh, finally, security people don't think that an encryption algorithm being "well known" is any kind of weakness. This is known as the Dolev-Yao threat model, where all security depends on the secrecy of the key, and nothing else.

    9. Re:So he wants security through obscurity... by Anonymous Coward · · Score: 0

      you don't need to use security through obscurity.

      in a good standard (which MS-OOXML is not), there would be a master password in the user's head (probably typed when loading the document and cached during the office suite's execution), or a private key in your smartcard, which would decrypt all the properly encrypted database passwords in the MS-OOXML document you are using at the moment. voila: no need to store plaintext passwords, or to obscure them.

      guess I should send the 5-second security design bill to MS? oh, why bother, they don't care.
      the bad standard of using security through obscurity is typical of Microsoft's products.

    10. Re:So he wants security through obscurity... by mysticgoat · · Score: 1

      Putting the password in the document file in any form is the problem.

      A car analogy is obviously called for. The OOXML standard describes a method for taping your car keys to the driver's side window where your co-worker can easily find them when he wants to take your car for a spin.

      There are secure methods of managing passwords, especially in an "Office Suite" environment, but none of these are in MS' bag of tricks.

    11. Re:So he wants security through obscurity... by Anonymous Coward · · Score: 0

      "Insightful"? Rubbish. I call "Blatant strawman".

      Weir simply points to the storing of a so-called "password" in open text, and states that "the lack of any security mechanism on this feature is alarming". He doesn't remotely suggest what such a security mechanism should be, he merely (and indisputably) points out that the absence of one is a massive flaw. The fact that the parent can't come up with a credible mechanism, and attacks Weir on that basis, says considerably more about the parent's ego than it does about Weir's analysis.

    12. Re:So he wants security through obscurity... by Anonymous Coward · · Score: 0

      A better question might be, "what is a password doing in such a document in the first place"?

  19. Re:Small bias? by misleb · · Score: 2, Informative

    Man, I'm really getting sick and tired of people abusing the "ad hominem" charge. Ad hom refers specifically to an attack on ones character which is used to discredit an argument. Simply questioning a persons motives and biases is not necessarily an ad hominem attack. It is important to make any potential biases clear. Though in this particular case, I'm not seeing it.

    Also, attacks on ones character may not be considered "ad hominem" unless it is being use to refute an argument. This is probably the most common misuse of the term. For example, I can call someone an asshole and it wouldn't necessarily be an "ad hominem" attack. It might just mean I think the person is an asshole. It is a valid opinion. It just isn't relevant to any logical argument.

    -matthew

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  20. Re:Small bias? by oGMo · · Score: 3, Insightful

    He might well be right, but I'd be more inclined to believe it from someone who doesn't have a corporate interest in picking data points to fit the line he would like to draw.

    So you won't verify anything, or even check, but rather you feel that the exact same thing from someone else would be more true. Essentially, despite the facts, you don't feel the truthiness is sufficient.

    By your logic, you may well be right, but you may also just be a shill for Microsoft. I'd be more inclined to believe someone else who didn't have a corporate interesting in picking data points to disparage the argument you'd like to make. Or maybe if you had an argument to make not based on a well-known informal fallacy.

    --

    Don't think of it as a flame---it's more like an argument that does 3d6 fire damage

  21. no kidding, that would make things worse by r00t · · Score: 1

    It adds complexity, which is generally bad for security, and makes the format harder to understand, which is also bad.

    The word that comes to mind is "dumbass".

    I do hope there is an option to have an "ask the user" password. (not stored in file)

  22. Implement first, standardize later. by colmore · · Score: 2, Insightful

    Did we learn nothing from the 80s and early 90s? If you write the standard first, you're going to get the kitchen sink. Engineer a good system, then standardize it. Nothing sands the sharp edges like the real world.

    --
    In Capitalist America, bank robs you!
    1. Re:Implement first, standardize later. by WWWWolf · · Score: 1

      Did we learn nothing from the 80s and early 90s? If you write the standard first, you're going to get the kitchen sink. Engineer a good system, then standardize it. Nothing sands the sharp edges like the real world.

      No, we learnt from 80s and 90s that if you engineer a system and then standardize it, you get a crappy system - your bugs become everyone's features.

      If you engineer a good system, learn from the experience, then write a standard that allows for room for growth, and then make your system compliant with the standard, you get a great standard. If you do this process again n times, you'll be on even stronger ground. We learned that standards aren't perfect and need to be refined; yet, at the same time, compliance with existing standards is important.

      (...said he, and posted this over Internet Protocol v4 and Hypertext Transfer Protocol v1.1...)

      OpenDocument folks did it right: Start from OpenOffice.org standard, think how to make it better in real world, then standardize it and let OpenOffice.org folks fix their implementation - and the OOo folks did that. With OOXML, Microsoft is just saying "no, perhaps it's not perfect, but you will implement this, all quirks and undocumented sides included, because we aren't touching our perfect implementation. Either that, or you don't implement it at all."

  23. Re:Whatever by el+cisne · · Score: 4, Funny

    "Does the poster have a chair?"

    Not any more.....

  24. Um, this is a perfect example of "ad hominem"... by Joce640k · · Score: 1

    Did the poster say something like, e.g.:

    "Rob Weir made the following mistakes in his methodology:
    a) ...
    b) ...
    c) ... ...
    "

    Nope. He based his 'argument' on his perception of Rob Weir.

    --
    No sig today...
  25. MSOOXML is not standard quality by Anonymous Coward · · Score: 2, Insightful

    During the BRM is has been shown that MSOOXML is not up to the quality for an international standard.

    The only reason that this thing is considered in ISO is because Microsoft is being so bullish, trying to defend the monopoly.

  26. Standards are not religons by surfingmarmot · · Score: 3, Insightful

    Yet a lot of people treat them that way like this Slash Dot commenter: "He might well be right, but I'd be more inclined to believe it from someone who doesn't have a corporate interest in picking data points to fit the line he would like to draw." Just why is that rated a 5? It is NOT about belief, but more about science--either the facts and peer review support Mr. Weir or they don't. Apparently they do and in Spades. The majority of "yes" votes on this "standard" are by Microsoft partners who have a vested interest in a dingle vendor, single application (the only full implementation read and write) solution they sell products and services for and can lock in business. Sure IBM is a commercial organization with a checkered past, but they don't own completely open ODF so they aren't doing this for gain. they jsut want a level playing field for formats. And it is a great idea.

  27. Not how should it be done, but why it shouldn't be by g2devi · · Score: 1

    I think you're missing something important. The document format should not store this information at all -- it's the job of the keyring password manager. The document may define an alias for the database connection string, but it shouldn't provide the actual connection details since that would be a security hole.

    Look at it from another angle. Imagine that I need to connect to the database using the connection string, a@mycompany.com:mypass. I send you the document, but you're on another network. You don't see my database, but you do see a proxy database that maps to my database, so the proper connection string would be: b@proxyserver:mypass2. If we send each other the document, we'll be in an edit war. Every time you get the document, you'll want to change it to your password and every time I get it, I'll change it to mine. If however, we leave it up to the keyring manager, there's no problem.

  28. Re:Um, this is a perfect example of "ad hominem".. by misleb · · Score: 1

    Nope. He based his 'argument' on his perception of Rob Weir.


    He was simply pointing out a potential source of bias. I didn't even really see an argument either. Just an expressed opinion about how much the OP trust the author.

    There are much better examples of ad hominem attacks. For example, if the OP had said "Rob Weir is an asshole and can't possibly be right". THAT would be a perfect example of ad hominem

    -matthew

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  29. Re:Small bias? by Anonymous Coward · · Score: 0

    Can you read?

    "He might well be right, but I'd be more inclined to believe it from someone who doesn't have a corporate interest in picking data points to fit the line he would like to draw."

    translated ,

    "His argument may be valid, but I am doubting it because of who he is."

  30. Re:Small bias? by dedazo · · Score: 1

    I am doubting it because of who he is

    No, he is doubting it because of what he is.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  31. ISO 8859 by jbeaupre · · Score: 1

    Heck, isn't just about everything stored in ISO 8859? I actually thought it was the same as ASCII until reading this: http://kb.iu.edu/data/ahfr.html.

    There's your ISO right there! Oh, format ... right ...

    --
    The world is made by those who show up for the job.
    1. Re:ISO 8859 by Fred_A · · Score: 1

      Heck, isn't just about everything stored in ISO 8859? I actually thought it was the same as ASCII until reading this: http://kb.iu.edu/data/ahfr.html. FWIW the 8859 section of that page is in bad need of an upgrade (the tables go beyond 8858-8, for example western Europe uses 8859-15 which adds € and completes character tables that were left unfinished in -1)...
      You might want to check Wikipedia which appears to be much more complete (for once).

      --

      May contain traces of nut.
      Made from the freshest electrons.
    2. Re:ISO 8859 by jbeaupre · · Score: 1

      I was surprised enough that what I've always called ASCII ... ain't. Luckily my job doesn't require that much level of knowledge.

      --
      The world is made by those who show up for the job.
  32. And now for some selective quotations! by peacefinder · · Score: 2, Funny

    OOXML's Flaws Have Been Addressed

    "IBM's Rob Weir has done a study on how many flaws were addressed by the OOXML Ballot Resolution Meeting. So far, using a random sampling technique, he has yet to find a flaw [...] there were no mistakes on [...] the [...] pages he reviewed."

    There. Doesn't that sound better? :-)

    --
    With reasonable men I will reason; with humane men I will plead; but to tyrants I will give no quarter. -- William Lloyd
  33. Re:Small bias? by rhizome · · Score: 2, Insightful

    He might well be right, but I'd be more inclined to believe it from someone who doesn't have a corporate interest in picking data points to fit the line he would like to draw.

    Nobody is asking you to "believe" anything. Bias does not change facts, and it is a fallacy to suggest that he should be a perfectly impartial critic if he is to be taken seriously. If he makes observations of deficiencies in the format they are just as valid as if they were made by Bill Gates himself.

    --
    When I was a kid, we only had one Darth.
  34. Re:Um, this is a perfect example of "ad hominem".. by vtscott · · Score: 3, Informative
    No, this is a perfect example of an ad hominem attack... This particular type of ad hominem is an ad hominem circumstantial:

    Ad hominem circumstantial involves pointing out that someone is in circumstances such that he is disposed to take a particular position. Essentially, ad hominem circumstantial constitutes an attack on the bias of a person. The reason that this is fallacious in syllogistic logic is that pointing out that one's opponent is disposed to make a certain argument does not make the argument, from a logical point of view, any less credible; this overlaps with the genetic fallacy (an argument that a claim is incorrect due to its source).

    One example given by wikipedia is:

    Tobacco company representatives should not be believed when they say smoking doesn't seriously affect your health, because they're just defending their own multi-million-dollar financial interests.

    Just replace the relevant references with words like IBM, OOXML, etc. and it's basically the same.

  35. Re:Small bias? by LoyalOpposition · · Score: 2, Informative
    Ad hom refers specifically to an attack on ones character which is used to discredit an argument. Simply questioning a persons motives and biases is not necessarily an ad hominem attack.

    You started to get it right, but then you fell by the wayside. The entire phrase is argumentum ad hominem which means "argument to the man." It includes any attempt to discredit an argument based on characteristics of the person advancing the argument. In the instant case, the argument goes something like--OOXML should be rejected if it's a bad standard. OOXML is a bad standard because it has many shortcomings that haven't been addressed. Therefore OOXML should be rejected. Mongoose Disciple chose not to dispute any of the premisses of the argument or the inference, but rather to claim that Rob Weir stands to gain if the conclusion is accepted. Thus Mongoose Disciple presented us with an excellent example of an argumentum ad hominem.

    Also, attacks on ones character may not be considered "ad hominem" unless it is being use to refute an argument. This is probably the most common misuse of the term. For example, I can call someone an asshole and it wouldn't necessarily be an "ad hominem" attack.

    Completely correct. However, it's irrelevant to the instant argument.

    -Loyal

    --
    I aim to misbehave.
  36. Re:Not how should it be done, but why it shouldn't by jfclavette · · Score: 1

    Not a bad idea but now you need to graft a standard interface to a keyring password manager in the standard. Is it worth it ? Like has been mentionned in other posts, it is very possible to attain more security trough relying on Kerberos or Active Directory for authentication and that's trivially implemented with a custom connection string. My point is merely that I consider it a 'less secure but more practical option for the little guy', not a security vulnerability. It's a viable option when your data's not exactly national secrets.

  37. Double plus bias by dedazo · · Score: 1, Insightful
    Whenever this comes up here I always get a big chuckle because IBM is just doing what it does best (much like Microsoft), except that they've amusingly managed to do it completely out in the open. So while Rob Weir might be nothing more than a shill, he actually admits he's a shill by virtue of being a full-time salaried employee of IBM, a company that just happens to be offering a range of products (including an office suite) that compete with Microsoft Office. Everyone else just puts their fingers in their ears and goes la-la-la-la-la.

    Remember Peter Torr? He wrote a blog post not long after Firefox hit 1.0 where he questioned why the Firefox installer was not digitally signed. What he said was completely true - so true in fact that not long after that Mozilla started signing the installer. That didn't prevent few thousand raving lunatics from descending on his blog and calling him a shill and an idiot. To paraphrase you, yes his company maybe bias in not wanting the [browser to succeed], but does that make what he says less true? The facts speak the truth.

    So essentially we have situations where the source of income and ulterior motives of one person should not be questioned because the topic is unpopular and everybody knows he must be right. On the other hand we have people whose motives *must* be automatically questioned solely because of their source of income and ulterior motives.

    The truth is that Weir should have recused himself from all this a long time ago. That he hasn't done that tells you a lot about him and his employers.

    You might argue that Microsoft had all this coming. You might argue that OOXML is not a good standard. You might argue a lot of things, but none of them make IBM's conduct in all this (including the whole ISO thing) any less dishonest.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  38. Re:Small bias? by setagllib · · Score: 1

    Ah, but can you prove it via induction? :)

    --
    Sam ty sig.
  39. Re:Small bias? by octopus72 · · Score: 1

    If that kind of statement is drawn from a detailed review of the documentation,
    than his "bias" will reflect quality of OOXML format very well.

    If something is garbage, it should be said loud and clear.

  40. Re:Small bias? by setagllib · · Score: 2, Funny

    What's wrong with publicly stating the religious body backing OOXML development? Microsoft is very fortunate to have so much support from Hell. Why, if they had to supply their own evil or go through commercial channels, the global evil reserves would dry up overnight.

    --
    Sam ty sig.
  41. Re:Small bias? by Anonymous Coward · · Score: 0
    See the comment above about "ad hominem".

    For example, I can call someone an asshole and it wouldn't necessarily be an "ad hominem" attack. It might just mean I think the person is an asshole. It is a valid opinion. It just isn't relevant to any logical argument.

    In the same way, his calling OOXML names has no bearing on the logical validity or lack thereof of his arguments.
  42. Re: ad hominem by ozbird · · Score: 2, Interesting

    You mean like the slur made by a Microsoft employee against a Standards New Zealand representative?

  43. Database??? by DoofusOfDeath · · Score: 1

    OOXML stores passwords in database connection strings in plain text.

    Am I the only person who's wondering WTF a database connection string is doing in a word processing document?

    I'm starting to understand why the spec is 6000 pages long.

  44. Re:Um, this is a perfect example of "ad hominem".. by clampolo · · Score: 0

    This is why so many people look down on philosophy: it runs counter to common sense.

    Following this train of logic, when I'm buying a new car I should ignore that the salesman only makes money if he sells me a car. So when he's busy telling me that the 1982 Volkswagon he's trying to sell me could out-accelerate a Porsche, I should just treat it as an impartial opinion

    The poster is completely correct in pointing out that an IBM representative has an inherent bias against a Microsoft standard and it's wrong to label his post as a flame.

  45. Passwords in plain text by bluefoxlucid · · Score: 1

    How the hell would YOU store passwords? With an encrypted text using a fixed key? Or with a randomly generated key stored in the file (key union ciphertext == plaintext)? Or maybe use an NTLMv2 hash that connects ONLY to a proprietary database (MSSQL) with a proprietary setting, which you can happily replay (we call this a secondary password...)? The only solution is to password-lock the file and use the password to encrypt a master key that encrypts A) the whole file; or B) a master password list embedded in the file. Neither of these will satisfy point-and-click easy access requirements; and if you implement (B) the password becomes common knowledge among many individuals (bad).

    1. Re:Passwords in plain text by SCHecklerX · · Score: 1

      If the doc requires a connection to a database, surely requiring a connection to a standard authentication mechanism (kind of like how firefox does it if you assign a master password for your stored passwords). Yes, a PITA, and maybe silly, but no more so than allowing a word processor document to connect to a database in the first place.

    2. Re:Passwords in plain text by bluefoxlucid · · Score: 1

      Yes, but then the auth mechanism would require all kinds of things, an encryption key for each user, etc.. it's a hard problem.

    3. Re:Passwords in plain text by seandiggity · · Score: 1

      You can change your sig now; that Firefox plushie is back: http://store.mozilla.org/product.php?code=14%2093119&catid=search

      --
      Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
    4. Re:Passwords in plain text by Anonymous Coward · · Score: 0

      Sorted.

      Your problem?

  46. He is not involved in GNOME anymore by Anonymous Coward · · Score: 0

    see title.

  47. Re:Small bias? by Mongoose+Disciple · · Score: 0

    I sure wish "Overrated" mods had to face meta-moderation. It's not "-1, Disagree", and I'm not posting anything that isn't completely obvious to anyone who RTFA.

    Cowardice around here isn't always limited to posting anonymously, I guess.

  48. Financial blogs getting heavily shilled by Anonymous Coward · · Score: 0

    Take a few minutes off of Slashdotting to look here. IMHO, Dennis Byron is a one-man Microsoft promotion machine, specializing in OOXML. He sometimes writes on the same blog as "Research 2.0", going so far as occasional visits to the make-believe world of SCO.

  49. OOXML approved by NIST by seandiggity · · Score: 3, Informative

    Even though none of the substantial problems have been addressed, NIST has approved OOXML.

    --
    Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
    1. Re:OOXML approved by NIST by Anonymous Coward · · Score: 0

      The NIST approval sounds like someone has been paid off or is just not paying attention to the issues.

  50. Re:Small bias? by Anonymous Coward · · Score: 1, Insightful

    The article says that the data was randomly selected, right? So if you want to suggest selection bias, a first step would be to show that the page umbers were indeed not random.

  51. No he doesn't! by Xenographic · · Score: 1

    You're putting words in his mouth. He never recommended obfuscation as a "fix" for this issue, now did he? That was YOUR idea.

    Personally, I would require the user to supply the password, or else I would create something where the document was signed cryptographically and presented itself to the database for authentication. I'm sure there are other, better ways of doing this than just "who cares? store it in plain text because we're lazy and don't care!"

    1. Re:No he doesn't! by Rakishi · · Score: 1

      None of your "solutions" preserve the functionality that the current proposal has. One requires not only user input but the need to send this second password to the user, in some cases not a trivial possibility. The second requires a special database setup and won't work in the majority of cases. Sure other methods can also be included but those are new features and the plain text one will still be left there.

    2. Re:No he doesn't! by colinrichardday · · Score: 1

      And this "functionality" a good idea?

  52. Re:Small bias? by Anonymous Coward · · Score: 0

    Everything has deficiencies. You present the deficiencies and ignore all positive points and now your factual analysis is worthless because it doesn't lead to any reasonable conclusion.

  53. Re:Um, this is a perfect example of "ad hominem".. by Omestes · · Score: 1

    I wouldn't blame this one on the discipline of philosophy, as it is an informal fallacy. I would put this more into the area of rhetoric.

    I do see the point though, since just claiming potential bias is not enough to discredit a source. A potentially biased, or vested, individual can tell the truth as well. To turn your analogy around; a Porsche dealer tells you that this new Porsche is faster than you '68 Bug.

    That said, I don't think the g-g-parent was off the mark, nor guilty of committing this informal fallacy. Pointing out potential bias isn't the same as discrediting someone for the same potential bias. The contested statement basically said "we should pay a wee more attention than we would, because IBM has a history of collaborating with Microsoft", this is not discrediting IBM, but just warranting caution in accord with inductive reasoning (it has been often previously observed that).

    --
    A patriot must always be ready to defend his country against his government. -edward abbey
  54. Re:Small bias? by Anonymous Coward · · Score: 0

    Your post, in lolcat form:
    "lol biased man is biased" (insert kitteh picture here)

    Why on earth would you think you *deserve* to be highly rated for your post? If it's completely obvious, it's (-1, Redundant). Also, it's a tangent that ignores the facts of the matter, thus (-1, Offtopic). Not to mention, you seem to be taking Microsoft's side, which would be (-1, Flamebait). The only appropriate mod that addresses all the problems with the post you graced us all with is (-1, Overrated).

  55. Re:Um, this is a perfect example of "ad hominem".. by Skrapion · · Score: 2, Interesting

    Here's the difference, though. You're assuming the OP said:

    "Rob Weir can't be trusted because it's in his best interest for OOXML to fail."

    But the spirit of what the OP said was actually closer to this:

    "I don't trust Rob Weir, because it's in his best interest for OOXML to fail."

    It's actually a pretty big difference. The first statement is a logical fallacy, but the second one is just explaining his personal bias. And keep in mind that the OP specifically stated that Rob Weir "might well be right".

    --
    The details are trivial and useless; The reasons, as always, purely human ones.
  56. Compare against 'How to Write Unmaintainable Code' by Anonymous Coward · · Score: 0
    Never mind other ISO standards, just compare the flaws listed against How to Write Unmaintainable Code!

    [Main page] http://mindprod.com/jgloss/unmain.html

    I'd only got as far as item 3 on Rob Weir's list, "... The allowed values of this type express the measurement units to be used: Auto, Twentieths of a point, Nil (no width), Fiftieths of a percent. I find these choices to be capricious and not based on any sound engineering principle..." and from the HowTo, in the section on Coding Obfuscation, item 6: "Foolish Consistency Is the Hobgoblin of Little Minds When you need a character constant, use many different formats: ' ', 32, 0x20, 040..."

    Is this resemblance coincidence? I doubt it.

    [Coding Obfuscation section] http://mindprod.com/jgloss/unmainobfuscation.html

  57. Mod parent up by shrikel · · Score: 2, Insightful
    I find it unfortunate that so much of public debate today has degenerated into a knee-jerk contest. "Oh, that guy works for X company, so he cannot possibly have a good point." When did people decide that thoughtful analysis of articulate, well-composed arguments is unnecessary to reaching a good understanding? Who can better speak out for a product/idea/standard/whatever than those who are most passionate about its qualities (i.e. its developers, backers, etc)? Who can better point out its flaws than those who are most motivated to FIND and EXPOSE those flaws?

    Arguments should be accepted based on their validity and their accuracy. What if Einstein (or any other scientist, for that matter) were not allowed to defend his own theories?

    --
    Any sufficiently simple magic can be passed off as mere advanced technology.
  58. Re:Um, this is a perfect example of "ad hominem".. by Anonymous Coward · · Score: 0

    Yeah, except that's Wikipedia and I just wrote that entire thing myself on a guess...

    or did I? Do you really know?

  59. Who else? by Tony · · Score: 5, Insightful

    Riiight. We should have one of the few people willing and able to examine the standard for flaws just not do it. That's an excellent idea.

    At what point has IBM been dishonest? Rob Weir is an employee of IBM. They have a distinct interest in making sure that whatever format is approved, they are able to implement it. Therefore, it is in their best interest to make sure it is a good standard. As they have determined that it isn't a good standard, what should they do? Not talk about it?

    The fact that his bias is out in the open is perfectly fine, as is the example you give from Peter Torr. That allows people to judge their statements, and account for possible bias.

    The problem with Weir recusing himself is this: nobody else seems to be doing this. Nobody else is standing up to a corrupted process, where the intended and stated results are sidelined for political expediency. If it takes one corrupt company to stand up to another corrupt company, then so be it. At least they are standing up to a corrupt company. (Yes, I'd prefer if neither were corrupt.)

    --
    Microsoft is to software what Budweiser is to beer.
  60. There are a number of problems with this post by Trestop · · Score: 2, Informative

    As well as with the original article. First thing - you can't really say "few flaws have been fixed" when the original article (and the post blurb) specifically say that no fixed flaws where actually found in the testing sample.

    On the other hand, the statistics used by Rob Weir are shoddy according to my local statistics semi-expert (my girlfriend who finished 2nd year BA stats A. with a perfect 100 score). Specifically his sample is incredibly small: 25 random pages out of a random selection of 200 pages out of 5220 pages of the original standard document, out of 6045 pages actually in the original document (not the amended document), of which he doesn't know how many defects where actually reported against each page (we know how many were reported totally, but we don't know what is their percentage in the first sampling or subsequent sampling), and as Rob Weir found new defects that were not reported to Microsoft in time for the BRM, he has no idea what is the actual density of (pre-BRM) reported defects in the total "defect population" (defects discovered before BRM, after BRM and defects that are yet undiscovered).

    As such a confidence interval of 1.5% +-3% (i.e. at worst 4.5%, which is not what the post reports) seems highly suspect. To clarify for non-statistics students, a confidence interval of 1.5% +-3% in a result of 0 hits out of a random sample, means that Rob Weir is at worst 95.5% confident and at best 100% confident that there were no defects addressed by Microsoft.

    This is awfully presumptuous, even if its Microsoft that we are talking about.

    1. Re:There are a number of problems with this post by marcosdumay · · Score: 1

      "To clarify for non-statistics students, a confidence interval of 1.5% +-3% in a result of 0 hits out of a random sample, means that Rob Weir is at worst 95.5% confident and at best 100% confident that there were no defects addressed by Microsoft."

      To clarify for staticians wannabe (altough I'm not one statician either, but I at least FINISHED the basic statistics course), a confidence value can only have some meaning toghether with an error margin.

      What he is saying is that he is 95.5% confident (at worst) that the corrected flaws are betwwen 0 and N, where the value of N was lost during the report.

      Alternatively, he is saying that he is 98.5% confident that less than 3% of the flaws were corrected, and, altough the words of that setence were displaced during the report, the numbers are still the same.

  61. What I really look forward to... by patiodragon · · Score: 1

    when I drop by Slashdot is, if I'm lucky, people will have a good argument *about* arguing. What the hell was this post about anyway? I can't remember.

    It says, "Post Comment", not "Bicker Indefinitely".

  62. I hope y'all are gentle with them... by argent · · Score: 2, Funny

    Considering they provide the email address and phone number of their media contact in that announcement.

  63. Czech Republic's expert disagrees wholeheartedly by I'm+Don+Giovanni · · Score: 0
    Sorry, but this is bullshit, as is to be expected from Rob Weir.
    Jií Kosek, the Czech Republic's expert, disagrees. He has switched from NO to YES due to OOXML's fixes, and he's unbiased (quite unlike Rob Weir). Here's what he has to say on the matter:
    http://xmlguru.cz/2008/01/ecma-response-to-czech-ooxml-comments

    Read that post and you see that nearly every one of the Czech Republic's objections has been addressed (the only one not satisfactorily addressed was the Czech Republic's complaint that part of the spec has redundant info). Let me quote:

    ECMA already provided proposed resolution for 75 comments (out of total 75 Czech comments). This means that 100.00% of Czech comments were handled by ECMA.

    90.67% of comments were satisfactory resolved.

    8.00% of comments were resolved only partially.

    1.33% of comments were not satisfactory resolved. ... ...
    In fact I was really surprised how many "green boxes" are there at the end. I was expecting that ECMA will properly address only part of our comments. The vast majority of Czech comments was addressed by ECMA so it is time to say yes to OOXML.

    Rob Weir is not an objective source, period. Cite an objective source if you want your criticisms to carry any weight outside of the "I Hate Microsoft" crowd.
    --
    -- "I never gave these stories much credence." - HAL 9000
  64. Re: ad hominem by holloway · · Score: 2, Informative

    Hi ozbird, I'm not a Standards NZ representative. I am part of the NZ Open Source Society (NZOSS) and a techy on Docvert. I am part of the advisory group formed by Standards NZ for this process but like all others in the group I'm not paid and I'm basically an independent who gets invited to meetings every so often to debate OOXML, and stuff like that.

  65. Re: ad hominem by mav[LAG] · · Score: 1

    Hey Matthew - care to name the Microsoft employee who slandered you? Grant Thomas's reply just says
    To: [name]@microsoft.com

    --
    --- Hot Shot City is particularly good.
  66. Re:Czech Republic's expert disagrees wholeheartedl by fbjon · · Score: 1
    OK. If you would now please explain to everyone how 75 comments from the Czech delegation is representative of the total of thousands of defects in the proposed "standard".


    Stop twisting reality so much, it makes my head hurt.

    --
    True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
  67. Re:Um, this is a perfect example of "ad hominem".. by Anonymous Coward · · Score: 0

    Just replace the relevant references with words like IBM, OOXML, etc. and it's basically the same. I would think in this case IBM would be an alcohol seller saying tobacco can and will damage your health.

    Or IBM is another tobacco company saying MS tobacco is bad for your health, but not the already accepted IBM tobacco.
  68. Re: ad hominem by holloway · · Score: 1

    Heh, well the short answer is "no".

    The long answer is that if I post the contact then it will get out of my control and it's likely that the Microsoft person could get disgusting or threatening emails which, quite honestly, I don't want. As much as I find this Microsoft persons' behaviour as quite repugnant I'm going via the official channels. If I get a satisfactory result via that then I'll be happy. As of yet however I have not received anything that would constitute a sincere apology.

    In the meantime, I'm asking everyone this favour, I'm the guy involved in this and these are my wishes (feel free to email me on anything at holloway.co.nz if anyone doesn't think that this account is me): please don't hunt this Microsoft person down. I'm on-top of this one, I assure you. I won't let this behaviour go without a response and if I don't get a satisfactory result here I am considering forwarding these details to the European Commission investigations into OOXML (if they don't already know).

  69. Re: ad hominem by mav[LAG] · · Score: 1

    Fair enough. I'm sure we'll be kept abreast of progress by Groklaw and the like.

    Oh yeah, and thanks for Docvert :)

    --
    --- Hot Shot City is particularly good.
  70. Personalized database accounts. by splutty · · Score: 1

    You're missing the point, really..

    There should be *NO* passwords in documents. Period. What you should do is make personalized user accounts in the database for all users that actually require access to this data, then have that username automatically filled in from the logged on user, then prompt the user to type in their own password.

    This provides a solid authentication model, will deny all users who have nothing to do with this data to access it, and will also create a personal audit trail.

    ps. This is my 256th post! Weeh! :)

    --
    Coz eternity my friend, is a long *ing time.
  71. Re:Small bias? by walterbyrd · · Score: 1

    As to the anti-OOXML side, I would recommend you look at: http://www.noooxml.org/ this site does an excellent job at detailing numerous flaws in the OOXML standard, and numerous irregularities in the ISO OOXML acceptance process.

    But it is only fair to understand Microsoft's point of view as well: http://www.microsoft.com/interop/letters/ChrisCapOpenLetter.mspx

    I have considered both viewpoints. IMO: the OOXML standard is just another msft scam. Msft is continuing to abuse its monopoloy position, and aggressively fighting to maintain and extend its monolopy position.

    But, that is just my opinion. Please consider both sides of the arguement, and come to your own conclusions.

  72. Re:Um, this is a perfect example of "ad hominem".. by marcosdumay · · Score: 1

    Tobacco company representatives should not be believed when they say smoking doesn't seriously affect your health, because they're just defending their own multi-million-dollar financial interests.

    Just replace the relevant references with words like IBM, OOXML, etc. and it's basically the same.

    I couldn't explain in a better way why, on real life, you can't blindly trust logics.

    See, we can't stop to verify every testimony of every person that MS buy. We simply don't have the time, nor all the facts.

  73. Re: ad hominem by holloway · · Score: 1

    Oh and just to clarify, I'm not saying that people are trying to hunt anyone down, or that there would be any "disgusting or threatening" communications (I have no reason to think that and I certainly people haven't been behaving that way).

  74. Re: ad hominem by ozbird · · Score: 1

    Another one: this time in India.

  75. What's on offer? by Anonymous Coward · · Score: 0

    Theocrat corporate whore politicians sell themselves. Are they worthwhile?

  76. In re politely-spoken loser and chairs by Anonymous Coward · · Score: 0

    I hereby promise to donate $5 to the Steve A. Ballmer Memorial Whoopee Cushion Fund provided that a) others match funds until a sufficiency for a really good one is reached, and b) a volunteer or volunteers come forward with credible plans to permanently affix same to SteveB's chair and/or pants at the next shareholder's meeting. Since the stock has been performing so well, and since the company has turned into such a good corporate citizen, let's let Steve know how much we really appreciate (or otherwise) him.

    I mean, seriously....Bozo the Clown could be a more effective CEO. We've really had enough of his Evil Twin. And, if I recall correctly, Good Bozo actually catches chairs.