Slashdot Mirror


Microsoft Patents Sudo's Behavior

Foofoobar writes "Just when you thought all was safe on the crazy patent front, Microsoft has come out of the obvious patent closet to file patent number 7617530, which basically duplicates the functionality of 'sudo' which is found in all Linux systems. PJ over at groklaw has a wonderful writeup on the entire fiasco."

657 comments

  1. Penalties by alain94040 · · Score: 3, Interesting

    I don't condemn all software patents. Just because it's software doesn't mean that it can't be brilliant and stunningly innovative.

    But sudo with a GUI? A quick fix I'd suggest to get rid of those bogus patents is to have a rule that says that if a patent is proven obvious later on, then the company (Microsoft in that case) would lose all their patents for the year. That would make them think twice before filing junk...

    ---
    the Co-FoundersMeetup in Mountain View is next week

    1. Re:Penalties by isama · · Score: 1, Informative

      sudo with a gui? gksu

      lame.

    2. Re:Penalties by sopssa · · Score: 5, Insightful

      It's US patent system's fault, not Microsoft. They have to file these to cover their own ass. And actually I haven't ever seen MS patent trolling, they've even gave their patents to organizations which purpose is to keep them open. Even the TomTom vs. Microsoft case was because TomTom attacked MS first and they had to counter.

      Patent system is the one to blame.

    3. Re:Penalties by jez9999 · · Score: 0

      I condemn all software patents.

    4. Re:Penalties by Ethanol-fueled · · Score: 5, Funny

      Patent system is the one to blame.

      There are too many sudo-intellectuals running it, that's why.

    5. Re:Penalties by alexborges · · Score: 4, Insightful

      Patenting sudo is a slight legitimate error?

      Damn. I want some of that anti-guilt thing you are taking.

      --
      NO SIG
    6. Re:Penalties by Tim+C · · Score: 5, Informative

      I don't condemn all software patents.

      I do. Copyright protects software, there's no need for patent protection.

    7. Re:Penalties by neiras · · Score: 5, Funny


      $ make me a patent
      make: *** No rule to make target `me'. Stop.
      $ sudo make me a patent
      Okay!
      $

    8. Re:Penalties by postbigbang · · Score: 4, Funny

      No, it was a typo.

      They patented *sume*. Long 'e' by the way.

      --
      ---- Teach Peace. It's Cheaper Than War.
    9. Re:Penalties by adamdoyle · · Score: 3, Insightful

      copyright doesn't protect against duplicating functionality - only copying the exact binaries/source code. If I want to write my own sudo replica, copyright doesn't stop me... but a patent would.

    10. Re:Penalties by cromar · · Score: 1

      Maybe MS doesn't patent troll, per se, but they have certainly done some bullying using the patent system.

    11. Re:Penalties by Theaetetus · · Score: 0, Redundant

      I don't condemn all software patents.

      I do. Copyright protects software, there's no need for patent protection.

      Copyright protects a specific implementation of software.

      Tell you what, send me copies of all your source code. I promise I won't copy them. However, when I come out with programs that do the exact same thing, but in a different language, and then refuse to pay you a license fee because I didn't infringe your copyright, then let's see whether you think software may need more protection than just copyright.

    12. Re:Penalties by Toonol · · Score: 5, Insightful

      copyright doesn't protect against duplicating functionality - only copying the exact binaries/source code. If I want to write my own sudo replica, copyright doesn't stop me... but a patent would.

      That is one of those statements where both sides shout "EXACTLY", and then stare at each other.

    13. Re:Penalties by jim_v2000 · · Score: 1

      It's not "sudo with a gui". PJ apparently couldn't take the time to actually read what the patent was for. The system here isn't for rights elevation in general, it's for showing which user accounts have rights to do the selected action. So if you're trying to install something (and you don't have admin rights at all...no rights elevation privs or anything like that), it doesn't pop up and say "Please enter the username/password for an administrator account". Instead, it will pop up and say something like "Pick one of these admin accounts and type in the password".

      --
      Don't take life so seriously. No one makes it out alive.
    14. Re:Penalties by JWW · · Score: 4, Insightful

      If you have a copy of his source code and duplicate product in another language, you'll get your clock cleaned in court. To effectively copy the other guys software, the best defense would be to have no knowledge whatsoever of his code.

      Historically everyone in software has been copying everyone else all along. Things were fine before patents became all the rage. Imagine is Apple had patented the GUI in 1984. The windows GUI couldn't have been developed patent free until 1999. It's an absurd idea, no matter how much I currently dislike windows dominance. And, yes, I do realize Apple stole the GUI from Xerox...

    15. Re:Penalties by Anonymous Coward · · Score: 4, Insightful

      Do we actually want to prevent duplication of functionality?
      Also, isn't patent still supposed to allow duplicated functionality if the implementation is different enough?

    16. Re:Penalties by honkycat · · Score: 1

      No, software does not need more protection than just copyright. I don't see any aspect of your little scenario that suggests it does. If someone wants to reverse-engineer a piece of software, then more power to them. If I want to be protective, I am not going to send you the source code to "not copy."

      We'd all be better off without the quagmire that is patented software and algorithms. Can you really pretend we'd be better off if the word processor or spreadsheet had been patented when they were first invented?

    17. Re:Penalties by epee1221 · · Score: 1

      If I don't want others to be able to duplicate what I've done, why would I send out my source code? I'm keeping it as a trade secret.

      --
      "The use-mention distinction" is not "enforced here."
    18. Re:Penalties by Whitemage12380 · · Score: 1

      I'm sure you have a good point somewhere, but using an example in which someone gives you full source code and then expects licensing fees doesn't help your case.

    19. Re:Penalties by Waffle+Iron · · Score: 5, Insightful

      And actually I haven't ever seen MS patent trolling,

      Their shakedown of camera vendors and threats to OS implementors over the VFAT patents are a classic case of patent trolling.

      The technology covered by the patents no longer has any intrinsic value, because nobody uses OSes that don't support long filenames. The only reason to use the long/short filename conversion in VFAT is purely circular: to ensure compatibility with VFAT itself.

      Thus, these patents only remaining purpose in life is to create a barrier to entry in the markets that Microsoft operates in. The technology covered by them is is providing no end-user benefit, and consumers are paying royalties and getting nothing in return other than a less competitive market.

    20. Re:Penalties by Anonymous Coward · · Score: 1, Funny

      How original.

      http://xkcd.com/149/

    21. Re:Penalties by Anonymous Coward · · Score: 0

      A GUI on sudo isn't even novel (never mind non-obvious): Even stuff like ubuntu has that (in some places).

    22. Re:Penalties by Anonymous Coward · · Score: 0

      Seconded.

    23. Re:Penalties by Hurricane78 · · Score: 1

      But copyright does not protect inventors. Copyright does ONLY protect those who COPY it (reproduction and extortion industry). That's why it's called that way.

      And that's why ACTA would be horrible for Germany, where we still have dominant urheberrecht, that protects the creator/inventor/author, and is not transferable at all.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    24. Re:Penalties by Theaetetus · · Score: 1

      No, software does not need more protection than just copyright. I don't see any aspect of your little scenario that suggests it does. If someone wants to reverse-engineer a piece of software, then more power to them. If I want to be protective, I am not going to send you the source code to "not copy."

      We'd all be better off without the quagmire that is patented software and algorithms. Can you really pretend we'd be better off if the word processor or spreadsheet had been patented when they were first invented?

      So you'd prefer trade secrets (as another poster to the same parent post suggested)? No one published source code, no one publishes patent applications, you can reverse engineer an application... if you can?

      Frankly, I prefer living in an industrialized country. Every industrialized nation in the world has implemented a public-disclosure-in-exchange for-a-time-limited-monopoly system to specifically encourage innovation which trade secrets otherwise stifle.

    25. Re:Penalties by buchner.johannes · · Score: 1

      "sudo !!" does the same and is so much better semantically.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    26. Re:Penalties by Lord+Lode · · Score: 1

      The originality lies in the combination of that xkcd (which I'm sure both the author of the post and his intended audience know) with the topic of this slashdot article. Genious.

    27. Re:Penalties by Kerrigann · · Score: 2, Insightful

      That sounds pretty ridiculous... what you would have created would most definitely be a derivative work, which would have copyright protection.

      If you clean-room reverse engineered the program down to the last pixel, wouldn't there be a copyright claim to the layout and specific appearance of the program?

      If the program looks different, is coded independently, but performs the same algorithms and functions, well that's called *interoperability*. If you don't understand why that's important, then we'll never ever agree.

      I'm talking about a specific steering wheel design, you're talking about *the entire idea of a steering wheel*.

      Somebody else came up with the idea of html, markup, tying a scripting language to said markup, asynchronous updates on the markup, and everything else we're using to communicate here, and there are probably patents covering most of it. Do you think that only very large companies with very large armies of lawyers should be writing web pages?

      I'll give you that there are probably a select few areas where some patentable idea could be expressed in software, but the barrier to entry is so low in software development, that they all would have been implemented anyway. Patents are not a land grab or a right, they were only supposed to be used to increase production and knowledge. They don't, they waste huge amounts of energy, which is why people around here get so frustrated (and make silly arguments).

      Of course, I'm not adding anything new and you probably knew all this, so I'll shut up now.

    28. Re:Penalties by mea37 · · Score: 1

      Copyright was designed to protect expressive works. Computer code is not typically expressive, but rather is typically functional. For 99.99% of software, copyright protection is a horrible retrofit that I can only believe came about because nobody really thought it through.

      I see nothing that distinguishes software designs from any other design WRT the intent of patent. I hear lots of arguments that show how absurd a software patent can be - apparently based on the idea that if there's any software you can patent, then that must mean that any bit of software could be patented.

      There are plenty of physical "inventions" that should not be patentable, and the copyright law tries to categorize the reasons why a given invention would fall in this category. The same categories work equally well with software patents, with the caveat that someone lacking software skill would have a hard time evaluating them. (But guess what - someone without EE training would have a hard time applying them to a circuit board.) All of the nightmare scenarios I hear about "...someone could patent X if software patents are allowed" would actually be prevented just by applying such standards as novelty and usefullness.

      Note I said "work equally well", not 'work perfectly'. Even in the world of inventions whose embodiments are tangible machines, the criteria for patentability are imperfect. It's really a tough problem, and if you find that reason enough to oppose all patents then I can understand that position (though I wouldn't agree). I find it harder to understand singling out of software patents on those grounds.

      The only distinction I think is "real" around software patents is - while physical patents tend to restrain you from doing things you'd have a hard time doing anyway, a software patent may often be the one thing keeping you from making/selling/using something. Just another instance where the digital world has made something so easy, that people just want to assume it should be legal and unrestrained.

    29. Re:Penalties by Anonymous Coward · · Score: 0

      Also, patenting formulae and algorithms is a terrible idea.

    30. Re:Penalties by earlymon · · Score: 1

      I'd suggest to get rid of those bogus patents is to have a rule that says that if a patent is proven obvious later on...

      The law already says that you can't patent anything already obvious to those familiar with the art, or technology, in the area to which your patent applies (I paraphrase).

      One should already be able to overturn any obvious patent.

      The problem is that some patent examiners are good, some are less so - I know this from firsthand experience.

      One opinion on the matter here:

      http://www.cl.cam.ac.uk/~mgk25/stallman-patents.html

      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    31. Re:Penalties by earlymon · · Score: 4, Funny
      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    32. Re:Penalties by chaboud · · Score: 4, Funny

      You're use of the word "genious" is brillant.

    33. Re:Penalties by earlymon · · Score: 1

      The originality lies in the combination of that xkcd (which I'm sure both the author of the post and his intended audience know) with the topic of this slashdot article. Genious.

      Agreed.

      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    34. Re:Penalties by fritsd · · Score: 2, Interesting

      You're using the argument that without software patents, those "inventions" would not be publically disclosed (after all, that's the trade-off, right?) So why is it that the source code of those "inventions" is not attached to the patent as proof of public disclosure? There's no technical reason whatsoever to not do this.

      --
      To be, or not to be: isn't that quite logical, Slashdot Beta?
    35. Re:Penalties by Kerrigann · · Score: 1

      I think that *Europe* is pretty civilized, and they specifically exclude business method and software patents still, as far as I know.

      And like fritsd said, we don't see source code attached to patent applications, and you go read most software patent applications and tell me if they *help* you develop anything.

    36. Re:Penalties by Anonymous Coward · · Score: 0

      Yeah i'm fine with trade secrets in software. Try to tell me that sudo is a trade secret or that doing activity X but on the Internet is going to seriously be a trade secret. Even novel software algorithms for encryption or compression can stay trade secrets. Eventually someone is going to come along and bring something similar to the table. It may not be as good or it may be better but then you have something that the software industry hasn't seen in a very long time, COMPETITION. I say to all those companies, keep your ingenious ideas to yourself, because someone else will come up with something better eventually. No time to sit on your ass and collect residuals on one hit wonders. Isn't that how business was supposed to operate?

    37. Re:Penalties by Theaetetus · · Score: 1

      So why is it that the source code of those "inventions" is not attached to the patent as proof of public disclosure? There's no technical reason whatsoever to not do this.

      Because flow charts and extensive descriptions are enough to show a qualified programmer how to implement the program, and if you include source code in, say, C, then someone will later argue in litigation that you only invented it in C and their translation to Perl doesn't infringe your patent. The flow chart says "do it this way" while the code only says "this is one specific example".

    38. Re:Penalties by Theaetetus · · Score: 1

      I think that *Europe* is pretty civilized, and they specifically exclude business method and software patents still, as far as I know.

      ... but they allow Beauregard claims like the one here - "a computer-readable medium comprising computer-readable instructions for performing the steps of..." So, no... they only exclude a very narrow category.

      And like fritsd said, we don't see source code attached to patent applications, and you go read most software patent applications and tell me if they *help* you develop anything.

      Sure they do, but then, I'm a qualified programmer who can read a flow chart.

    39. Re:Penalties by damburger · · Score: 4, Insightful

      I always thought a sudo-intellectual was someone who thinks they are smart enough to be given the root password...

      --
      If we can put a man on the moon, why can't we shoot people for Apollo-related non-sequiturs?
    40. Re:Penalties by dougisfunny · · Score: 1

      In this case however, what has MS disclosed that would encourage innovation?

      A patent was supposed to be for the case, "I have this neato machine that does X and Y, it uses this method M to do X and Y"

      So anyone else could see a machine that does X and Y, and build there own as long as it uses some other method of their own devising O to complete X and Y.

      A software patent is a case "I have this neato program that does X and Y on a computer"

      And the patent is for doing X and Y, not the implementation M. M is not disclosed. No one else is allowed to do X and Y.

      --
      This is not the funny you're looking for.
    41. Re:Penalties by Anxiety35 · · Score: 1

      I thought the USPTO was cracking down on patent troll companies like this one that don't do anything else.

    42. Re:Penalties by jocknerd · · Score: 4, Insightful

      Math equations can be brilliant and stunningly innovative yet they can't be patented. Why should software be any different?

    43. Re:Penalties by lilomar · · Score: 1

      +1 Hilarious But True.

      --
      The creator of this post (Jacob Smith) hereby releases it, and all of his other posts, into the public domain.
    44. Re:Penalties by PFI_Optix · · Score: 4, Informative

      After skimming the patent, this sounds more like it's more like prompting for sudo. If this were Linux, it would be something like:

      "You need to use sudo to run this program. Would you like to use sudo? y / n"

      This is a very specific patent and most certainly wouldn't cover sudo, but rather the automatic detection of the need for it and a very detailed description of the GUI built on it. It's almost like the people writing about the patent didn't bother to read it...

      --
      120 characters for a sig? That's bloody useless.
    45. Re:Penalties by Theaetetus · · Score: 0, Redundant

      In this case however, what has MS disclosed that would encourage innovation?

      A patent was supposed to be for the case, "I have this neato machine that does X and Y, it uses this method M to do X and Y"

      So anyone else could see a machine that does X and Y, and build there own as long as it uses some other method of their own devising O to complete X and Y.

      A software patent is a case "I have this neato program that does X and Y on a computer"

      And the patent is for doing X and Y, not the implementation M. M is not disclosed. No one else is allowed to do X and Y.

      Nope... A software patent is still "I have this neato computer that does X and Y. It uses this method M to do X and Y." If your software doesn't do anything useful, then it's not patentable.

    46. Re:Penalties by atheistmonk · · Score: 1

      EXACTLY!

    47. Re:Penalties by mcguirez · · Score: 1

      Ah this brings back memories... baiting the grammar Nazi's. Wonderful fun.

      --
      When you hear hoofbeats, think horses, not zebras
    48. Re:Penalties by hdparm · · Score: 1

      Not to mention your use of the word "your".

    49. Re:Penalties by RiotingPacifist · · Score: 1

      so sudo that parses /etc/sudoers beforehand to find who can run the command and you can be elevated to? oh well that's totally different!

      --
      IranAir Flight 655 never forget!
    50. Re:Penalties by PFI_Optix · · Score: 1

      They didn't patent sudo. Read the patent.

      --
      120 characters for a sig? That's bloody useless.
    51. Re:Penalties by b4upoo · · Score: 1

      Not only with Microsoft, but with other large corporations as well , we need to seriously increase the size of fines to the point that these firms dread them. For example a fine of one billion dollars sounds like big money to almost all of us but when a company can make twenty billion and be fined only one billion for the act that created that twenty billion the size of the fine is an encouragement and a signal that the company should keep on violating laws and other peoples' rights. It is like a fine to me of $100 for breaking into your home. The catch being that I found five thousand bucks in your home. The criminal justice system is running the same way. Shoot a young man and ruin his life, put him in a wheelchair, and get only ten or twenty years in jail. That is not justice.

    52. Re:Penalties by Anonymous Coward · · Score: 0

      this is one of the best comments i've read on slashdot for a while

    53. Re:Penalties by honkycat · · Score: 1

      In a word, yes.

      There seem to be a lot of software patents that are interesting as an interface widget or as a solution to a problem, but are rarely technically complicated. To use my example, if you merely use a word processor or a spreadsheet, you know it is a useful tool. You don't need the source code or a detailed patent application to develop another. Similarly with the Microsoft patent in question-- it's clearly a simple UI extension (if even that) of a technical solution that's existed for decades. Any competent systems programmer who used the interface would have a pretty good idea how to reimplement it without any further assistance.

      To me, that does not rise to the degree of novelty/non-obviousness to warrant a patent. Sure, your implementation of the idea is yours through copyright.

      I'm actually inclined to be a bit more sympathetic to more complicated technical achievements, but I still don't believe we benefit as a society from the technological Balkanization that occurs as a result of software patents. There's a murky muddy line between mathematical truths and software algorithms, and we're better off if we keep government-sponsored monopolies away from mathematical truths.

      Finally, nice try with the "industrialized country" bit, but that really doesn't get off the ground. I'm not arguing against patents as an institution, just their (mis-)application to software and algorithms. Patents and copyrights are distinct concepts for a reason-- in a sense, one deals with "things" and the other with "ideas." Extending the rules for one into the milieu of the other is a dangerous endeavor.

    54. Re:Penalties by IAmGarethAdams · · Score: 1

      Not to mention your use of the word "Whoooooshhhh!"

    55. Re:Penalties by RichardJenkins · · Score: 1

      The patent says:

      "Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention."

      Which I read as:

      "Software patents are the corporate equivalent of jerking off"

      Perhaps my reading comprehension needs some work.

    56. Re:Penalties by Kerrigann · · Score: 1

      Hey, I never meant anything personal, sorry if I offended you.

      Most patents I've read look like this:

      http://www.google.com/patents/about?id=RX94AAAAEBAJ

      or this:

      http://www.google.com/patents?id=Ay99AAAAEBAJ&dq=7139761

      Lots and lots and lots of description of the minutia of any complex system that really wouldn't help me unless I was trying to do something that was exactly the same, and in the exact same environment, and maybe not even then. And that is buried in tons of description of basic computer science or engineering concepts like what a WAN or LAN is and what eeprom is.

      Maybe you can make sense of that and gain something from it. I guess I could too, in the sense that they're like very obfuscated requirements documents.

      But, you caught me, I have not had enough patience to actually read an *entire* patent like these before.

      And, of course, they're not all like this... but man are there a lot of them.

      Oh, and I thought the European Patent Convention required (at least recently) that the invention make significant contribution in an otherwise patentable area, i.e. no *pure* software patents. I might be wrong on that.

      But yeah, I can read a flow chart, on a good day, I can even *draw* a mean flow chart. And I'm sure you can too :)

    57. Re:Penalties by Clopnixus · · Score: 1

      Yup, they are all patently stupid.

    58. Re:Penalties by Anonymous Coward · · Score: 0

      The way you phrase it... it seems you favor "protecting against duplicating functionality".

      Know by this that I consider such attitude evil.

      Not wanting others to do what we do amounts to being selfish and preventing others from behaving on equal footing (possibly with evil intents like preventing others from thriving).

      That's Bad on my dictionary. With a big B.

    59. Re:Penalties by Theaetetus · · Score: 1

      Hey, I never meant anything personal, sorry if I offended you.

      Most patents I've read look like this:

      http://www.google.com/patents/about?id=RX94AAAAEBAJ

      or this:

      http://www.google.com/patents?id=Ay99AAAAEBAJ&dq=7139761

      Lots and lots and lots of description of the minutia of any complex system that really wouldn't help me unless I was trying to do something that was exactly the same, and in the exact same environment, and maybe not even then. And that is buried in tons of description of basic computer science or engineering concepts like what a WAN or LAN is and what eeprom is.

      No prob... it does take a lot of patience, but if you look at those two, one has 41 figures and descriptions relating to each, the other has 18, including figures and system diagrams. I'm drafting one right now that has flow charts, system diagrams, and even packet flow diagrams. Remember, the claims aren't there to teach you how to use the invention - they're there to define it. The specification and figures are there to teach you how to use it.

      As for the defining of basic computer science stuff, blame the USPTO. Right now, when we say "LAN" in a claim, they come back and say "what's a LAN - you didn't define it in your specification", so we end up having to put in paragraphs about how "a network can be a local area network, commonly known as a farking LAN."

    60. Re:Penalties by PopeRatzo · · Score: 1

      lame.

      No...Fraunhofer.

      --
      You are welcome on my lawn.
    61. Re:Penalties by supernova_hq · · Score: 1

      That's like saying you can translate an english book to french, sell the french version and not get hit by copyright.

      Yeah, good luck with that one...

    62. Re:Penalties by Zordak · · Score: 1

      Does sudo have "information indicating the task and an entity that attempted the task; a selectable help graphic wherein responsive to receiving selection of the selectable help graphic, the computer-readable instructions further cause the computing device to present the information; identifiers, each of the identifiers identifying other accounts having a right to permit the task, wherein the identifiers presented are based on criteria comprising: frequency of use; association with the user; and indication of sufficient but not unlimited rights; one of the identifiers identifies a higher-rights account having a right to permit the task, wherein the one of the identifiers comprises: a graphic identifying the higher-rights accounts associated with the user; and a name of the higher-rights account; an authenticator region capable of receiving, from the user, an authenticator usable to authenticate the higher-rights account having the right to permit the task, wherein: the authenticator comprises a password, and the authenticator region comprises a data-entry field configured to receive the password"?

      No? Then you're just posting a knee-jerk reaction to something you don't understand.

      --

      Today's Sesame Street was brought to you by the number e.
    63. Re:Penalties by supernova_hq · · Score: 1

      Also, patenting formulae and algorithms is only allowed in software patents.

      There, fixed that for you.

    64. Re:Penalties by RichardJenkins · · Score: 2, Interesting

      After reading the patent, best I can tell is it's saying:

      "Sometimes an application tries to do something whilst running under a non-privileged account. If an application tries this we could use [magic] to interrupt the process and present a dialogue allowing a user to assume permissions of another account which we know has appropriate permissions [by magic]. Alternatively, we could [do magic] to determine if the user can elevate privileges of their own account, and allow them to do so."

      I'm not sure if such a system existed when this was filed in 2005 (it certainly does now, except the bits which this patent does by magic are fully fleshed out and publicly viewable in the source), but the only non-obvious part in going from the following scenario:

      rj@laptop:/$ passwd root
      passwd: You may not view or modify password information for root.
      rj@laptop:/$ sudo passwd
      [sudo] password for rj:
      Enter new UNIX password: ...to what they described is the bit which they've left to magic.

      Most tellingly: "the specific features and steps are disclosed as preferred forms of implementing the claimed invention." they're trying to steal the feature of automatic privilege escalation from anyone who wants to build it without going through MS.

    65. Re:Penalties by Anonymous Coward · · Score: 0

      Linux - 1991
      Microsoft - Public since 1987. Where is the prior art?

      Not defending MS, just pointing out the obvious.

      How long has sudo been in unix?

    66. Re:Penalties by FlyMysticalDJ · · Score: 1

      If such a law were put into place, I could see that as essentially creating a limit of one patent per organization per year that can't afford enough legal advice to ensure 100% they don't get a patent declared obvious. I'm all for getting rid of superfluous patents and money grubbing, but not at the cost of making innovation harder, especially those without money.

    67. Re:Penalties by HungryHobo · · Score: 4, Interesting

      The problem being you can engineer your way round a patent on a specific innovative break design in a car.
      Trying to work around a patent with a flowchart with a note reading "slows car down" is pretty much impossible.

      Hence it kills innovation, not encourages it.

    68. Re:Penalties by Anonymous Coward · · Score: 0

      So you'd prefer trade secrets (as another poster to the same parent post suggested)? No one published source code, no one publishes patent applications, you can reverse engineer an application... if you can?

      How the fuck is that any different than what we have *RIGHT NOW*, except that you have patents loaded on top of it?

    69. Re:Penalties by jim_v2000 · · Score: 1

      And you have to explicitly use sudo, vs a screen popping up on demand. It is totally different.

      --
      Don't take life so seriously. No one makes it out alive.
    70. Re:Penalties by socceroos · · Score: 1

      I've also heard that "sudo ???" makes you money as well.

    71. Re:Penalties by NotQuiteReal · · Score: 1

      I just assumed Lord Lode works for the government, and while wasting work time on Slashdot, accidentally let slip the acronym for the latest program he is working on.

      Genious is clearly short for "generate IOUs", which, if you live in California, you have seen in the recent past, and will probably be seeing more of, if the state owes you money.

      --
      This issue is a bit more complicated than you think.
    72. Re:Penalties by daver00 · · Score: 4, Insightful

      I presented this argument to someone just the other day, but here it is again: Mathematicians develop insanely difficult and complex algorithms all the time, and must share their work in the public domain because you can't copyright or patent mathematics. Not a formula, I'm talking about full algorithms, logical procedures, proofs and so on. Algorithms which have changed the world by such orders of magnitude that no matter how novel and amazing some little piece of code looks to the programmer, compared to the work of mathematicians it is almost always will come up looking pretty much completely trivial.

      Imagine if someone had patented the fast fourier transform? Or any number of a virtually infinite set of unique and groundbreaking algorithms that have literally changed the course of science. Technology and science would be weaker for it, you might not even have a job with a computer in front of you.

      Now why is it that sequences of logical steps, algorithms, when developed by mathematicians are anybodies game, and yet when a programmer or a software company comes up with an algorithm, a sequence of logical steps no different to the ones in the field of mathematics, it is suddenly different and needs monopoly rights granted to the author? Do you honestly think that novel method 3.57a to make database requests in a unique way is as important to the world as something like the fft? Or the Kalman filter?

      Get over yourselves programmers, your code is not special, logic is logic, patenting a logical procedure is about as wrong as it gets in my books. If you develop code and it is useful, you are going to be the foremost expert in your new system. You will make money without a patent. The problem is this isn't about putting food on the table, this is about geeks who fancy themselves Knuth thinking they ought to be millionaires.

    73. Re:Penalties by Attila+Dimedici · · Score: 1

      copyright doesn't protect against duplicating functionality - only copying the exact binaries/source code. If I want to write my own sudo replica, copyright doesn't stop me... but a patent would.

      Patents weren't intended to protect against duplicating functionality, they were intended to prevent outright copying of design. If person A has a patent on a machine to make widgets, person B can still build machines to make widgets, it just has to do it differently than the way described in person A's patent (unless person B licenses that technology from person A).

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    74. Re:Penalties by Anonymous Coward · · Score: 0

      But sudo with a GUI?

      If that's what this patent was for, it would be pretty outrageous, but it isn't. If you read the patent, it's about a specific user interface design for privilege elevation, namely the UAC design Microsoft introduced in Vista. Nobody in their right mind would claim sudo violates this patent, or even sudo with a GUI unless implemented with exactly the same user interface.

      Once again, some Groklaw troll has worked the slashbots into a frenzy over nothing. Maybe it will help put pressure on the US government to do something about excessive use of patents (especially but not only for software and business models), so it might have a good result, but the troll who started this whole thing either didn't read the patent, didn't understand it or is being deliberately dishonest.

    75. Re:Penalties by Bigjeff5 · · Score: 1

      I think, therefore I am.

      Now gimme gimme gimme!

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    76. Re:Penalties by Kerrigann · · Score: 1

      Oh, trust me, I read past the claims section.. these were two patents that caught my attention because they were on slashdot previously, and I wanted to see what the average software patent looked like. They always look like a laywer and a programmer sat down and translated every diagram and requirements document into legalese.

      I mean look...

      The system management tools available with the present invention allow system administrators to monitor, control and customize an institution's online teaching and learning environment from the web browser. The system administrator may control security permissions and enable/disable features for numerous user roles. Batch user enrollment (and unenrollment) may be performed system wide. Preferences and options may be managed on multiple courses, all from within a central system administrator panel. The system administrator may also track and report faculty, student and course statistics, may plan and manage system hardware requirements by assigning instructors with pre-assigned disk quotas for content storage, and may employ system-wide announcements to broadcast messages to users about system maintenance or institutional announcements.

      In the Course & Portal Manager embodiment, the enterprise database support provides support for tens of thousands of users across an entire institution or system of institutions. User and course data may be managed efficiently and effectively. Moreover, large volumes of transactions may be managed efficiently and effectively. The "My Institution" interface includes portal and community functionality along with quick access to web email, course and institutional announcements, and links to other campus departments. Administrators may enable or disable portal modules and establish required and optional modules from the portal options menu bar. Administrators may also assign different portal default settings to different user roles (e.g. students get different portals than instructors).

      Course e-commerce management functionality allows institutions to set prices and charge fees for course enrollment directly through the "e-Learning" platform

      That's in the "DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS" section. That's like a back of the box product description. I know they go into more detail later, but it's always meaningless minutiae about what part of the website connects to what, or the fact that such and such field would be retrieved from a database. Well duh. Were these bad examples? Is this what a "design patent" looks like?

      Even the figures are mostly grossly simplified networking diagrams and *screenshots* of the web interface. I mean, come on!

      The second patent looks better, but the novel parts look to be in exactly how they tie information from different logged in users. It definitely seems *interesting*, but it sounds like it's interesting because their problem domain is unusual, not because the concept is amazingly novel independently of that.

      Don't get me wrong, the flow chart comment aside, I think I qualify as a someone reasonably proficient in the field. Up until recently my job was primarily doing aeronatic and numerical processing code for the DoD and designing a library and application for easily integrating aeronautic flight models for the purposes of weapons effectiveness and defensive analysis in dogfights primarily for use at Top Gun and Fallon.

      And these (well, mainly the first one) sound like nearly useless 50,000 views of a system filled mostly with information that you could garner just from *using* the system.

      You know what seems like a straightforward patent? http://www.google.com/patents?vid=4405829 RSA is the most deserving software idea I can think of for being granted a patent... and it seemed to stall web commerce for a decade. It was absolutely a deserved patent... but the barrier to entry for software is just *so low*. It actually seems more valuable to

    77. Re:Penalties by Bigjeff5 · · Score: 1

      It doesn't allow for duplication if the result is the same. It allows for innovations to be added onto an existing patent, so if your different implimentation improved the original in some meaningful and non-obvious way, it should be legit.

      For example, the first person who invents the wheel gets totally screwed out of his innovation if someone else is allowed to make the exact same thing (a wheel) via a different process. Now, if the new process improved the design of the wheel - say by making it lighter and stronger, then the original inventor is just too slow to profit from his idea, as something better has come along.

      This is exactly the reason why a lot of software patents are complete bull, because they usually perform some mundane function, but on a computer. That alone should not be enough to make it innovative, yet we see patents awarded for such things all the time.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    78. Re:Penalties by Kerrigann · · Score: 1

      Thank you for expressing my thoughts much better than I can :)

    79. Re:Penalties by geminidomino · · Score: 1

      Nope. gksu does that already too.

    80. Re:Penalties by geminidomino · · Score: 1

      That doesn't mean that it's not a horrible idea.

    81. Re:Penalties by ThatMegathronDude · · Score: 3, Insightful

      I don't think its most coders that want patents. It's the PHBs.

    82. Re:Penalties by Anonymous Coward · · Score: 0

      I use the word "protect" because that's the whole point. It may not be good for the industry or even good for me, but the reason companies spend insane amounts of money on patents is because they want to "protect" their work.

      (Maybe I should've used quotation marks to convey my disapproval of the USPTO granting patents for overtly trivial applications)

    83. Re:Penalties by Weaselmancer · · Score: 2, Informative

      No, Lame. Fraunhofer is patent encumbered.

      --
      Weaselmancer
      rediculous.
    84. Re:Penalties by Anonymous Coward · · Score: 0

      Your use of the "You're" is genius.

    85. Re:Penalties by ShadowRangerRIT · · Score: 1

      *whoosh* You missed brillant. The errors were clearly intentional.

      --
      $_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
    86. Re:Penalties by Bigjeff5 · · Score: 1

      Unfortunately, although software certainly uses mathematics, software is -not- mathematics. Saying software is mathematics and therefore should not be patentable or copyrightable is akin to saying mechanical engineering is mathematics and therefore not patentable. Well of course it's mathematics, but it produces a product and that product is what is patentable.

      No mathematical algorithm produces anything on its own, no matter how complex it is or how difficult it was create. That is what makes math non-patentable - it produces nothing. Math needs an application to be useful, and it's that application that is potentially patentable.

      In other words, if you took an algorithm and used it to produce a new cryptographic system which was faster and more secure than any previous system, you could patent it. If you took that same algorithm and built a device that would tell the best places to install sensors for survey purposes, and there was no similar way to do that already or the new device makes it better/easier/cheaper, then you could patent that as well. Two patents, two applications, one algorithm.

      Get over yourselves programmers, your code is not special, logic is logic, patenting a logical procedure is about as wrong as it gets in my books.

      I've found programming to be more like engineering that math, and it's certainly about a lot more than logical procedures. If this than that, sure, it also involves applying various algorithms in a way that is useful to the end user. Pure math doesn't bother with this, the math must always be applied somewhere else. That is at the heart of what makes software patentable vs mathematics, math simply doesn't produce a final product, software does. This should be easy to see, since you don't patent the source code (which contains the logic), you patent what the source code compiles into, which is the finished product.

      I believe there is a place for software patents, but I also think software patents are vastly over-issued. For some reason patent officials seem to think "on a computer" is not obvious and deserves a patent.

      I also think that if Patents apply to compiled software, copyright should only apply to the source code. If we consider software a "work of art", then it should not be patentable at all.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    87. Re:Penalties by Rocketship+Underpant · · Score: 1

      Microsoft has to patent sudo to cover its ass? Really?

      Really?

      I can think of 100 other things they could do that would cover their (enormous) ass a lot better.

      --
      He who lights his taper at mine, receives light without darkening me.
    88. Re:Penalties by GoochOwnsYou · · Score: 1

      This is a very specific patent and most certainly wouldn't cover sudo, but rather the automatic detection of the need for it and a very detailed description of the GUI built on it. It's almost like the people writing about the patent didn't bother to read it...

      Sounds like stuff most distro's already have.

      --
      This sig has been distributed under the Creative Commons license.
    89. Re:Penalties by Bigjeff5 · · Score: 1

      Wrong, patents protect the final product. If the widget warrants a patent, person B must improve the widget in some useful, non-trivial way in order to reproduce it.

      The only way person B can reproduce the widget is by licensing the patent to do so from person A. You'll note that in most patent disputes, unless the patent is for the process itself and not the product, that the two parties don't give a rat's ass about the process used to produce either item, and again, unless it's a patent of a process, most patents describe what the product does, not how it is manufactured.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    90. Re:Penalties by Anonymous Coward · · Score: 0

      You're use of the word "genious" is brillant.

      Your use of the word "You're" is genious.

    91. Re:Penalties by Anonymous Coward · · Score: 0

      What about components of guidance systems and other mechanical engineering topics that are in a software medium. Is that the sort of thing that qualifies for software patents?

      I could imagine some of that being fairly innovative and patent-worthy. Is that, perhaps, what they're aimed at?

      For instance, whoever first wrote OCR software, if you ask me, came up with a rather innovative solution. He or she can't patent the scanner (obviously) but it seems reasonable to patent the algorithm for recognizing characters so he/she can have exclusivity (or license it) for awhile. I think twenty years is WAY too long (I think ten would be more reasonable), but I would say an OCR patent is just as patent-worthy as a conventional non-software patent.

    92. Re:Penalties by Imrik · · Score: 1

      It is totally different, now you don't have to try to figure out which accounts you need to break into.

    93. Re:Penalties by ericspinder · · Score: 1

      It's almost like the people writing about the patent didn't bother to read it...

      Well then, they have something in common with the overworked patent clerks. Really something needs to be done about the system, while this patent might seem 'ok', many more over generalized business method patents are becoming land mines for real business innovation. We need to overhaul the system. At least we need to fund better examinations, and review processes. However I'd suggest eliminating the category altogether.

      --
      The grass is only greener, if you don't take care of your own lawn.
    94. Re:Penalties by RiotingPacifist · · Score: 1

      Many programs will prompt for root if they are run with insufficient permissions, that implementation requires programs to be sudo aware, but if i understand software patents correctly, as long as it has the same effect it infringes

      Also policykit seams to do everything that just got patented, I run kpackagekit and it does everything it can as me, but when I try and update I am prompted for a password.

      --
      IranAir Flight 655 never forget!
    95. Re:Penalties by adamdoyle · · Score: 1

      Exactly what kind of machine does one use to "build" software? (and don't say computers)

    96. Re:Penalties by Anonymous Coward · · Score: 0

      He is use of the word brilliant?

    97. Re:Penalties by PFI_Optix · · Score: 1

      I'm not sure I can agree with the abolition of software patents entirely, as copyrights are insufficient in protecting innovation long enough for it to be profitable and there is no other system which ensures a company can recover development costs on truly innovative software.

      There needs to be *something* which protects software developers from having their products ripped off and all their innovative functionality duplicated. Exactly how that *something* should work is best left to people far more expert in the field than me...but before we scrap software patents, we need to provide developers with an alternative.

      --
      120 characters for a sig? That's bloody useless.
    98. Re:Penalties by Attila+Dimedici · · Score: 1

      Person A's final product was machines that make widgets, not widgets. Somebody else makes widgets.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    99. Re:Penalties by Attila+Dimedici · · Score: 1

      In my example the machine was the equivalent of software, not something to build software.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    100. Re:Penalties by KnowledgeKeeper · · Score: 4, Informative

      And, yes, I do realize Apple stole the GUI from Xerox...

      Actually, no. Apple traded their stocks for a day with Xerox engineers which had to show them what they've done. And they've done very little compared to things that were in the first Mac GUI. I.e. overlapping windows.

      Things like these are documented on Apple's folklore site.

      --
      It is always better to be a first grade version of yourself than a second grade version of someone else.
    101. Re:Penalties by icannotthinkofaname · · Score: 1

      Your use of the word "brillant" is quite scholarly.

      --
      Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    102. Re:Penalties by Anonymous Coward · · Score: 0

      That's a very confusing metaphor...

    103. Re:Penalties by icannotthinkofaname · · Score: 1

      Patenting sudo is a slight legitimate error?

      Yes, it's a legitimate error, unless some of them refuse to use the operating system produced by the company.

      Question for which I would like an answer: How many Microsoft employees do you expect use a non-Windows OS, especially it's natural enemy, the FOSS Linux?

      --
      Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    104. Re:Penalties by daver00 · · Score: 1

      I can agree with this reasoning, but the conclusion I draw is we should patent a method, a process, and outcome as you say. But not an algorithm, and certainly not raw chunks of code. That is what I am getting at, an algorithm taken by itself, even if used in the context of a wider application, does nothing.

      It seems these days software patents are nothing more than useless pieces of an idea which by themselves do nothing. I mean we are talking about a patent to protect asking a user if they want to elevate priveledges? That is a nothing if you ask me. There are too many examples of software patents that do nothings, or patents for small pieces of something that might do something... maybe.

    105. Re:Penalties by daver00 · · Score: 1

      What bothers me is that things like OCR and guidance systems are usually just implementations of highly sophisticated mathematical algorithms. Mathematicians do all the heavy lifting.... for free... then people come along and make millions off it.

      OCR I think uses Mumford-Shah methods, and basically that there is maths doing the job for you. You see it appears unique and innovative, but really the innovation was in finding a way of doing the maths in the first place. In my opinion.

    106. Re:Penalties by Anonymous Coward · · Score: 0

      Why should MS have to patent sudo? Even the most cursory prior art search shows that sudo is the default configuration of every system MS has ever produced.

    107. Re:Penalties by Anonymous Coward · · Score: 1, Informative

      Unfortunately, although software certainly uses mathematics, software is -not- mathematics. Saying software is mathematics and therefore should not be patentable or copyrightable is akin to saying mechanical engineering is mathematics and therefore not patentable. Well of course it's mathematics, but it produces a product and that product is what is patentable.

      That's provably wrong. Writing constructive mathematical proofs and writing computer programs are provably the same activity. The Howard-Curry Correspondence is one of many, many proofs.

      In fact, most "technology" -- that is, sets of production techniques -- are provably equivalent to formal algorithms acting on physical resources.

      I've found programming to be more like engineering that math, and it's certainly about a lot more than logical procedures. If this than that, sure, it also involves applying various algorithms in a way that is useful to the end user. Pure math doesn't bother with this, the math must always be applied somewhere else.

      You don't know much about pure mathematics. Algorithms are proofs. Proofs are algorithms. Proofs are arguments and documentation.

      The whole practice of writing mathematical papers belies your point. Heck, Google for "Literate Haskell" to find a LOT of mathematics papers that use Haskell syntax instead of traditional mathematical syntax. Why? Because the code is an implementation of the same mathematical constructs. So you can talk about your construct, in English, and use it for computation, in Haskell.

      On the other hand, there is some truth to what you say with regards to engineering. Complex mathematical papers typically have a single focus. If you want to combine results from multiple papers, you need to cite them. You need to write your document in such a way that it is clear what those other papers say (insofar as it is relevant to your point). You need to develop your own argument. Notice how much this corresponds to writing code: you need to import libraries. You need to make sure the libraries do what you want. You need to structure your code in such a way to make use of the libraries in order to write your computation/argument.

      What you are describing is architecture, and there is a simple mathematical construct that describes the architecture of every computer program (the monad). Using "the wrong monad" is a recipe for spaghetti code, like many modern abuses of an object system.

    108. Re:Penalties by Anonymous Coward · · Score: 0

      Well I guess the real question is why do mathematicians not go the extra mile and implement the stuff they come up with. Obviously they understand what problem they're solving, so why don't they learn a programming language, hire a lawyer, and file a patent? Then: license the patent and make money.

    109. Re:Penalties by NotBornYesterday · · Score: 1

      Do you suppose "You're" and "brillant" were intentionally used for irony?

      --
      I prefer rogues to imbeciles because they sometimes take a rest.
    110. Re:Penalties by NotBornYesterday · · Score: 1

      You are in violation of my patent for posting a condemnation of software patents.

      --
      I prefer rogues to imbeciles because they sometimes take a rest.
    111. Re:Penalties by tuxgeek · · Score: 1

      Funny
      Occasionally when I try to run a command that requires su privileges on my Kubuntu box, the system prompts me to enter my sudo password.
      Not quite how you put it, but it's there

      This is not an original idea of M$
      It's already been done and in use right now .. and has been for years

      --
      "Suppose you were an idiot...and suppose you were a member of Congress...but I repeat myself." Mark Twain
    112. Re:Penalties by tietokone-olmi · · Score: 1

      And too many damned sudo-mites tagging along.

    113. Re:Penalties by the+biologist · · Score: 1

      I take it you haven't read any of the software patents which have been discussed here? They generally refer to "a method for doing [blah] with a computer", without actually stating what the method is.

    114. Re:Penalties by tietokone-olmi · · Score: 1

      If you can't stay ahead in the game, you wouldn't have deserved a patent either. You would sit on your pile of gold and retard progress.

    115. Re:Penalties by Anonymous Coward · · Score: 0

      Your stance is "don't patent software, you silly twerps", so most of slashdot ALREADY agrees with you - you're preaching to the choir. I agree (in theory) that patents should apply to implementations and not concepts (assuming that we can't feasibly scrap patents altogether) - however, it's ludicrously easy to write a piece of code that does the same thing as another but in a different way. In fact, if you're rewriting the code without copy+paste'ing the source, your solution is basically guaranteed to be different in at least some small way - different languages/compilers/libraries and APIs/coding philosophies/coding priorities/design philosophies/naming schemes/syntax schemes/IDE artefacts.. I could go on forever. Now I'm not 100% certain here (I'm absolutely terrible at maths) - but does this apply to maths? Are there often multiple, equally valid ways to write a maths algorithm?

      we are talking about a patent to protect asking a user if they want to elevate priveledges? That is a nothing if you ask me.

      I dunno, sudo is a pretty useful tool. I use it at least as much as say, a web browser (in terms of number of times run). It's practically vital if you want a computer with a decent security model that's also usable. I know there's su, but sudo is easier and safer in some situations (eg, you can set per-user limits in /etc/sudoers, trace security leaks back to a particular user, don't have to worry about giving out the root password over possibly-insecure channels, and it has a fixed upper bound on the window of time for attack).

    116. Re:Penalties by Anonymous Coward · · Score: 0

      EXACTLY !

    117. Re:Penalties by Whiteox · · Score: 1

      Shouldn't that be "brillig"?

      --
      Don't be apathetic. Procrastinate!
    118. Re:Penalties by daver00 · · Score: 1

      In maths there are virtually endless ways to prove things, however constructive proofs tend to lead to specific algorithms which are efficient. There are a number of ways to take a fourier transform for instance, but theres a reason we use the fft. The point of using a specific algorithm has to do with convergence rates, truncation error and so on, so no, you typically are talking about the one algo. There are however usually dozens and dozens of algorithms to achieve any given goal (say solving the matrix system Ax=b), but often one will be uniquely awesome (the fft).

    119. Re:Penalties by daver00 · · Score: 1

      No, they often do not understand the problem that ends up being solved. Thats the thing. Pure maths tends to be more about, assume these conditions are met, these theorems can then be proven true. An applied mathematician, scientist or engineer will typically then discover a new technique and show that it is useful for describing the real world in some way.

      This is still ridiculous to consider as patentable. Imagine if Feynman were able and willing to patent his work on quantum electrodynamics, or Einstein his work on general relativity, because these are both examples of scientists taking existing mathematical techniques and applying them to a problem. The notion that these techniques then 'belong' to these guys is ludicrous. The entire body of engineering is a collection of methods to achieve outcomes using mathematics and logical reasoning.

      Marketable products, I can see a case for patent protections, somewhat, and they should be severely limited. Software patents tend not to be anything close to a complete marketable product, just pieces of random thoughts scribbled down on paper. Engineering patents are ridiculously vague also, and this annoys me.

      What I would love to see is that the patent system require start to finish descriptions of a product, full design schematics, manufacturing processes and a clearly defined description of the operation of the invention. And if you cannot provide such a high level of detail then you should not be granted patent protection. You should also be required to be actively implementing your patent for it to remain valid. Patent trolling is a serious problem that needs to be dealt with, not to mention the problem we have of the patent office being swamped in millions of new patents all the time.

    120. Re:Penalties by Bigjeff5 · · Score: 1

      Sorry, I apparently completely misread the post. So long as the widgets weren't part of the patent there would be nothing stopping person B.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    121. Re:Penalties by falconwolf · · Score: 1

      Copyright protects a specific implementation of software.

      And patents protect a specific implementation of a physical item not what it does.

      Falcon

    122. Re:Penalties by Bigjeff5 · · Score: 1

      I'm assuming you're a programmer when you say this, and as such, have you never been working on a problem, implimented a solution that works, then discussed it with a collegue who said "Why'd you do that? Just do X, Y, and Z first, then you can A, B, C it and be done" in very generic terms and had a giant light light-bulb go off in your head? You think "Oh my God, why didn't I think of that?" Well because it was a better way of doing it.

      That is the kind of thing software patents should cover, though obviously on the truly unique and innovative level, not just the "something I never thought of before" level. It should also give a description of the idea that gives a competant software engineer working in the same area a light-bulb moment of their own.

      MOST software patents aren't even close to that, IMO, and should never have been granted in the first place.

      Lets face it, the USPTO is out of their league when it comes to software patents, and they are over-worked (from what I hear anyway) to boot. Something has to give.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    123. Re:Penalties by Anonymous Coward · · Score: 0

      You're an idiot.

    124. Re:Penalties by falconwolf · · Score: 2, Informative

      And, yes, I do realize Apple stole the GUI from Xerox...

      On Xerox, Apple, and Progress. Fact is in return for Xerox allowing Steve Jobs and a development team to tour PARC Jobs allowed Xerox to invest in Apple by buying 100,000 shares of stock at $10 a share. Less than a year later that $1 million investment netted Xerox $17.6 million when Apple had it's IPO.

      Falcon

    125. Re:Penalties by Beat+The+Odds · · Score: 1

      You're use of the word "genious" is brillant.

      Your use of "you're" is also brilliant!!
      Thanks for the laugh though...

    126. Re:Penalties by falconwolf · · Score: 1

      Frankly, I prefer living in an industrialized country

      So do I, I especially wouldn't want to spend thousands never mind millions of dollars to research something only to be slapped with a patent infringement lawsuit.

      Every industrialized nation in the world has implemented a public-disclosure-in-exchange for-a-time-limited-monopoly system to specifically encourage innovation which trade secrets otherwise stifle.

      Which copyrights do, no need for patents. As it is now a number of economic studies have concluded patents may stifle innovation. Study finds patent systems may discourage innovation. Patent systems may discourage innovation. Patents Don't Promote Innovation: Study.

      Falcon

    127. Re:Penalties by falconwolf · · Score: 1

      copyright doesn't protect against duplicating functionality - only copying the exact binaries/source code. If I want to write my own sudo replica, copyright doesn't stop me... but a patent would.

      And that's one of the problems with patents. If I invent and design a car but someone else has already patented a car then I'm out of luck. It could operate entirely differently but too bad. Or take electricity, a capacitor or resister can be made in a number of ways but if the idea of a capacitor or resister is patentable then no matter how many ways there are to make one it's too bad, all of them but the ones invented by the patent holder infringe on the patent.

      Ideas should not be patentable.

      Falcon

    128. Re:Penalties by picz · · Score: 1

      Royalties and closed markeds are nice to have for a company, but there is more to it.

      I fully understand Microsoft and other large companies. They "arm themselfes" with patents and use them in the same way as strategic nuclear weapons are used by governments.

      Every big business has to aquire as many patents as possible for everything they can think of. If they don't have them, they are sitting duck and can easily be ruined by lawsuits from other players.

      Every company is infringing patents owned by others, because basically everything useful is being patented. There is a fragile equilibrium, because everybody is affraid to start lawsuits, knowing that a counter lawsuit will be launched against you.

      This is how patents are used today. The big companies are not the ones to blame. The patent system made this behaviour possible, so it has to be fixed.

      --
      ------- Look mum! I have posted another Slashdot comment! --------
    129. Re:Penalties by IICV · · Score: 5, Informative

      Further: how quickly we forget the threat of those 235 patents. If that's not patent trolling, what is?

    130. Re:Penalties by Anonymous Coward · · Score: 0

      *whoosh*

      (since you probably won't understand this message either: that was the sound of the GPs post going over your head)

    131. Re:Penalties by Thinboy00 · · Score: 1

      Hmm, now where have I heard "brillant" before...

      http://thedailywtf.com/articles/the_brillant_paula_bean.aspx

      --
      $ make available
    132. Re:Penalties by GofG · · Score: 1

      Your use of the two words "you" and "are" are equally brilliant. I can't tell if they were intended or not :/

      --
      GFA/M/S d-- s: a--- C++++ UBL++$ P+ L+++ !E- W++ N+ !o K- w--- !O !M !V PS++ PE Y+ PGP+ t+++ 5- X+ R tv@ b++ DI++++ D+ G
    133. Re:Penalties by niftymitch · · Score: 1

      Good golly this may be slightly more interesting than sudo which hinges on the SUID bit.
      In a multiple level security system like Trusted Irix, Multix or some of the other systems like WinNT sudo is not sufficient in and of itself.
      Linux has Security Enhanced Linux (SELinux) and depending on the structure of the policy. "sudo" alone is not sufficient for privilege transitions. In some policy structures the phrase "cannot get there from here" applies and the only solution is to log out and back in at a new level. On Linux I also think the Smack project comes to mind as another possible area of prior art.
      All in all, I cannot believe that there is a novel invention here but what do I know....

      --
      Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
    134. Re:Penalties by Anonymous Coward · · Score: 0

      You spelled "spelt" wrong.

    135. Re:Penalties by Anonymous Coward · · Score: 0

      As is your use of "you're".

    136. Re:Penalties by Anonymous Coward · · Score: 0

      "you're" has no business in the GP post, just so you know...

      Think about it: "Enough of you are 'bating"? .. because that IS what you're means, you know?

    137. Re:Penalties by Anonymous Coward · · Score: 0

      Did you just... mention Nazis?

    138. Re:Penalties by donaldm · · Score: 3, Insightful

      There needs to be *something* which protects software developers from having their products ripped off and all their innovative functionality duplicated. Exactly how that *something* should work is best left to people far more expert in the field than me...but before we scrap software patents, we need to provide developers with an alternative.

      There are plenty of somethings that can protect software developers:

      1. Copyright
      2. Proprietary software. In other words don't publish your code.
      3. Licences such as GPL, LGPL, BSD (if you want to give it away), Creative Commons, ... etc

      I am sure this can easily be added to without resorting to stupid software patents, which IMHO don't contribute to innovation in developing software. The only people that stand to gain from software patents are the Lawyers and patent Trolls.

      Why am I so down on Software Patents? Well try to read one sometime, although be sure to have plenty of headache pills and a couple of belts of the hard stuff also helps. It is almost impossible for a professional person to understand the description let alone the Lawyer who wrote it. :)

      --
      There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
    139. Re:Penalties by xtracto · · Score: 1

      No, it is not only prompting. In fact it is something that Microsoft WIndows XP (what I am using now) already does:

      FTF Patent:

      In one embodiment, the tools present a user interface identifying an account having a right to permit a task in response to the task being prohibited based on a user's current account not having that right. By so doing, the user may elevate his or her rights without having to search for or type in an account name.

      It is what happens when you want to install whatever software in XP under non-admin account. XP pops up a dialog (present a user interface) listing the available users, and automatically selecting the administrator account (identifying an account having a right to permit a task).

      After this, the user must write the admin password to execute whatever action.

      Sudo does it in a different way, only requiring the use to type his *own* password I guess to validate that he is not a machine. FWIW I prefer Sudo.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    140. Re:Penalties by Anonymous Coward · · Score: 0

      You are use of the word "You're" is not brilliant.

    141. Re:Penalties by Anonymous Coward · · Score: 0

      Cos you can't make an industry out of mathematicians

    142. Re:Penalties by Anonymous Coward · · Score: 0

      Paula? Is that you?

    143. Re:Penalties by donaldm · · Score: 1

      Occasionally when I try to run a command that requires su privileges on my Kubuntu box, the system prompts me to enter my sudo password.

      Setting up sudo to allow the user to run any task which requires privilege is almost the same of logging in as root. If you are the system admin then you have the root password so sudo is pointless. The idea of sudo is to provide certain users with the ability to run specific "set" tasks requiring elevated privileges without them needing to know the root password. This also means not allowing users to use "sudo" to install, copy, move, remove, edit ... etc as root.

      When people ask for sudo access which would give them full root accerss I politely decline, if they persist then they can put their request in writing and submit it to management to which I will reply to by pointing at the companies' own security policy. If said company does not care then I want in writing for my people to be absolved of any responsibility that may result if there is a stuff-up made by the user.

      I am quite sure I am going to get many people try to point out the advantages of using sudo to install. To which I will reply "rubbish" and I am being polite here. What I have stated still stands. I could concede some more dangerous elevated commands being run under sudo providing a password is required, but not having to provide a password is just plain stupid which is again just like logging in as root.

      It must be noted I am not against sudo if used correctly but I am against setting up in sudo a user that will have full root privileges and especially one where a password is not required (you actually can do this in sudo).

      --
      There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
    144. Re:Penalties by Anonymous Coward · · Score: 0

      Because mathematics is innately true, correct, and unchanging since the beginning of time. The proof was always there to begin with, it was just waiting to be found.

      Software is constantly rewritten to be whatever we want it to be on any particular day.

       

    145. Re:Penalties by Anonymous Coward · · Score: 0

      No, but PolicyKit does.

    146. Re:Penalties by donaldm · · Score: 1

      Using the Lawyer speak or jargon from the patent is meaningless however this "drivel" actually describes in great but muddy detail what sudo can be made to do. Graphical Interface - oh please I could knock one up in about an hour or so using Tk/Tcl. I find this patent so stupid it should be laughed at and I particularly love the part were Microsoft has only gone back to 1998 as if the 1980's did not exist.

      --
      There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
    147. Re:Penalties by ibsteve2u · · Score: 1

      "You need to use sudo to run this program. Would you like to use sudo? y / n"

      Oh, you mean like eeebuntu is always pestering me?

      --
      Orwell: "In a Time of Universal Deceit, telling the Truth is a Revolutionary Act"
    148. Re:Penalties by Anonymous Coward · · Score: 0

      Yeah, and we can conclude that the people inventing negative numbers, fractions and complex numbers were retards since it's quite obvious. No?

      I can see the direct similarities between worms squirming out of the ground due to an electric current and all these mangry posts. No one noticed how mangry you turned when some GPL licenseed code similarities were discovered in some software in win7?

      Make up your minds.

    149. Re:Penalties by daver00 · · Score: 1

      No, mathematics is provably true within a predefined and entirely arbitrary set of rules. We consider those rules (axioms) to be innately true in themselves, but only in a naive and unprovable way. They are 'obvious' if you wish.

      Its actually somewhat similar (read: identical) to computers... since the theories of computing were developed by mathematicians after all.

    150. Re:Penalties by donaldm · · Score: 2, Insightful

      I believe there is a place for software patents, but I also think software patents are vastly over-issued. For some reason patent officials seem to think "on a computer" is not obvious and deserves a patent.

      I respectively disagree. All software is based on "Numerical Analysis" which is a branch of mathematics which in itself can not or should I say "should not" be patentable.

      I also think that if Patents apply to compiled software, copyright should only apply to the source code. If we consider software a "work of art", then it should not be patentable at all.

      For source code it would be better under a License that is enforcible. You can take out a copyright on a suite of software which would effectively prevent people calling their functionally equivalent software the same as yours. Actually the best way to make money from software is to provide support and companies like Redhat and Novel are doing quite well even thought they provide the source for most of their products.

      All software can be considered not only part of mathematics but also a "work of art" especially if there is any graphical output which could be considered copyright and therefore not patentable. An excellent example are "fonts" which can only be protected under copyright but not under patent, however this still allows someone to bring out a font which is functionally equivalent to the copyright font as long as they call said font a different name unless there is an agreement with the copyright holder.

      --
      There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
    151. Re:Penalties by L4t3r4lu5 · · Score: 0

      Again, it's the system. If MS hadn't contested them and they had been found to be infringing at a later date, MS would lose the patents. If the patents are invalid, they're invalid, if they stand, then they have the option of licensing them out.

      You know how if someone sells you a rock that keeps away tigers, and you never get to test it because you never go near tigers? I have a patent on that rock. If someone else makes a rock which does the same thing, I have to challenge their anti-big- cat-rock claim, or I lose the right to be the only person making a rock which stops you getting eaten when walking around safari parks.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    152. Re:Penalties by FireFury03 · · Score: 2, Interesting

      1. Copyright
      2. Licences such as GPL, LGPL, BSD (if you want to give it away), Creative Commons, ... etc

      These things don't protect you from the things patents are _supposed_ to protect you from (namely, someone ripping off your _idea_, rather than your implementation).

      1. Proprietary software. In other words don't publish your code.

      This one will protect your idea, only if it is a hidden subsystem within your product - e.g. an algorithm which is orders of magnitude faster than existing methods of doing that job would be partly protected when integrated into proprietary software since it wouldn't be visible, but a "whole-product" idea such as Amazon's infamous one-click purchase system isn't protected because it is downright obvious how it could be implemented without needing to look at the code.

      Of course, interested parties can still reverse engineer your code anyway.

      I am sure this can easily be added to without resorting to stupid software patents, which IMHO don't contribute to innovation in developing software. The only people that stand to gain from software patents are the Lawyers and patent Trolls.

      On this we certainly agree. IMHO the whole patent system is broken and rarely does anything beneficial to innovation.

    153. Re:Penalties by Anspen · · Score: 1

      I'm not sure I can agree with the abolition of software patents entirely, as copyrights are insufficient in protecting innovation long enough for it to be profitable and there is no other system which ensures a company can recover development costs on truly innovative software.

      There needs to be *something* which protects software developers from having their products ripped off and all their innovative functionality duplicated. Exactly how that *something* should work is best left to people far more expert in the field than me...but before we scrap software patents, we need to provide developers with an alternative.

      I'd argue that almost all software shouldn't fall under software patents because the development cost is the same for the original creators and the competitor copying it. If software maker x comes up with a briljant new app/pug-in/feature software makes y should be free to implement it as wall, as long as they write the code themselves (otherwise they would be making copyright infringement).

      Temporary monopolies through patents are meant to pay you back for the research time and effort, not to simply reward novel ideas. The only situation in software where that really applies would be something like googles search algorithm and the like, where it's possible that the actual algorithm is very simple to copy, while it takes years of research to arrive there.

    154. Re:Penalties by Anonymous Coward · · Score: 0

      this is about geeks who fancy themselves Knuth thinking they ought to be millionaires.

      More likely it's about those who employ geeks thinking _they_ ought to be millionaires.

      1. hire geeks
      2. ???
      3. patent geek's work
      4 profit!

    155. Re:Penalties by Anonymous Coward · · Score: 0

      You're use of the word "genious" is brillant.

      Jesus dude, learn to spell.

    156. Re:Penalties by dougisfunny · · Score: 1

      Even if the patent is for clicking (once) to buy something?

      --
      This is not the funny you're looking for.
    157. Re:Penalties by Paradyme · · Score: 1

      Coders often want to get paid by their PHBs as well. Unless a company can maintain atleast some sort of competitive advantage against the rivals, guess what'll happen to the coders.

    158. Re:Penalties by Anonymous Coward · · Score: 0

      Your use of you're is just as good

    159. Re:Penalties by Anonymous Coward · · Score: 0

      It's not the programmers who want patents, it's companies. And certainly not all companies. Only really large companies benefit from them at all, in the sense they can shut out competition from smaller companies, but have cross-licensing deals with other mega-corporations. It's Mutually Assured Destruction between the super-powers, and sufficient fire-power (or threat of fire-power) to shut down any innovative smaller players.

    160. Re:Penalties by Zordak · · Score: 1

      The "drivel," as you call it, is the only thing that matters as to the scope of the patent. The GUI you "knock up" in about an hour using Tk/Tcl would not infringe the claim unless it had each and every one of those elements. And the fact that you can do something after somebody patents it doesn't say anything about whether the patent is obvious. That's what the patent's supposed to do.

      --

      Today's Sesame Street was brought to you by the number e.
    161. Re:Penalties by Anonymous Coward · · Score: 0

      Get over yourselves programmers, your code is not special

      In my experience, it isn't the programmers who need to "get over themselves", it's the programmers' managers.

      In fact, it happened several times at a company I used to work for -- Programmers wrote something cool; boss got all excited and wanted to patent something.

    162. Re:Penalties by thyarcher · · Score: 1

      Then I want to pose a straightforward devil's advocate question. What is different about what you just described from every other patent in existence? Every patent is a design for a widget. The patent for that widget is a guide/physical steps/algorithm for building that widget. Why does physically moving stuff instead of logically moving information make one patentable and fine and the other "as wrong as it gets"?

    163. Re:Penalties by dkh2 · · Score: 1

      Thank you! This just became one of the random quips in my instance of Bugzilla.

      --
      My office has been taken over by iPod people.
    164. Re:Penalties by pipboy9999 · · Score: 1

      I assume that the logic there would be that the mathematics existed prior to the discovery of it. The Pythagorean theorem is a law of nature governing right triangles, Pythagoras didn't just sit down one day and "invent" an equation that solved for triangle side lengths, he discovered it. On the other hand, if I write a new snippet of code to solve a problem I am having, I invented a solution to the problem.

      --
      Yeah, I've got nothing...
    165. Re:Penalties by Anonymous Coward · · Score: 3, Informative

      You've got it exactly backwards. Patents very specifically do not cover _ideas_. They are absolutely 100% only for implementations.

      It doesn't matter _what_ you build, it matters _how_ you build it.

      The trouble is, that in the software world, many ideas are simple enough that there's really only one or two sensible implementations.

    166. Re:Penalties by Vetruvet · · Score: 1

      There's already a sudo with a GUI (in Linux w/KDE): kdesu I'm not sure about GNOME, but I would think it has something similar Honestly, I hate when M$ tries to patent trivial shit. It's like saying: "I'm going to go patent J-PB-J sandwich, because I used jelly twice!".

    167. Re:Penalties by daver00 · · Score: 1

      Well my original comment where I said basically this was on reddit in response to a guy who seemed to be striking out on his own. He was a programmer, and he had it in his head that because he sunk so much time and personal funds into his code, it was special. Hell maybe it is special. I still don't agree with patent protections on it.

    168. Re:Penalties by wtfamidoinghere · · Score: 1

      And that's EXACTLY why software patents are wrong and insane! A patent without full disclosure is not a patent, does not benefit society and innovation in exchange for the limited monopoly, and since full disclosure would break any sense in patenting software...

    169. Re:Penalties by illumin8 · · Score: 1

      And actually I haven't ever seen MS patent trolling, they've even gave their patents to organizations which purpose is to keep them open.

      This is demonstrably false. Microsoft has used the threat of patent litigation to keep large customers away from Linux. Microsoft has hinted publicly and through deals with partners like Novell that Linux infringes on patents, which are never specified, in order to give companies using or considering Linux fear of patent litigation. This is the very definition of patent trolling. They've only sued Tom Tom so far, but they use their patent arsenal as a weapon.

      Patents are like nukes, even the threat of using them carries a lot of force.

      --
      "When the president does it, that means it's not illegal." - Richard M. Nixon
    170. Re:Penalties by jthill · · Score: 1

      Now, there's a clever idea: patch sudo to do an automatic union-mount. Sapir-Whorf security: you can't execute what's not in your namespace.

      You should patent it, of course.

      --
      As always, all IMO. Insert "I think" everywhere grammatically possible.
    171. Re:Penalties by mcgrew · · Score: 2, Funny

      Sometimes an application tries to do something whilst running under a non-privileged account. If an application tries this we could use [magic] to interrupt the process and present a dialogue allowing a user to assume permissions of another account which we know has appropriate permissions [by magic]. Alternatively, we could [do magic] to determine if the user can elevate privileges of their own account, and allow them to do so."

      But all your cabbages would explode!

    172. Re:Penalties by MBGMorden · · Score: 1

      A lot of times though sudo is used on single user systems. On my Linux box at home I very much have sudo access with full root privileges because, well, I'm the only user and anything that needs root I need to be able to do, but naturally I don't want to run as root at all times (that's like walking around waving a loaded gun). The simple solution is to use a standard user account that access sudo access to any and everything when needed.

      One thing I can't stand though is Ubuntu's completely locking out the root account all-together. I know better than to run as root always, but there are sometimes when I'm going to be doing a lot when throwing sudo in front of EVERY command is a PITA. In those cases I just want to su to root and do what I gotta. So to get around their nanny-complex I just sudo'd the passwd command to change the root account's password from whatever Ubuntu scrambles it to :).

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    173. Re:Penalties by Java+Pimp · · Score: 1

      sudo bash

      Or your shell of choice... works for me.

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    174. Re:Penalties by MBGMorden · · Score: 1

      Indeed. But su - works just as fine after the previous suggestion too. No harm in there being multiple solutions to the problem :).

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    175. Re:Penalties by paving-slab · · Score: 1

      Sudo does it in a different way, only requiring the use to type his *own* password

      Sudo can be set up to require the password of the account that is using sudo, the password of the account being requested, or no password at all.

    176. Re:Penalties by Kerrigann · · Score: 1

      Yeah, we a better discussion of this further down... my blanket statement here wasn't well justified.

      I have of course had exactly that experience, on both sides, but never something that I felt was patentable. This might be that most of my programming work has been very tightly coupled to mathematics. I feel math shouldn't be patentable, so I never feel that my programming implementation of it shouldn't be, but I understand how someone could feel that way. A good counterexample to what I was saying would be the RSA patent... shorter than most, and very clear on what the novel algorithm is and what it's useful for right up front.

      I should have qualified what I was saying and emphasized *most*. Granted I haven't looked at *that many* patents, but all the ones I've seen are just vague descriptions of what some system looks like at the interface level. There was one that patented... something to do with slot machines that were networked and shared data. They weren't networked in any novel way, the patent didn't describe anything particularly novel they were doing with the data, it just seemed to patent *the idea of having slot machines in a network*.

      That sort of patent doesn't show you how to do something, it just makes a land grab. I think we're in agreement about the USPTO and probably about patents in general, but I shouldn't have made such a blanket statement without qualifying it.

    177. Re:Penalties by Bigjeff5 · · Score: 1

      Permissions elevation in Windows Vista and 7 performs a function very similar to sudo. If MS does not at least try to patent their version of it, it leaves them open to one of the smaller but often nastier Linux patent trolls coming back later and suing the snot out of them.

      So it's a big deal.

      Is it right? That depends, I honestly don't know how the Windows version differs from Sudo in any detail, but at least at the user's end it seems to be a lot more transparent and automatic.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    178. Re:Penalties by Golddess · · Score: 2, Informative

      It doesn't allow for duplication if the result is the same.

      Bullshit.

      In an episode of Modern Marvels about Nikola Tesla I believe it was, they'd mentioned how, since Edison had patented his light bulb, he was able to disallow Tesla from using that design at the World's Fair. So Tesla invented his own florescent bulbs. End result is the same (produce light), yet there was no patent infringement on the part of Nikola Tesla.

      --
      "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
    179. Re:Penalties by Bigjeff5 · · Score: 1

      This is the very definition of patent trolling.

      No, it isn't. Exercising a patent, and warning companies that they may be infringing on a patent is definitely not patent trolling.

      Patent trolling is very simply buying up someone else's patent, waiting for the idea to become popular and widespread, and then suing the pants off anyone and everyone who even might be infringing on the patent. It's a dangerous game, because the longer you wait the more you'll get for the lawsuits, but if you wait too long your patent claim can become nullified due to lack of action.

      THAT is patent trolling, and that is not what MS does. Patent trolls don't even attempt to license their patents, or if they do it is at extortionary rates. Microsoft does try to use patents to gain competitive advantage, and you can see that as dirty tactics if you want to, but that's not patent trolling. They only actually seem to sue when their patent is threatened - as in the Tom Tom case. In case you missed it, Tom Tom refused to license the patent MS had which they infringed upon. It was not only their right to sue, if they had NOT sued they would have lost the right to sue in the future.

      Chances are the reason MS only threatens to sue Linux companies and never actually sues them is because they have waited far to long for most of the patents they use to be upheld. All they would be doing is destroying business partners. By not suing, and allowing the threat to hang there, they get to cajole and coerce their partners instead. It's much more advantageous to them than becoming a patent troll - patent trolls are bottom feeders, and legitimate companies only resort to it when they are dieing.

      I know you wish patents somehow meant you could never sue, but there are legitimate reasons for suing for patent infringment, namely when someone infringes on your patent! Duh!

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    180. Re:Penalties by alexborges · · Score: 1

      Zordak, my MS defending friend, it is very simple.

      In Linux/BSD/Unix there have been tons and tons and tons of UI's to accomplish each and every one of the claims of this patents.

      From PolicyKit, to SELinux/AVP and the redhat stuff, to sudo/gksudo.

      This patent is SHIT and an obvious attempt, again, to fuck us over. We shouldn't just stare at the guy kicking dirt on our face.

      --
      NO SIG
    181. Re:Penalties by PalmKiller · · Score: 1

      And you are saying the state machine (simple computer) does not exist in nature? And is DNA not analogous to a program? How do you know that the solution to your problem was not solved in some analogous form so by the same argument of pre-existance, do we really have the right to patent code?

    182. Re:Penalties by Bigjeff5 · · Score: 1

      End result is the same (produce light)

      You cannot patent light, dumbass. Else the Sun is prior art. Light is not the product (i.e. the thing you produce and sell), the lightbulb is, and Tesla's bulb was vastly different than (and in many ways superior to) Edison's.

      I don't think you know very much about lightbulbs (I don't either, but obviously a lot more than you do), see Edison's bulb was what they call an incandescent bulb. Big word I know, but it operates by passing electrical current through a tungsten fillament. The fillament is high-resistance, so when that resistance is overcome it gets very hot and glows brightly, giving off light. Note that the reason most incandescent bulbs are round is because in order to extend the life of the fillament it needs to be set inside a vacuum to prevent oxidization (they burn out super quick without it).

      Flourescents are more complicated. A glass tube is filled with an inert gas of some type, lots of current is pumped in, some magic happens (sorry, I don't know nearly as much about flourescents off the top of my head), the inert gas becomes charged, conducts electricity, and becomes a plasma. Plasma glows quite brightly, thus, we have light.

      Just so we are crystal clear, you CAN NOT PATENT LIGHT. But you CAN and DO patent LIGHTBULBS. Mmmkay?

      (sorry, I'm apparently grumpy this morning)

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    183. Re:Penalties by NotBornYesterday · · Score: 2, Funny

      Thanks! My day isn't complete until I've pissed off an AC.

      --
      I prefer rogues to imbeciles because they sometimes take a rest.
    184. Re:Penalties by kbeyer · · Score: 1

      sudo bash

      Or your shell of choice... works for me.

      sudo su -

      if you also want to get root's environment...

    185. Re:Penalties by Golddess · · Score: 1

      It seems I may have misunderstood what you meant by "the result is the same". You're referring to "produce the same product", right? Because I was originally treating that as "produce a different product which performs the same function". I know that the incandescent bulb and the fluorescent bulb produce light via different methods, but their function is the same.

      --
      "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
    186. Re:Penalties by JLF65 · · Score: 1

      If MS hadn't contested them and they had been found to be infringing at a later date, MS would lose the patents.

      Wrong. You're thinking of trademarks. Patents don't have a "defend it or lose it" clause. That's the very essence of submarine patents - file a patent, keep quiet, wait until a bunch of people are using it, then BAM!! Surface and file a bunch of lawsuits.

    187. Re:Penalties by umdenken · · Score: 1

      ...I haven't ever seen MS patent trolling, they've even gave their patents to organizations which purpose is to keep them open...

      I'm not buying it. I know personally that Microsoft keeps patents as an arsenal for negotiations with small companies. I.e., if you continue such-and-such development, we'll challenge every patent you've got; we'll get some of them thrown out, and bankrupt you in the process. (I'm a 3rd year law student; one of my best friends is a patent agent in a firm that represents MS and tells me these stories about "business as usual".)

    188. Re:Penalties by Creepy · · Score: 2, Interesting

      Actually, it is a little beyond that, otherwise it would be identical to what Apple has done since MacOS X.0. What this does different is bring up a dialog box WITH USERS that can run the application, and you can select one of those to run the app as instead, if you know the password. In a UNIX-like system this is worthless because you may have hundreds or thousands of users, but most desktop windows systems only have a handful of users at most.

      In fact, I don't think Linux (or UNIX for that matter) could even do this if it wanted to, or it'd be very ugly - it would have to check the sticky bit (and other special bits), then user, group, and role for all users to generate that list. Windows uses an ACL (Access Control List). Macs (since Tiger) and some UNIX/UNIX-likes support both UNIX permissions and ACLs which just compounds the mess. ACLs have a bit more flexibility than the UNIX bits - for instance, I could assign multiple groups and users not in those groups access permissions. I also don't have to edit /etc/passwd to do it (a root owned file) if I want to share a file with several users and don't have a container group.

    189. Re:Penalties by adamdoyle · · Score: 1

      Edison's Patent is listed as "Improvement in Electric Lights." I read some of it, and it appears as though he just modified existing light bulbs in a way that kept the filament under the melting point. (which I guess makes it more efficient and helps it last longer)

      He didn't invent the lightbulb... he invented a practical lightbulb that lasts long enough for it to be usable. He IMPROVED an existing patent which warrants a new patent in itself.

      So, to summarize, patents keep people from copying functionality. The lightbulbs before Edison's were unreliable so Edison's lightbulb had new functionality. It produced light and did it effectively. That second component ("did it effectively") is the new functionality.

    190. Re:Penalties by hazah · · Score: 1

      While I agree with your sentiment, I whole hardheartedly disagree with the premise that code is anything like mathematical formula. On the surface of it, code is based on mathematical notation, but it expresses concepts in a very different context. It is like the difference between physics and architecture. Physics are physics, you can figure them out, or not comprehend them, but they are what they are. Architecture is based on physics in a very real sense. But you can't "figure out" architecture, its a matter of taste combined with what works, mixed in with tricks of the trade learned so far along with "accepted (in your area) best practices".

    191. Re:Penalties by rcblach · · Score: 1

      I would like to make this comment, all interfaces are graphical, or picto-graphs
      this is because writing is pictorial. Just look at cuneaform writing,or Japanese, Chineses block letters.

      All letters are pictures, personally I dont see the difference between graphical and written, because they are all pictorial,
      just in different fashions.

      In the end analysis, a computer does not know the difference.

      This is not a new idea.

    192. Re:Penalties by adamdoyle · · Score: 1

      actually, according to wikipedia, the improvements were: better vacuum, better incandescent material, and then the one I cited (kept under melting point).

      but that doesn't change my argument - it was still improved enough for it to be useful. A usable lightbulb (when contrasted with an unusable lightbulb) is patent-worthy, even if the original lightbulb is already patented. The fact that it's now usable is the "new functionality."

    193. Re:Penalties by MrResistor · · Score: 1

      No, you are the one who has it backwards, and those who modded you Informative should be ashamed of themselves.

      Patents cover the idea, which is why you can have a patent that does not describe a particular implementation.

      In software, implementation is covered by copyright.

      If you have a patent, I cannot implement the idea you patented regardless of how different my implementation is, even if you have no implementation at all. If you don't have a patent, I just have to make sure all the code I use I have legal rights to.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    194. Re:Penalties by krenaud · · Score: 1
    195. Re:Penalties by mcguirez · · Score: 1

      I did indeed. Nazi greengrocers.

      --
      When you hear hoofbeats, think horses, not zebras
    196. Re:Penalties by DaVince21 · · Score: 1

      Rather than hate, a misunderstanding on the patent has been widely spread and is now being believed by a lot of people to be true, causing any possible hate.

      I'm glad the article got red-marked or however you call it, but plenty of people won't notice that or won't believe the people who are saying what the article is making you believe isn't actually true.

      --
      I am not devoid of humor.
    197. Re:Penalties by oji-sama · · Score: 1

      Unfortunate but true.

      --
      It is what it is.
    198. Re:Penalties by MrResistor · · Score: 1

      The fact that it's now usable is the "new functionality."

      ... and I'm pretty sure that would be Microsoft's justification for this patent. I seriously doubt that MS is unaware of the existence of sudo, though they may be unaware of sudo guis that have this functionality (I certainly was unaware of them, but then it wasn't something I had any interest in either).

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    199. Re:Penalties by adamdoyle · · Score: 1

      I seriously doubt that MS is unaware of the existence of sudo

      well considering the fact that the "references" section at the bottom of the patent listing actually linked to sudo manuals and other sudo references... I would say they are definitely aware of the existence of sudo.

    200. Re:Penalties by drsmithy · · Score: 1

      THAT is patent trolling, and that is not what MS does. Patent trolls don't even attempt to license their patents, or if they do it is at extortionary rates.

      Most significantly, patent trolls rarely - if ever - have an actual product in the market that leverages the patent.

    201. Re:Penalties by HermMunster · · Score: 1

      How is this different than making a car? A patent can stop that too.

      --
      You can lead a man with reason but you can't make him think.
    202. Re:Penalties by daver00 · · Score: 1

      I explicitly stated that mathematics is not formulas and I am not talking about mathematical formulas. I am talking about logical procedures and the reasoning behind them. Constructive proofs are no different from an algorithm, in fact that is where mathematical algorithms are born, they are the same thing.

    203. Re:Penalties by True+Grit · · Score: 1

      Unless a company can maintain atleast some sort of competitive advantage against the rivals, guess what'll happen to the coders.

      If companies didn't have to worry about building up defensive patent portfolio's they could let their coders spend more time... well... coding. And maybe, just maybe, they could even pay their coders more, since they won't need to waste millions on patent lawyer fees.

      Without patents, a software company's 'competitive advantage' will swing back to the *coders* themselves, what it arguably should have been all along, if not for the lawyers sidetracking everyone with their patent violations, copyright violations, trademark infringements, EULAs, DRM, etc, etc, but certainly the software patent madness is the worst of their monstrous creations. All of that stuff is about control: locking someone in, or locking someone out, its not about competition.

      Its only the patent lawyers who want you to think that gaming the legal system qualifies as a valid (as in creative/useful to society at large) way of gaining 'competitive advantage'. After all, software patents are inherently anti-competitive by their very nature.

      The rest of us would prefer this game a lot better if it were left up to the coders themselves, by letting the best *coder*, rather than the best lawyer, win...

    204. Re:Penalties by L4t3r4lu5 · · Score: 1

      Apologies, quite right.

      Perhaps I should preface every post with IANAL :D

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    205. Re:Penalties by SL+Baur · · Score: 1

      In fact, I don't think Linux (or UNIX for that matter) could even do this if it wanted to, or it'd be very ugly - it would have to check the sticky bit (and other special bits), then user, group, and role for all users to generate that list.

      The traditional Unix way to limit access to an executable is via group permissions and turning off all world permissions. Conceptually, this isn't any different than an ACL, except that modifying members of a group requires administrative access.

      Ancient versions of Unix (System V and older) only allowed a user to be in a single group at a time. That was fixed decades ago.

      The sticky bit on an executable, a hint to keep the executable in memory when the program exits, hasn't worked that way for just about as long.

    206. Re:Penalties by supernova_hq · · Score: 1

      You're telling me. I live in Canada. Thanks to that *@#@*$ international patent law, Canadians are not allowed to patent software (good), but we still have to abide by software patents given to Americans (WTF).

    207. Re:Penalties by Drinking+Bleach · · Score: 1

      sudo -i

    208. Re:Penalties by PenisLands · · Score: 0

      What about when Microsoft threatened that Linux infringed on MS intellectual property? That's trolling if I ever saw it.

    209. Re:Penalties by Creepy · · Score: 1

      that's for sticky bit on a file; on a directory it has a different meaning (like /tmp - a user or superuser can write to or remove files there but other users can't if that file exists)

      UNIX file permissions are good for most situations, but do contain some issues:
      1) groups don't nest
      2) you can't add a mix of users and groups
      3) you can't have groups with different permissions (say read and execute on one and read, write, and execute for another).
      4) you can't have multiple users that own a file
      5) no way to have cascading permissions (if this condition then add write, if this condition add read, etc).

      For instance, you're a teacher and have two TAs and four groups of students. You want to give the TAs read access to everything in the directory, read and write access to the grade file and only give the students write access to create new files in the directory and read access to their own files. After grading, you want to initially allow the students to see the other students in their group's work but not the other groups and later allow all groups to see each other's work (e.g. you wouldn't want a group to see the other group's work before they had their class).

      ACLs can also key off of other attributes of the file - for instance, you could key off creation date or filesize or even multiple attributes - for instance, the user is the creator but no longer in the group, remove write permission.

  2. claims by sopssa · · Score: 5, Informative

    As usual, you need to look at the claims of the patent. For example these points dont really cover sudo:

    1. One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to present a user interface in response to a task being prohibited based on a user's current account not having a right to permit the task, the user interface comprising: information indicating the task and an entity that attempted the task; a selectable help graphic wherein responsive to receiving selection of the selectable help graphic, the computer-readable instructions further cause the computing device to present the information; identifiers, each of the identifiers identifying other accounts having a right to permit the task, wherein the identifiers presented are based on criteria comprising: frequency of use; association with the user; and indication of sufficient but not unlimited rights; one of the identifiers identifies a higher-rights account having a right to permit the task, wherein the one of the identifiers comprises: a graphic identifying the higher-rights accounts associated with the user; and a name of the higher-rights account; an authenticator region capable of receiving, from the user, an authenticator usable to authenticate the higher-rights account having the right to permit the task, wherein: the authenticator comprises a password, and the authenticator region comprises a data-entry field configured to receive the password.

    2. One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to perform acts comprising: determining multiple accounts capable of permitting a task not permitted by an account of a current user wherein the determining is based on criteria comprising: frequency of use; association with the current user; and indication of sufficient but not unlimited rights; receiving indicators for the multiple accounts capable of permitting the task; presenting a graphical user interface, the graphical user interface having: multiple account regions, each account region identifying one of the multiple accounts capable of permitting the task; an authenticator region capable of receiving an authenticator for one of the multiple accounts capable of permitting the task; receiving, through the graphical user interface, the authenticator for one of the multiple accounts capable of permitting the task; and responsive to receiving the authenticator for one of the accounts capable of permitting the task, packaging, into a computer-readable package, the received authenticator and the account capable of permitting the task associated with the authenticator, the package effective to enable authentication of the account capable of permitting the task.

    3. The media of claim 2, where the each account region comprises a name identifying one of the multiple accounts capable of permitting the task.

    4. The media of claim 2, where the each account region comprises a graphic identifying one of the multiple accounts capable of permitting the task.

    5. The media of claim 2, further comprising permitting the task.

    6. The media of claim 2, further comprising authenticating the account capable of permitting the task and, responsive to authenticating the account capable of permitting the task, temporarily elevating rights of the current user to that of the account capable of permitting the task effective to permit the task.

    7. The media of claim 2, wherein rights of the account of the current user are limited by controlled-access software.

    8. The media of claim 7, wherein the task is prohibited by the controlled-access software prior to authentication of the account capable of permitting the task and wherein the controlled-access software refrains from prohibiting the task in response to authentication of the account capable of permitting the task.

    9. One or more computer-readable media having co

    1. Re:claims by plasmacutter · · Score: 1, Insightful

      The person analyzing this for groklaw is a lawyer well seasoned in tech and IP litigation, and disagrees with you.

      Funny how you also don't provide the analysis into common english.

      It's sudo with a gui, in other words: what macos does when you try to modify files in the system folder, or gksudo in linux.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    2. Re:claims by greensoap · · Score: 1

      No mod points, so I just wanted to say thank you to the parent. Those claims do not cover sudo. Congratulations to the OP on using scare tactics to get to the front page os /. Well played good sir, well played.

    3. Re:claims by alexborges · · Score: 1

      We call that "SELINUX".

      GFYS.

      --
      NO SIG
    4. Re:claims by CannonballHead · · Score: 1

      The person analyzing this for groklaw is a lawyer well seasoned in tech and IP litigation, and disagrees with you.

      That's the argument politicians use for why they know better than I do what I want ;)

    5. Re:claims by sopssa · · Score: 1

      Groklaw article is saying that Microsoft is filing this patent to collect a toll from Linux community for sudo. But there is no case, since if the patent would collide with sudo it would itself be invalid, because sudo has been around since like 1980.

      Again the claims do not fully overlap with sudo (or gui's that use it). Every claim has to collide for there to be a case.

    6. Re:claims by Halo1 · · Score: 5, Informative

      Remember that they all have to apply.

      No, they don't. Only one independent claim (i.e., 1, 2 or 9) has to apply (at least it's like that in Europe), or an independent claim along with some dependent claims if you want a stronger case because then the claims become more specific and hence hopefully more distant from the prior are (e.g., 2 and 3, or 2 and 7 and 8).

      This isn't exactly sudo.

      That's true. It's still a crappy patent application though, since it basically covers showing a password dialog box with eligible user accounts (along with some details about their associated privileges) when an operation requires elevated privileges.

      --
      Donate free food here
    7. Re:claims by Sockatume · · Score: 1

      I don't think that the following, the author's only analysis of the claims of the patent, is really an air-tight disassembly of its value:

      "Etc. blah, blah. Dude. It's sudo. With a gui. Sudo for Dummies. That's what it is. Software and patents need to get a divorce, before all the geeks in the world either stop coding in disgust or die laughing."

      --
      No kidding!!! What do you say at this point?
    8. Re:claims by Victor_0x53h · · Score: 1

      Is there a grammar or patent-writing rule prohibiting numbered points from containing more than one period? I wonder if this has anything to do with blanket approvals.

    9. Re:claims by jpmorgan · · Score: 2, Insightful
      Apparently the author at groklaw either doesn't understand patents, or doesn't understand the technology. Look at the very first claim:

      One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to present a user interface in response to a task being prohibited based on a user's current account not having a right to permit the task, the user interface comprising: information indicating the task and an entity that attempted the task; a selectable help graphic wherein responsive to receiving selection of the selectable help graphic, the computer-readable instructions further cause the computing device to present the information; identifiers, each of the identifiers identifying other accounts having a right to permit the task, wherein the identifiers presented are based on criteria comprising: frequency of use; association with the user; and indication of sufficient but not unlimited rights; one of the identifiers identifies a higher-rights account having a right to permit the task, wherein the one of the identifiers comprises: a graphic identifying the higher-rights accounts associated with the user; and a name of the higher-rights account; an authenticator region capable of receiving, from the user, an authenticator usable to authenticate the higher-rights account having the right to permit the task, wherein: the authenticator comprises a password, and the authenticator region comprises a data-entry field configured to receive the password.

      Emphasis mine. Sudo does not do this. Thus, this patent does not cover sudo. Fini.

    10. Re:claims by Adrian+Lopez · · Score: 4, Insightful

      Oh no, I've gone cross-eyed.

      According to patent law, the above example of murder-by-verbiage is supposed to help third-parties implement the invention described, but the language employed is clearly designed to accomplish the exact opposite. I think it's time to put the patent system out of its misery.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    11. Re:claims by plasmacutter · · Score: 1

      I don't think that the following, the author's only analysis of the claims of the patent, is really an air-tight disassembly of its value:

      "Etc. blah, blah. Dude. It's sudo. With a gui. Sudo for Dummies. That's what it is. Software and patents need to get a divorce, before all the geeks in the world either stop coding in disgust or die laughing."

      The whole point of a lawyer's interpretation of patents, contracts, or legal text is to make it understandable. That's exactly what is done.

      Going through line-by-line analysis will lose most of the readership and defeat the purpose.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    12. Re:claims by Sockatume · · Score: 1

      Such a response doesn't render it understandable, it simply returns an opinion. It's the equivalent of pointing at a rock and going "SHIT FALLS DOWN" as an attempt to render gravity understandable.

      --
      No kidding!!! What do you say at this point?
    13. Re:claims by Anonymous Coward · · Score: 0

      Emphasis mine. Sudo does not do this. Thus, this patent does not cover sudo. Fini.

      The part you added emphasis to is:
      in response to a task being prohibited based on a user's current account not having a right to permit the task

      That is exactly how it works. gksudo at least, and whatever they call the sudo gui in OS X.

      Double click an administration app that needs root, but under a user account.
      Oops! There comes your gksudo dialog, from noticing that the app requires root and that you are not root, and asks for a password (Or just gives an ok/cancel button if password caching is on), and then behind the scenes runs the app again under sudo.

      I fail to see how that example is not running sudo in response to a task being prohibited based on a user's current account not having a right to permit the task

    14. Re:claims by plasmacutter · · Score: 2, Informative

      cause the computing device to present a user interface in response to a task being prohibited based on a user's current account not having a right to permit the task

      macos x does this

      gksudo does this

      This patent covers material which has been present in linux and macos X and is part of the evolving function of sudo. Fini.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    15. Re:claims by jedidiah · · Score: 1

      This seems to be an implementation of the sudo "concept" for the Windows
      security model. If they are allowed to get a patent on this, this basically
      means that any CIS undergrad that can cook up their own solution can be sued
      for doing so and using the results of their own intellect.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    16. Re:claims by Xiaran · · Score: 1

      While Ill agree with you about sudo I would point out that many GUI systems including Linux and OS X *do* present a GUI when attempting to execute a task that requires higher permissions.

    17. Re:claims by sopssa · · Score: 1

      That is exactly how it works. gksudo at least, and whatever they call the sudo gui in OS X.

      Double click an administration app that needs root, but under a user account.
      Oops! There comes your gksudo dialog, from noticing that the app requires root and that you are not root, and asks for a password (Or just gives an ok/cancel button if password caching is on), and then behind the scenes runs the app again under sudo.

      I fail to see how that example is not running sudo in response to a task being prohibited based on a user's current account not having a right to permit the task

      Do we have to go down the list of every claim now? What about this one thats under it

      identifiers, each of the identifiers identifying other accounts having a right to permit the task, wherein the identifiers presented are based on criteria comprising: frequency of use; association with the user; and indication of sufficient but not unlimited rights;

      Does gksudo or OS X do this? Because it has to apply as well.

    18. Re:claims by jpmorgan · · Score: 5, Informative

      Except, gksudo doesn't come up in response to a failed security authentication. gksudo comes up because the control panel knows it needs administrator permissions and explicitly calls gksudo. gksudo is not sitting around behind the scenes, watching for authentication failures.

    19. Re:claims by wytcld · · Score: 4, Insightful

      Where's your analysis of the degree to which this "isn't exactly sudo"? It's pretty damn close. If it comes down to the degree of "exactly," please provide some examples from patent case law that show that the degree of difference here is sufficient for the two programs not to be close enough to the same that sudo, had it been invented after this patent, wouldn't violate said patent.

      I'm nothing like a patent attorney. But my understanding is that if someone invents a special right-angle shovel, and patents it, you're going to be in trouble even if your shovel head is only at an 80 degree angle rather than 90 degrees. If not at 80, certainly at 89.

      Besides, this patent ends with language claiming that the method of implementation is only the preferred one, while the patent covers other methods of implementation of the same underlying concept. And in which sense is the underlying concept even a few degrees different from what sudo does? Your analysis?

      --
      "with their freedom lost all virtue lose" - Milton
    20. Re:claims by jpmorgan · · Score: 1

      Presenting a GUI when attempting to execute a task that requires higher permissions, is not in response to a task being prohibited. gksudo in Linux is used proactively and explicitly by the control panel. This patent covers reactive and automatic elevation based on software behavior.

    21. Re:claims by xenocide2 · · Score: 1

      gksudo does not do this. It's literally a GTK frontend to sudo. If you try to do something via gui that fails, gksudo will not suddenly run and ask you for prompts.

      There are existing systems that do do this, like update-manager and PolicyKit.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    22. Re:claims by jack2000 · · Score: 1

      For the kind of people that run the patent system that really is understandable...:[

    23. Re:claims by tinkerghost · · Score: 1

      in response to a task being prohibited based on a user's current account not having a right to permit the task

      Emphasis mine. Sudo does not do this. Thus, this patent does not cover sudo. Fini.

      This is a patent on using a custom error handler as a wrapper to call sudo, so you're right: it's not sudo. On the other hand, using existing tools for what they are designed for isn't supposed to rise to the level of patent-ability.

    24. Re:claims by Shagg · · Score: 1

      Have you used any recent versions of Linux (within the last several years at least)? Login to the GUI as a regular user, click on something that needs root permissions, you get a popup box warning you and also requesting the root password. It's basically the exact same thing as this patent.

      --
      Unix is user friendly, it's just selective about who its friends are.
    25. Re:claims by nine-times · · Score: 1

      So if you change/drop any of the elements of this patent, is it not covered? Like if you don't have identifiers indicated other accounts having the right to permit the task, but you have the rest of it, can you say, "Sorry Microsoft, but your patent doesn't cover my implimentation."?

    26. Re:claims by digitig · · Score: 1

      The person analyzing this for groklaw is a lawyer well seasoned in tech and IP litigation, and disagrees with you.

      Funny how you also don't provide the analysis into common english.

      It's sudo with a gui, in other words: what macos does when you try to modify files in the system folder, or gksudo in linux.

      It's sudo with a GUI, but it specifies features of the GUI that I've not seen on Linux (not that I'm much of a Linux guru). Yes, when I try to do something beyond my privs I might get a dialog offering to sudo, mut the Microsoft patent also seems to say that the dialog will actually offer the names of logins that do have the required privs, based on frequency of use and whether they're associated with the current user. that's something I've not seen. Not something I especially want to see either, but it suggests something more novel than a simple sudo GUI,

      --
      Quidnam Latine loqui modo coepi?
    27. Re:claims by jpmorgan · · Score: 1

      I have no clue what OS X does, but gksudo does not. gksudo is just a graphical front end, it does not come up "in response to a task being prohibited based on a user's current account not having a right to permit the task." gksudo is in some instances called proactively and explicitly by certain programs (like gnome control center windows). But it does not transparently operate behind the scenes, elevating programs based on OS level privilege failures, as this patent describes. You are confusing proactive and explicit use with reactive and automatic use, as the patent covers.

    28. Re:claims by Anonymous Coward · · Score: 0

      Lawyer talk. IRIX had this behaviour in the package manager ages ago (start package manager unprivileged, dialog requesting root password). Red Carpet has this for some time now.

      Same difference, ridiculous patent.

    29. Re:claims by jpmorgan · · Score: 1

      I never said it was worthy of a patent. Whether it is or not, it does not cover sudo or gksudo.

    30. Re:claims by tomhudson · · Score: 4, Insightful

      Adding a GUI is no more "creative" and "non-obvious" than adding "on the Internet".

      Then again, it might be non-obvious to Microsoft. Does anyone remember if Microsoft XENIX had a sudo equivalent? It would be nice to use something from them from a quarter-century ago as prior art.

    31. Re:claims by TigerNut · · Score: 3, Informative
      Remember that they all have to apply. This isn't exactly sudo.

      Not correct. Of the claims you listed, 1, 2, and 9 are independent claims and can stand alone. A competitive product that incorporated just the elements of, say, claim 9, would violate this patent. A prior art product that included the elements of claim 1 would invalidate claim 1 as an independent claim, but not necessarily the combinations of claim 1 and claim 13 or claim 1 and claim 14. Unless the dependent claims 13 and 14 were subsequently judged to be obvious in light of the earlier product that demonstrated claim 1.

      To an aggressive patent prosecutor, "exactly" has nothing to do with it. The approach is "We've got this patent, see? Pay us the money or we'll sue until you're out of business".

      --

      Less is more.

    32. Re:claims by maxfresh · · Score: 1

      Yes, there's a patent-claim writing rule that says that each claim must be expressed in exactly one sentence, of whatever length and complexity necessary to completely express the claim.

      Quote: "Eachclaimbeginswithacapitalletterandendswitha period.Periodsmaynotbeusedelsewhereintheclaimsexcept for abbreviations."

      Source: Manual of Patent Examination and Procedure (MPEP) Section 608.01(m)

    33. Re:claims by Anonymous Coward · · Score: 0

      this should not be patentable and isn't in other countries. What's next? Copy all existing patents but specify that the the user has to be wearing pants?

    34. Re:claims by tiocsti · · Score: 1

      Except, gksudo doesn't come up in response to a failed security authentication. gksudo comes up because the control panel knows it needs administrator permissions and explicitly calls gksudo. gksudo is not sitting around behind the scenes, watching for authentication failures.

      Pretty much this. A closer comparison to these patent claims would be openbsd's systrace w/ priv escalation, rather than sudo. Even that's not quite the same thing, though, and is primarily designed for a different purpose. They key behind this patent seems to be that the application does not need to be sudo-aware, and invoke it explicitly -- and it just happens passively as a result of a failure due to permissions.

      Also, in the patent apps references section, they call out gksudo, sudo, and several other unix tools that are similar to this if you only read the abstract.

    35. Re:claims by Theaetetus · · Score: 1

      According to patent law, the above example of murder-by-verbiage is supposed to help third-parties implement the invention described, but the language employed is clearly designed to accomplish the exact opposite. I think it's time to put the patent system out of its misery.

      No, it isn't. According to patent law, the above murder-by-verbiage is supposed to identify, in a way that is legally clear and unambiguous exactly what the scope of the claims cover. The specification - the pages of descriptions, examples, and drawings - are what are supposed to help third-parties implement the invention.

      Basically, the specification is for disclosure purposes to teach the world about the innovation. The claims are to help lawyers and judges identify exactly what is covered for purposes of infringement suits. Don't worry that they're difficult to read - they're supposed to be as exact and specific as a contract or a license agreement, because they're carefully defining rights. This usually results in a lot of language.

    36. Re:claims by Anonymous Coward · · Score: 0

      I think PolicyKit does this, anyway, and that's been available for a while, in that it allows you to define what rights specific users or all users can have. I can define privileges on a per-application basis (if they require PolicyKit authorisation), can define default privileges on a per-application basis and can override the default on a per-user basis. If I understand correctly, this is what that section of the patent is attempting to patent, and it already exists.

    37. Re:claims by VisceralLogic · · Score: 1

      However, OS X does do what GP means. For example, If logged into my user account I try to delete a file owned by root, I get a dialog pop up asking me to enter my password to authenticate as administrator in order to perform this action.

      Of course, it doesn't have to determine what potential user can do this, since administrator can do anything, so it's not exactly the same as the MS patent.

      --
      Stop! Dremel time!
    38. Re:claims by Adrian+Lopez · · Score: 1

      Can you point out the text in the patent claim that makes a distinction between a gksudo-type program that is executed on demand by an application requiring greater privilege and a UAC-type module that is executed automatically by the operating system? It seems to me the patent would cover gksudo when invoked by an application that knows it doesn't have the necessary rights to perform an operation, but perhaps there's something I've missed?

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    39. Re:claims by Anonymous Coward · · Score: 0

      You need to consider the claim in its entirety: they claim telling the user what alternative accounts are permitted to perform the operation that is not permitted to the current account. That is not present in su, sudo ksudo etc.

    40. Re:claims by tomhudson · · Score: 1

      identifiers for rights? Try ls -l and you'll see something like drwxrwxrwx, defining a mask of all, group, and individual user rights to read, write, or execute (or in the case of directories, cd into).

      association with the user? right there - the user # (though ls translates it into the user name if it's available).

      frequency of use? Not really needed, but sure - acl logging (acl == access control list). As well as ctime (creation time), mtime (modification time) and atime (last access time - you should disable this if yo want a faster system, or leave it enabled if you want to monitor when a file was last accessed).

      In other words, it's all there. Nothing original or groundbreaking.

    41. Re:claims by Anonymous Coward · · Score: 0

      gksudo is just a front end for sudo, which has a configuration file, /etc/sudoers, in which users and groups who have the rights to run certain programs are listed. You can make the rules pretty complicated, in fact.

    42. Re:claims by mea37 · · Score: 1

      The part that says that the instructions cause X, Y, and Z to happen in response to an authorization failure, along with the lack of any part that says the instruction cause X, Y, and Z to happen in response to being specifically asked to do so by the user and/or another program.

    43. Re:claims by Xiaran · · Score: 1

      I think I and other in this thread are not quite getting what you are saying. It has been said before. In both OS X and Linux if you attempt to do something that requries elevated permissions you will be prompted with a GUI thing. In OS X you will be promted with a box say are you sure(if you have not set up a root account) and a box asking for the root password(if you have). In say ubunut if I run the synaptic package manager to install new software I will be gui proimpted for a password to authorise this.

      Can you please explain why this is different than the patent?

    44. Re:claims by Adrian+Lopez · · Score: 1

      Where does the patent say the "response to authorization failure" can't be handled directly by the application that requires greater privilege? Whether the OS invokes the authorization GUI or the application does, it's still "in response to an authorization failure".

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    45. Re:claims by jim_v2000 · · Score: 1

      Nonsense. PJ at Grocklaw can't read worth shiat. Here's the crux of the patent right here:

      "In one embodiment, the tools present a user interface to a user whereby the user may elevate his or her rights without having to search for or type in an account name. This user interface may be presented in response to a request to perform a task requiring a right not permitted by the user's current account. In some cases, for example, the tools determine which accounts have rights sufficient to enable a user to perform a task not permitted by a user's current account. The tools may then present these accounts and enable the user to select and submit an authenticator for one of these accounts. "

      If you don't have rights to perform an action, and your account doesn't have rights elevation privileges (e.g. you aren't in the sudoers file), then the OS will pop up a window that shows an account that DOES have the correct rights that you can type the password into if you know it. As far as I know, sudo doesn't automatically find a different user's account for you to log in with, so if you're account isn't in the sudoers file, you're screwed. And you could use su, but you'd still have to know that account name.

      --
      Don't take life so seriously. No one makes it out alive.
    46. Re:claims by Anonymous Coward · · Score: 0

      No, they DON'T all have to apply. ANY of them applying causes an infraction. That's why there's usually some extremely general claims weaseled in there.

      The real problem is the stupidity of the people in the Patent Office. The whole system should be abolished, there's no way to fix the mess they've made.

    47. Re:claims by jim_v2000 · · Score: 1

      It's only because you didn't take the time to read the patent. It's not patenting the sudo functionality. It's patenting a system that displays an account with the proper rights automatically. Sudo doesn't do that, and sudo only can use your account, not someone elses.

      --
      Don't take life so seriously. No one makes it out alive.
    48. Re:claims by jim_v2000 · · Score: 1

      So gksudo and OS X will show you the name of a user with sufficient privileges automatically if your account does not have sufficient privileges? Because as far as I know, OS X and sudo simply as you to put in your password, not the password for another account.

      --
      Don't take life so seriously. No one makes it out alive.
    49. Re:claims by jim_v2000 · · Score: 1

      "I get a dialog pop up asking me to enter my password to authenticate as administrator in order to perform this action."

      AH HAH! That's the whole point! This doesn't ask for your password. It asks for an administrator's password. Not every account on a computer has elevation rights.

      --
      Don't take life so seriously. No one makes it out alive.
    50. Re:claims by jim_v2000 · · Score: 1

      But the catch here is that you, as the user, have to have permission to elevate your account's rights. The system in this article allows you to user a different user's account, which is automatically displayed to you.

      --
      Don't take life so seriously. No one makes it out alive.
    51. Re:claims by Anonymous Coward · · Score: 0

      How right you are! A patent shouldn't have been granted for the electrical engine starter since it's just doing the same thing a user could have done with a hand crank. How foolish of everyone.

    52. Re:claims by Dachannien · · Score: 2, Informative

      If it comes down to the degree of "exactly," please provide some examples from patent case law that show that the degree of difference here is sufficient for the two programs not to be close enough to the same that sudo, had it been invented after this patent, wouldn't violate said patent.

      That's not the way it works. The examiner has to make a prima facie case of unpatentability in order to reject a claim. If the examiner can't substantiate such a case, the application gets allowed, and the applicant gets a patent.

      Only when the examiner makes a prima facie case does the burden shift to the applicant to either successfully traverse the rejection (e.g., by properly indicating a flaw in the rejection, by citing case law applicable to the rejection, by providing evidence of unexpected results/commercial success/various other secondary considerations in the case of an obviousness rejection, etc.) or amend the claims.

    53. Re:claims by mea37 · · Score: 1

      I'm afraid you have the question backwards.

      The correct question is: where in the claims does it say that it does cover a system in which an application, having received an "authorization denied" exception, and knowing that the invention is present, then requests that the invention do X, Y, and Z? The answer is, the claims don't say that - therefore such a system isn't covered.

      See, the claims don't enumerate the thigns that aren't the invention, so asking me to point out where it says that such-and-such isn't the invention is a bit absurd.

      The claim language is perfectly clear on this: the exception itself is the trigger for the invention to act. The app doesn't have to do anything, or even know that anything can be done.

    54. Re:claims by ben0207 · · Score: 1

      That's precisely what OS X does. If a limited user tries to do an admin-level task, it asks for an admin account name and admin password.

      If an admin account tries the same thing, the username box is already filled, it just needs a password.

      --
      cmd-q.co.uk - some sort of stupid fucking internet bullshit
    55. Re:claims by KarmaMB84 · · Score: 1

      The information on Groklaw has been prepared as a service to the FOSS community in particular and the general public. It is not intended to constitute legal advice. PJ is a paralegal, not a lawyer. Even when lawyers write or contribute to articles, it is still not legal advice.

    56. Re:claims by jim_v2000 · · Score: 1

      Does sudo suggest an account that you can use if your account isn't in the sudoers list? No. And that's the entire point of this patent.

      --
      Don't take life so seriously. No one makes it out alive.
    57. Re:claims by jim_v2000 · · Score: 1

      I understand, but this doesn't ask for the administrator's name, it shows you who the administrator is and you only have to know the password.

      --
      Don't take life so seriously. No one makes it out alive.
    58. Re:claims by ben0207 · · Score: 1

      Ah. In that case, MS might be onto something.

      Though on a technical level I'd like to know how it prioritises which account to list when there's more than one.

      --
      cmd-q.co.uk - some sort of stupid fucking internet bullshit
    59. Re:claims by Adrian+Lopez · · Score: 1

      I fail to see how I have it backwards. I'm saying is there's nothing in the text of the claim that requires the authentication request to be handled by the operating system. I'm saying the claim is ambiguous enough that the patent might cover the invocation of gksudo by an application that requires greater privileges just as it would cover an invocation by the operating system. I've asked you to resolve this ambiguity by pointing to the proper section of the patent claim, but all you do in response is dance around the issue and provide nothing of substance. I shall take your reply as a "no, I can't point to the relevant section in the patent claims because it doesn't exist".

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    60. Re:claims by EvanED · · Score: 1

      Can you please explain why this is different than the patent?

      To the end user, it will appear (nearly) the same.

      However, the architecture is rather different, at least compared the sudo case. In the sudo case, if a program runs with insufficient rights, it will simply fail. Because of this, a program that wants a dialog to pop up if the user does something (e.g. click "install") must take proactive actions to achieve this: it must explicitly call sudo.

      By contrast, what UAC does (and that's what this patent is talking about) is watches requests from a program; if it requests something it doesn't have rights to, then the OS will display the elevation prompt.

      To witness the effects of this, try installing software on Vista or Win 7. Some installers ask for elevations up front, but not all; others will let you go through the initial steps (e.g. choosing which parts to install, setting a target directory) without elevation, and then present the UAC prompt when it starts to install.

      In other words, by my understanding:
        - sudo cannot elevate an existing process
        - UAC does elevate existing processes

      I strongly suspect the same thing is true of OS X, though I can't speak with complete confidence in that matter.

      I don't want to argue that the patent is valid or anything like that, but there is a pretty big difference.

    61. Re:claims by larry+bagina · · Score: 1

      There are fundamental differences between sudo (with or without a gui), the os x permission prompt, and what this patent is describing.

      sudo: user specifies command which needs to be run with elevated security.
      os x (authorization services) : program requests authorization for specific operations, releases it when done
      ms (I only read enough to see it isn't sudo): if a system call is made with insufficient privileges, the os pops up a window asking for an admin password. Similar to os x authorization services, but the programmer/program doesn't ask for the authorization beforehand.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    62. Re:claims by Derek+Pomery · · Score: 1

      Just a slightly different way of looking at it.
      $ gksudo ls
      (prompts)
      $ gksudo ls
      (if you have sudo set to a timer, no prompt)

      So gksudo does come up in response to a failed attempt to escalate privileges. Otherwise it doesn't.
      It is the wrapper that permits this.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    63. Re:claims by EvanED · · Score: 1

      I meant to say one more thing. Ever been at the command prompt, issued a command as a normal user that needs root, gotten a failure, and gone "doh, forgot to run it as root", hit the up arrow, and put a sudo before it?

      With sudo-style elevation, you need to do that. This is what Gnome or whatever is doing behind the scenes when you open a configuration dialog that needs root (except that it never forgets!).

      The UAC, this-patent-way of doing it would be for your initial attempt to cause Linux to say "this program is trying to do something that needs root, is that what you wanted?" and give you a password prompt then.

    64. Re:claims by Anonymous Coward · · Score: 0

      They do NOT all have to apply. Each claim is a property right, similar to the boundaries detailed in a land deed. If you meet the limitations of a claim, for example claim 1, you infringe, regardless of whether you meet the limitations of the other claims.

    65. Re:claims by unix1 · · Score: 1

      Sorry, but the patent does not describe or cover the access control system for users. It merely references the user account permissions as a base/reason for escalation.

      The patent is about the interface used to escalate privileges in order to perform a task. The method of how it was determined that the user did not have access to the said task is irrelevant and is not covered by the patent.

      In fact, the patent describes what kdesu and similar tools (using sudo) already do - i.e. something (some underlying system, script, program, etc. - it doesn't matter what/how) determines there is a need for privilege escalation for a specific task, and presents the user interface in order to do so. This patent covers that use interface.

    66. Re:claims by Stuntmonkey · · Score: 1

      In both OS X and Linux if you attempt to do something that requries elevated permissions you will be prompted with a GUI thing. Can you please explain why this is different than the patent?

      You weren't asking me, but I'll take a stab at this. Patent claim #1:

      1. One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to present a user interface in response to a task being prohibited based on a user's current account not having a right to permit the task, the user interface comprising: information indicating the task and an entity that attempted the task; a selectable help graphic wherein responsive to receiving selection of the selectable help graphic, the computer-readable instructions further cause the computing device to present the information; identifiers, each of the identifiers identifying other accounts having a right to permit the task, wherein the identifiers presented are based on criteria comprising: frequency of use; association with the user; and indication of sufficient but not unlimited rights; one of the identifiers identifies a higher-rights account having a right to permit the task, wherein the one of the identifiers comprises: a graphic identifying the higher-rights accounts associated with the user; and a name of the higher-rights account; an authenticator region capable of receiving, from the user, an authenticator usable to authenticate the higher-rights account having the right to permit the task, wherein: the authenticator comprises a password, and the authenticator region comprises a data-entry field configured to receive the password.

      I've marked in bold the components that are not present in the OS X functionality at least (I'm not as familiar with Linux behavior). Under OS X there is no "selectable help graphic", nor is there a listing of accounts that may be "of sufficient but not unlimited rights" (on the contrary, OS X only allows you to authenticate as an administrator).

      This is obviously a highly-specific patent in its claims. As such it isn't very useful in practice -- it would be pretty easy to avoid infringing by building similar functionality that leaves out one small part of the above claim. This patent most certainly does not cover sudo or its variants. I'm surprised the commentator on Groklaw got confused by this, the patent is quite easy to read.

      Sudo etc. do not constitute prior art that would invalidate the claim above, since the claim contains elements not possessed by these earlier inventions. That alone however does not justify a patent. One must also argue that the invention is sufficiently novel -- in other words, that it is "unobvious" to a practitioner in the art, and that the additional elements over prior art add real value. Novelty is frankly where a lot of software patents get shaky since it's a judgment call (is Amazon 1-click "obvious to a practitioner of the art"?). I never thought of this exact kind of functionality before (in particular, showing a list of user accounts, rather than just an administrator account). But then I'm not an experienced practitioner in computer security.

      Overall this reads to me as not too bad of a patent, although not a very valuable one since it would be so easy to design around. Maybe they hand out bonuses at Microsoft for each patent you successfully file.

    67. Re:claims by Anonymous Coward · · Score: 0

      No, but there were mainframe systems that did trap on insufficent permissions, providing an opportunity to switch to an account that does. It would not be too darn difficult to make a program for Linux that acted almost identical, using GKSudo as the backend.

      The only orginal parts of this are identifying the users with the needed permissions, preferring those with less permissions to those with more, and tracking how often the user switched to each of those higher level accounts, and ordering them based in part on that. (The result would be that if user had a second account with more privileges, the system would gradually determine this, and after a few times, list that account first.

      This is despite the fact that it has been shown, time and time again, that move parts of the UI based on how frequently they are used is a bad idea. Remember how rarely used programs in the start menu would be hidden by default? How about rarely used icons in the notification area. (Bugs in this system have resulted in an absolute guarantee that whatever icon I want will not be present even in the full list of icons.) Please don't get me started on the hiding infrequently used menu components in Microsoft Office.

    68. Re:claims by Tacvek · · Score: 1

      PPJ is a paralegal not a lawyer. (Unless I missed the notification that she took and passed the Bar exam.) (I did not see any indication that this was written by somebody other than PJ, but If you know something I don't about this article, please enlighten me.)

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    69. Re:claims by Anonymous Coward · · Score: 0

      You mean that this is a patent for "clippysudo", where it stands in the background, saying "it looks like you do not have the right do do this, etc." ?

      Well, that's innovative !!

    70. Re:claims by fermion · · Score: 1
      As has been mentioned, it is not so much that MS patented sudo, but the GUI implementation of sudo.

      My reading is the patent covers effectively what has been the Mac OS X standard security interface. if the user does not have the sufficient privilege, the OS prompts for credentials. This is a GUI implementation. I don't know if the Mac implementation provide prior art, but maybe it was implemented on the NeXT. I don't remember having to type any additional credentials after login on my cube.

      I know that MS Windows XP has a primitive version of such authentication. I can log into certain resources from less privileged accounts, but I don't think I can, for instance, install or delete files from a less privileged account. I have not had to any real work in MS Vista, so maybe it is more fully implemented there.

      In any case, there is likely prior art, as is the case with most software patents. It is not an obvious patent, but it is patenting a common work method, which is the problem with software patents. If I build a machine that automatically makes cookies, that should absolutely be patented. But I should not be able to patent the common process of making cookies.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    71. Re:claims by Xiaran · · Score: 1

      Excellent. Your post and the ones below this clear up my problems and I agree with you. From my knowledge I am unaware of unix like operating systems to do this tho I can think of ways to do it if required. I agree this is not the same as sudo but does not really deserve a patent... its really not all that novel :)

    72. Re:claims by supernova_hq · · Score: 1

      ...displays an account with the proper rights automatically.

      Last I checked, 99.99% of the time, root is an account with the proper rights.

    73. Re:claims by Zordak · · Score: 1

      The person analyzing this for groklaw is a lawyer well seasoned in tech and IP litigation, and disagrees with you.

      Who? PJ? She's a paralegal. She lost credibility when she complained about the following paragraph:

      Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.

      Guess what. That's boiler plate. Every patent application has it. It's just says, "Hey, you folks on the jury! The claims aren't limited to the embodiments in the specification." Which is just plain, vanilla patent law. It's just saying what the judge should tell them anyway. Every single patent I write has a similar paragraph, and any competent patent attorney wouldn't blink an eye at it.

      This may not be the most earth-shattering patent in the world, but unless your program has every single feature of the claims, you don't infringe. And unless the prior art has every single feature of the claims, it doesn't anticipate. Sudo doesn't.

      --

      Today's Sesame Street was brought to you by the number e.
    74. Re:claims by supernova_hq · · Score: 1

      Does it need to list all of them, or just one? Because I can guarantee you that if ANY user can do something, root (the default for sudo/gksu/etc) can!

    75. Re:claims by sabt-pestnu · · Score: 1

      > Adding a GUI is no more "creative" and "non-obvious" than adding "on the Internet".

      More to the point, adding a GUI to sudo has already been done. The groklaw article even points this out. Any invention must come from other factors than "we added a GUI".

      And any claims to the extent of "we added a GUI with these features" has to withstand prior art claims per feature patented.

    76. Re:claims by Anonymous Coward · · Score: 0

      PolicyKit does

    77. Re:claims by jim_v2000 · · Score: 1

      Do you understand how sudo knows who can use sudo?

      --
      Don't take life so seriously. No one makes it out alive.
    78. Re:claims by PhilHibbs · · Score: 3, Informative

      If you try to do something that you aren't allowed to, does sudo automatically pop up and ask you if you want to authenticate to an account that does have the privilidges that you need? That's what this patent is about.

    79. Re:claims by PhilHibbs · · Score: 1

      The patent mentions sudo many times.

    80. Re:claims by iammani · · Score: 1

      Gnome + gksudo does that!

    81. Re:claims by Anonymous Coward · · Score: 0

      This patent applies to the UAC system Microsoft first released in Windows Vista, which predates the first version of PolicyKit (and the general policy architecture in Windows goes back to Windows NT in the mid-1990s).

      If PolicyKit is as similar to the Windows UAC and policy architectures as you claim, it's probably copied from Vista, and may in fact violate this patent.

    82. Re:claims by Anonymous Coward · · Score: 0

      Quoting Kosh: "You do not understand". While the method of implementation may be the preferred one, it's the claims that rule. I've filed patents (not pure software ones so don't give me grief about that) and I've been told in no uncertain terms by the lawyers that you have to get the claims right. The abstract, background and other stuff in the patent is only to help people understand the claims.

      That "this is only the preferred embodiment" is standard language for patents so that it can't be argued in court that the claims are limited by the background. Claims also have to be specific or they won't hold up in court.

      And, in your example, if there's a claim that states the angle is 90 degrees and no claims for other angles, then you can go and invent your 80 degree shovel immediately.

    83. Re:claims by Anonymous Coward · · Score: 0

      It really does help to read the patent before commenting. One of the essential parts of the 'invention' is that it minimises privilege elevation by defaulting to the *least-privileged* user allowed to carry out the operation. The least-privileged user would never be root unless no other user can do it. Windows doesn't even have a 'root' account anyway, and 'Administrators' don't have unrestricted privileges like 'root'.

    84. Re:claims by Anonymous Coward · · Score: 0

      Adding a GUI is not even enough, I should think ..

      Remember, a command-line is a type of user interface. Not a great one for many people, but it still qualifies.

    85. Re:claims by gzipped_tar · · Score: 1

      So it's like consolehelper all over again? No name asked (it's just "root", duh), and you only have to know the root password.

      --
      Colorless green Cthulhu waits dreaming furiously.
    86. Re:claims by Anonymous Coward · · Score: 0

      exception handling? Oh no, I have a security exception, let's try again with sudo.

    87. Re:claims by apoc.famine · · Score: 2, Informative

      Pretty much. I try to update my system, I get a box saying, "Please type your password here to sudo so I can complete this". Ubuntu has been doing that for years now.

      --
      Velociraptor = Distiraptor / Timeraptor
    88. Re:claims by Interoperable · · Score: 1

      Yeah, but is that really a sufficient leap away from sudo to justify a patent? Most mainstream Linux distros already provide a graphical dialog box for sudo privileges, Windows already provides administrator authentication pop-ups; surely the idea of displaying different possible user accounts isn't worth a patent.

      --
      So if this is the future...where's my jet pack?
    89. Re:claims by Anonymous Coward · · Score: 0

      If you're putting language like that in your claims, it won't hold up in court. Claims have to be specific
      You're right that it's boilerplate but only in the background section so as to not limit your claims with a particular embodiment described in the background.
      This has been made very clear to us by the lawyers at a company that *knows* about patents.

    90. Re:claims by Anonymous Coward · · Score: 0

      "If you try to do something that you aren't allowed to, does sudo automatically pop up and ask you if you want to authenticate to an account that does have the privilidges that you need? That's what this patent is about."

      WTF is parent +4? Are the morons that submitted this patent moderators today?

      You mean that if I realize I am going to need additional privileges for the task and ask for them before attempting to perform the task that is not covered by this patent, but if I don't realize that and it prompts me then it is covered? Why is that patentable?

    91. Re:claims by gzipped_tar · · Score: 1

      This is usually done via the "usermode" (https://fedorahosted.org/usermode/wiki) feature. The programs that requires priv. to use are symlinks to /usr/bin/consolehelper. When the user invokes such an application by name, consolehelper reads its argv[] and determines which program the user intended to run. Using this piece of information, it then runs /usr/sbin/userhelper with the right arguments. Unlike consolehelper, userhelper is capable of switching to *another* account by interfacing PAM. It checks whether this program (the one that does the actual job, usually not in $PATH. IIRC the jargon term is "PAM service") is present, and lets the PAM configuration determine what kind of authentication is required (i.e. which user's account to use, whether permission is required or optional, etc). If all is well, the service is run as the other user. Because this "other" user account is determined by the service's configuration, the user don't have to type the username, just the password, if required.

      --
      Colorless green Cthulhu waits dreaming furiously.
    92. Re:claims by Anonymous Coward · · Score: 0

      The above patent claim also does not come up "in response to a failed security authentication" in exactly the same way that sudo doesn't.

    93. Re:claims by Anonymous Coward · · Score: 0

      dude. i have never understood all these years - but gravity *is* about things falling down! thanks dude.

    94. Re:claims by jim_v2000 · · Score: 1

      I just read the man page for consolehelper...it sounds similar, but not really the same function or mechanism.

      --
      Don't take life so seriously. No one makes it out alive.
    95. Re:claims by Anonymous Coward · · Score: 0

      Define automatically. If you are using KDE, say, then most KDE software will automatically popup a gui for sudo (kdesu) if it needs additional privillages.

      Perhaps even closer is policykit though.

    96. Re:claims by gparent · · Score: 2, Insightful

      But that's not sudo doing that. Whatever pops up that box ends up using sudo to up your privileges, though.

    97. Re:claims by Macgrrl · · Score: 1

      If I want to install an application on my Mac, it pops up a window asking for an adminstrator password before it will permit the install. Isn't that essentially the same thing?

      --
      Sara
      Designer, Gamer, Macgrrl in an XP World
    98. Re:claims by Anonymous Coward · · Score: 1, Interesting

      The patent was filed four and a half years ago. I suspect that Microsoft has prior art of their own that predates ubuntu's first release as well. "Years" isn't enough. First is.

    99. Re:claims by Meski · · Score: 1

      Give me a patent!
      No
      sudo give me a patent!
      Ok

      (sorry http://xkcd.com/149/)

    100. Re:claims by falconwolf · · Score: 1

      in response to a task being prohibited based on a user's current account not having a right to permit the task,

      When I try something on my Mac that needs an admin to do but a regular user is logged in a window pops up asking for an admin's password that has the rights. If a password isn't typed in it won't do it. However the MS patent application says it presents "an account having a right to permit". My Mac doesn't do that though, so maybe it's novel enough.

      Falcon

    101. Re:claims by falconwolf · · Score: 1

      This patent covers material which has been present in linux and macos X and is part of the evolving function of sudo. Fini.

      It may be where sudo is evolving to but does sudo list the accounts that have the needed permission?

      Falcon

    102. Re:claims by Joe+Decker · · Score: 1

      Remember that they all have to apply.

      No, they don't. Only one independent claim (i.e., 1, 2 or 9) has to apply (at least it's like that in Europe)

      Same in the US. To violate the patent you only need to violate one claim.

    103. Re:claims by falconwolf · · Score: 1

      AH HAH! That's the whole point! This doesn't ask for your password. It asks for an administrator's password. Not every account on a computer has elevation rights.

      My Mac does ask for an admin's password. However it doesn't list the users accounts that have the required permissions whereas MS does list them. So in that MS has added something.

      I don't know if that rises to a novelty though, which is a requirement for patents.

      Falcon

    104. Re:claims by falconwolf · · Score: 1

      It seems to me the patent would cover gksudo when invoked by an application that knows it doesn't have the necessary rights to perform an operation, but perhaps there's something I've missed?

      "these systems and/or methods present a user interface identifying an account having a right to permit a task". Does gksudo list accounts that have the rights?

      Falcon

    105. Re:claims by Anonymous Coward · · Score: 0

      plus with prior art of Sudo in Linux, they have no chance to go against Linux for this

    106. Re:claims by the_womble · · Score: 3, Informative

      kdesu and gksu do most of it, and, as someone pointed out above, Policykit does all of it.

    107. Re:claims by mpe · · Score: 1

      Yeah, but is that really a sufficient leap away from sudo to justify a patent? Most mainstream Linux distros already provide a graphical dialog box for sudo privileges, Windows already provides administrator authentication pop-ups; surely the idea of displaying different possible user accounts isn't worth a patent.

      Especially since there are situations where such a list would not make much sense. e.g. where the number of possible accounts is large. Since such a system would allow an unprivileged user to find out about the privileges of other uses it may also be considered a security problem too.

    108. Re:claims by phooka.de · · Score: 1

      I've read numbers 1 through 8. It's the Mac OS X dialog you see when you need sudo-rights plus a graphical icon for Admin-acounts.

      I'm absolutely stunned how novel and non-obvious this slight modification to Apple's OS is, how innovative and worthy of a 20 year monopoly on implementation of such an astounding improvemant over what Apple ships for years.

    109. Re:claims by PhilHibbs · · Score: 1

      If that's a specific function of the application installer, then no. If it does the same thing for file deletion, user creation, changing system settings, and everything else that is controlled by user policies, then it may be the same thing.

    110. Re:claims by MrMr · · Score: 1

      They exactly cover sudo and its graphical wrappers. Read the claims instead of just copying and pasting them.

    111. Re:claims by MrMr · · Score: 1

      O really?
      Like A disk with a program that checks if you have permission to do a task and presents a prompt to escalate the permissions if required?
      You haven't got a clue. Fini indeed.

    112. Re:claims by Rockoon · · Score: 1

      The predominant difference is that the Mac does not run that installer in userland and then escalate the privileges while its already running.

      The Microsoft patent covers a situation where an already running application triggers an access violation, and instead of outright denying the access like Linux or OSX would, it prompts the user for increased privileges first.

      This isnt a sudo patent. Its a UAC patent.

      I am simply amazed that slashdot is arguing against Microsft keeping UAC to themselves.

      --
      "His name was James Damore."
    113. Re:claims by Anonymous Coward · · Score: 0

      Policykit does all of it.

      So, in case of patent trolling, could they claim prior art?

    114. Re:claims by Anonymous Coward · · Score: 0

      Actually, I think that Policykit is missing the "help" icon. But that's about all.

      Don't worry, that's probably enough. I mean, they found some other piece of crap to be novel *only* because it used four knowledge bases. Never mind the fact that you could split or combine those, or that EVERY other part of the "invention" was disclosed in prior art.

      Yes, I think the patent system is completely out to lunch here. Nobody comes out ahead except the lawyers.

    115. Re:claims by Adrian+Lopez · · Score: 1

      In Ubuntu, whenever I try to mount a drive but don't have the necessary privilege, I am presented with a list of users who do have such privilege and I am prompted pick a particular user and to provide that user's password. Even if no such list were presented to the user, however, a system like gksudo still has to identify an account -- say, root -- that does have the right to perform the privileged operation.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    116. Re:claims by mvdwege · · Score: 1

      Ahum.

      rootpw: If set, sudo will prompt for the root password instead of the password of the invoking user. This flag is off by default.

      Now why don't take your corporate shilling ass out of here?

      Mart

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    117. Re:claims by MightyMartian · · Score: 1

      That's kind of bizarre even in and of itself. Querying the user database and showing the results in a GUI window doesn't seem terribly innovative. I mean, what's next, patent a GUI-based query of all users whose first name begins with "R"? How about LDAP queries of everyone who is a member of a given group?

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    118. Re:claims by Victor_0x53h · · Score: 1

      Holy mackerel, you're right. Kudos!

    119. Re:claims by Anonymous Coward · · Score: 0

      Yes actually. The last 2 version of Ubuntu have had this feature.

    120. Re:claims by jgostling · · Score: 1

      Agreed. This patent is not about sudo. It's about setuid.

      Cheers!

    121. Re:claims by mea37 · · Score: 1

      "I'm saying is there's nothing in the text of the claim that requires the authentication request to be handled by the operating system."

      If the OS (or to be more precise, since the invention may be deployed as part of the OS, any component of the OS outside of the invention) has to intervene, that also is not the invention. The invention itself has to respond to the authorization failure. Not the application that tried to do something it wasn't allowed to do. Not the OS. The invention.

      "I'm saying the claim is ambiguous enough that the patent might cover the invocation of gksudo by an application"

      I understand what you are saying. You are incorrect.

      If I patent an invention where pulling into a driveway causes the garage door to open, I cannot then claim you're infringing if you're paying a guy to sit next to your garage door and open it when you pull into the driveway. The patent spells out what the invention does - not what happens in proximity to the invention - and it says quite clearly that the invention responds to an authorization failure. A device that relies on something outside of itself to do something spelled out in the patent claims, isn't the covered invention.

      "just as it would cover an invocation by the operating system"

      What you're not getting is, it wouldn't cover an "invocation" by the operating system. If the code has to be invoked by any outside component responding to the authorization failure - then the code itself is not responding to the authorization failure and is not the invention.

      "I shall take your reply as "

      If you want to interpret your failure to understand patent language as me being evasive, so be it. Try your argument in court, and you'll find out the hard way that I'm right.

    122. Re:claims by Bovarchist · · Score: 1

      I agree that it is a bad patent just because it is an obvious thing to do. However, I think comparing it to sudo is a bit of a stretch. Maybe I'm running the wrong version of Linux, but I've never had sudo pop up and tell me that I don't have permission to do something and would I please provide the password to an account that does have said permission. Is "Permission denied" a sudo prompt that I have been hitherto unaware?

      --
      Hell is other people's code.
    123. Re:claims by mcgrew · · Score: 1

      I'm not a patent lawyer either, but my former brother in law has a little insight into the matter. He worked in a factory, and the PHB would bring him a widget from a competetitor and say "can you make one of these with what we have on hand?" He didn't worry about any patents at all; that was what the legal department was for.

      The legal department would study the widget and any patents, and often you could get around the patent by using (for instance) brass instead of copper.

    124. Re:claims by Anonymous Coward · · Score: 0

      No, but there may be other prior art. Someone pointed PolicyKit, but Apple had something similar years before. Also, back in 2002 systrace could filter syscalls, halting any processes and asking the user to allow/deny the operation or kill the process that did a syscall matching the filter.

    125. Re:claims by True+Grit · · Score: 1

      The examiner has to make a prima facie case of unpatentability in order to reject a claim.

      So the burden of proof on the overworked, underpaid (and possibly incompetent) examiner is thus set very high, possibly too high.

      If the examiner can't substantiate such a case, the application gets allowed, and the applicant gets a patent.

      Who is now free to use that patent against others like a bludgeon, and the burden of proof for the *defendant* ends up high as well, and even when they can do what the examiner could not (find prior art), they've already *lost* anyway, at least from a business's bottom-line-oriented (expense) point-of-view.

      Only when the examiner makes a prima facie case does the burden shift to the applicant to either ...

      What burden? They just keep rewording and resubmitting it until they simply wear down the examiner...

      Are (most) patent attorneys paid per application *attempted*, or per application *approved*, or strictly per hour?

      What about companies with in-house staff? They've got nothing better to do than to keep chipping away at the USPTO, since every patent in their arsenal becomes worth the trouble in the case of a nuclear patent showdown with a rival...

    126. Re:claims by supernova_hq · · Score: 1

      Then jim_v2000 also skipped over that part, because his comment about that section completely excluded that little detail.

      Oh, and sorry for not wasting my team reading 10 PAGES of leaglise written by lawyers who haven't written a line of computer code in their lives.

  3. Much more specific than the summary suggests by Sockatume · · Score: 5, Informative

    If I'm reading the patent right, they've actually applied for protection of the UAC popup system that appears in Vista and Win7. There's no unqualified patent on user account privilege escalation. Indeed, "su" would be explicitly outwith this patent's claims, as it's specifically about bringing up an interface to escalate when the system determines that escalation will be required, not about escalating manually before the task is attempted.

    Top marks to the Groklaw article for providing a thorough explanation for how they can't get a patent on something they're not trying to get a patent for.

    --
    No kidding!!! What do you say at this point?
    1. Re:Much more specific than the summary suggests by MBCook · · Score: 2, Informative

      So, like what OS X had a year or two before Vista?

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    2. Re:Much more specific than the summary suggests by plasmacutter · · Score: 4, Informative

      If I'm reading the patent right, they've actually applied for protection of the UAC popup system that appears in Vista and Win7. There's no unqualified patent on user account privilege escalation. Indeed, "su" would be explicitly outwith this patent's claims, as it's specifically about bringing up an interface to escalate when the system determines that escalation will be required, not about escalating manually before the task is attempted.

      Top marks to the Groklaw article for providing a thorough explanation for how they can't get a patent on something they're not trying to get a patent for.

      macos x has been doing this since its inception.

      gksudo has been around for a long time as well.

      this is NOT new.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    3. Re:Much more specific than the summary suggests by Sockatume · · Score: 3, Insightful

      Perfectly good examples of prior art that the author of that article skipped in favour of a content-less rant.

      --
      No kidding!!! What do you say at this point?
    4. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 1, Informative

      No. OS X doesn't present a list of accounts which you can use to get privilege with, for one thing.

    5. Re:Much more specific than the summary suggests by CannonballHead · · Score: 0, Redundant

      gksudo escalates as required/when the system determines it is required?

      In all my usage of *IX systems, I've always had to either use sudo before I ran something, whether that's in a script or a program calling it and waiting for the user, etc.

      That's different from UAC. Which is why the OP said

      escalate when the system determines that escalation will be required, not about escalating manually before the task is attempted.

    6. Re:Much more specific than the summary suggests by plasmacutter · · Score: 1, Redundant

      and I'm telling you macos x does that already.

      continually telling me the same thing over and over does not make it different.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    7. Re:Much more specific than the summary suggests by sopssa · · Score: 1

      You're forgetting the other claims in the patent. Yeah it's easy to read the summary/abstract of patent and come up with "lol this have been done for so long!" while ignoring what the patent is actually completely claiming. Neither Mac OSX or sudo or gksudo cover what this patent is claiming.

    8. Re:Much more specific than the summary suggests by CannonballHead · · Score: 1

      gksudo has been around for a long time as well.

      I was responding to that.

      I have barely used mac os's so I don't want to comment on those, I'll let people that have used it comment.

      Incidentally, Apple is no stranger to patents and lawsuits, so if this Apple has prior art, I'm sure they'll let us know...

    9. Re:Much more specific than the summary suggests by MobyDisk · · Score: 1

      In all my usage of *IX systems, I've never had to do an sudo before I ran something. When I run the app downloading tool thingy, or changed something in the control panel, it just prompts me for a root password. Pardon me for being a Linux neophyte, but I just thought that the UAC prompt was Microsoft's version of the same thing (except that it pops-up at stupid times and asks you the same thing 3 times over).

      My knowledge is dated - I think it was Mandrake Linux that did that. Although more recently I saw Ubuntu do it too.

    10. Re:Much more specific than the summary suggests by CannonballHead · · Score: 1

      On an unrelated note, I didn't realize I responded to you in a different comment. Not trying to troll your comments or something. (just in case the thought arose)

    11. Re:Much more specific than the summary suggests by CannonballHead · · Score: 1

      But it's how that "tool thingy" implemented it that is the question. Using apt requires sudo. If the downloading tool thingy is simply a wrapper for apt (in this example), then it could very likely be calling sudo (or a GUI sudo)... but it's the application that is specifying the need to run sudo. It's not the OS determining "Hey, you can't do that! Do you want to sudo?" At least in my experience, when you try to do something you're not allowed to do in Linux, you get a Permission Denied type response. At lower levels, at any rate; wrappers to these responses may retry with sudo or su or whatever.

      It looks like the patent is specifically referring to intercepting things you're not allowed to do and instead of just failing, asking you to authenticate (/telling you that an application is trying to do that, do you want to let it?).

    12. Re:Much more specific than the summary suggests by Qzukk · · Score: 4, Informative

      Yeah, going to have to agree here. Not only is it specifically an interface brought up after you've tried to do something you're not allowed to (which is what makes it "not sudo"), this interface will give you a list of users who ARE allowed to do it (rather than just the admin account), which is what separates it from all the other implementations of this kind of security that I know of (eg cash registers that stop and require manager intervention or Windows's earlier "You look like you're trying to install a program, would you like to be administrator?" popup).

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    13. Re:Much more specific than the summary suggests by paxswill · · Score: 1

      IIRC, that's not quite correct. I haven't done any Cocoa recently that required root privileges, but most of the time you mark a task as requiring admin access, and the use is then prompted for a password (normally. If the current logged in user is an admin, and has no password, it will pass through I think). It asks for any user, but just fills in the user name for the currently logged in user if it's an admin. Basically, it will ask for a PW any time it needs sudo, no matter the user (unless the user is root).

    14. Re:Much more specific than the summary suggests by Theaetetus · · Score: 5, Insightful

      macos x has been doing this since its inception.

      gksudo has been around for a long time as well.

      this is NOT new.

      You've said this in at least two different posts, yet failed to indicate what those do that this patent covers. For example, OSX doesn't present an interface with a "selectable help graphic", the selection of which causes display of other accounts that have a right to permit the task, based on frequency of use, association with the user, and an identified higher-rights account that can permit the task. And that's just three of the limitations of claim 1. I doubt gksudo does them either.

    15. Re:Much more specific than the summary suggests by spitzak · · Score: 1

      At least in my experience, when you try to do something you're not allowed to do in Linux, you get a Permission Denied type response

      Which a calling program can catch and therefore decide to pop up this sudo dialog box. Catching the error from exec() is exactly the right way to do this. I think you are imagining that "detection" is somehow run in the target programs space or something, but "detection" can be done by the CALLING program. This is the same thing.

    16. Re:Much more specific than the summary suggests by markdavis · · Score: 1

      > it's specifically about bringing up an interface to escalate when the system determines that
      > escalation will be required, not about escalating manually before the task is attempted.

      Funny, but that is exactly what my Mandriva Linux system does when I try to install updates, launch the system configurator, change a network setting (instead of just selecting a network) etc. It pops up a GUI asking for the root password if I am not already allowed. And it has done this for years.

    17. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      I've had shell scripts that have done that for over a decade...

      I've developed a table of which commands on which systems need to be run as root, oracle, informix, db2instxyz, etc...

      Then when a user tries to execute one of them, it checks the table, validates if a) the command requires escalation, and b) if the user is allowed to escalate the command - if both pass, it utilizes sudo to switch to the appropriate user, and run the command with whichever safe parms were passed...

    18. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      Bully for you. What do you want, a fucking medal?

    19. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      that's PJ for you.

    20. Re:Much more specific than the summary suggests by BlueBoxSW.com · · Score: 1

      I read it the same way you do. They're looking to patent a more useful GUI version of SUDO, not that functionality itself.

      One in which the system figures out who can run the task, and presents the option to login as them.

      I get annoyed as much as the next guy as MS, but this article is misleading.

    21. Re:Much more specific than the summary suggests by Flwyd · · Score: 1

      Does the patent also cover being ridiculously annoying and not actually secure since it doesn't prompt for a password? If so, I say we grant it to Microsoft so nobody copies that design.

      It would be great if they added sudo.exe so you didn't have to run the whole command shell as an administrator.

      (I'm basing this on my experience with Vista; things may have gotten markedly better in Win7.)

      --
      Ceci n'est pas une signature.
    22. Re:Much more specific than the summary suggests by PitaBred · · Score: 2, Insightful

      Whoop-de-fuck. How exactly is that novel or non-obvious?

    23. Re:Much more specific than the summary suggests by CannonballHead · · Score: 1

      Yes, a program can implement a UAC-ish thing or even call gksudo or whatever as necessary. But UAC is not embedded within each application and Microsoft is not patenting a try-catch statement. It sounds like Microsoft is patenting a way to catch the failed authentication before it fails ... heh ... and prompt the user. The application does not need to know about this - and doesn't, which is obvious from many older programs (pre-Vista) that end up making UAC prompt when they try to do something that Vista/7 now require elevated privileges to do.

      And either way, gksudo does not do this, as many are claiming :)

    24. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      If I'm reading the patent right, they've actually applied for protection of the UAC popup system that appears in Vista and Win7. There's no unqualified patent on user account privilege escalation. Indeed, "su" would be explicitly outwith this patent's claims, as it's specifically about bringing up an interface to escalate when the system determines that escalation will be required, not about escalating manually before the task is attempted.

      exactly. sudo IMO is not prior art here. the FreeBSD ports(7) system is closer: you can run most of the process of downloading, extracting, patching and building of a port as a plain user; the ports system identifies tasks which require elevated privileges, and performs the task under su. that's more in line with the first claim quoted in the groklaw article than sudo, modulo the graphical interface and the minor security weakness of divulging privilege levels of unrelated accounts.

    25. Re:Much more specific than the summary suggests by Zephiris · · Score: 1

      At the worst, Microsoft appears to be patenting some 'enhanced' variation of UAC (which doesn't ask for or present any of the things covered in the patent either, apparently).
      This particular patent doesn't, as the parent points out, directly try to cover sudo, or Microsoft's own runas command, which -is- a direct ripoff of sudo.

      As is apparently common in patents, Microsoft realized they wouldn't be granted protection (or likely even a review) anytime near when UAC originally came out, so they patented a leapfrog idea that they could possibly use years later, and wouldn't already be common public knowledge. The rules get murky at times, but even several Slashdot articles have covered this in the last year or two: you can't patent something that already exists, but you also can't patent something that you've already refused or delayed in patenting.

      If Microsoft introduced UAC in Vista, but waited until after Windows 7, a second major product to use it or change it, to patent it, it'd dillute it enough (and WIndows 7's variation being minor) to be unpatentable by them or anyone else. MS leapfrogged the issue by having Vista UAC, and Windows 7, but neither did any of the major claims in the patent, which leaves them completely free to implement this in Windows 7.1 or 8.0, or whatever they decide to name the next version.

      --

      "A Goddess rarely smiles for she is forced by others to be an island unto herself." - Zephiris
    26. Re:Much more specific than the summary suggests by migla · · Score: 1

      To me that sounds like it might not be prior art, then, but it does feel pretty obvious. You can't just fiddle an idea a bit and get a new patent, right?

      --
      Some of my favourite people are from th US; Vonnegut, Chomsky, Bill Hicks.
    27. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      It doesn't. The application is responsible for requesting authorization ahead of time before it does something the user might not have the rights to do.

    28. Re:Much more specific than the summary suggests by Theaetetus · · Score: 1

      To me that sounds like it might not be prior art, then, but it does feel pretty obvious. You can't just fiddle an idea a bit and get a new patent, right?

      Depends what you mean by "fiddle an idea a bit". If it's really a new bit of fiddling that no one's come up with before, it may not be obvious to do so, particularly if there are good reasons to do it. Like, you may think it's obvious to make a non-lethal mousetrap. Mousetraps are known after all. But then, you put it on the market and it sells millions in the first month. That kinda points to it not being obvious - otherwise someone would have done it.

    29. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      Maybe, but a patent does not only require no prior art.
      It must also be non-obvious. (or something... don't remember the exact wording)

    30. Re:Much more specific than the summary suggests by sgtrock · · Score: 1

      Read KSR vs Teleflex. This patent should not have been granted because it's an obvious extension to anyone skilled in the art.

    31. Re:Much more specific than the summary suggests by AshtangiMan · · Score: 1

      Sounds like some prior art.

    32. Re:Much more specific than the summary suggests by Theaetetus · · Score: 1

      Read KSR vs Teleflex. This patent should not have been granted because it's an obvious extension to anyone skilled in the art.

      Read KSR v. Teleflex. The burden of proof is on the one stating that a claimed invention is obvious, and that includes the Examiner. Specifically, the Examiner is not allowed to say that a claimed invention is "an obvious extension to anyone skilled in the art," without providing documentary evidence sufficient to make a prima facie case for obviousness. Otherwise, it's merely a conclusory statement and carries no legal weight.

    33. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      can someone give a legal opinion on whether or not Microsoft could sue someone over this patent without this particular feature? is it really required that every single criteria in the list be met exactly in order to constitute patent violation?

    34. Re:Much more specific than the summary suggests by sabt-pestnu · · Score: 1

      I think a large part of the hoo-raa about this patent is that the patent does not call out which elements are inventions, and which are prior art/previous patents/etc. So we get slapped with a wall of text the first bit we grok is "it's kinda like sudo...".

    35. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      Right, but the better question might be, is adding a help box, or allowing for selection of accounts (based on usage) non-obvious when viewed in light of the prior art. And the prior art doesn't necessarily need to be another patent.

    36. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      Its called 'prior art' which can negate a patent claim since clearly, they didn't invent it

    37. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      All I've seen in reading from the OP to here is proof that the concept of software patents is idiotic. How a technologicay ?advanced? country like the US could work so hard to try and stifle creative FBI king, I'll never understand. I'm glad I don't live or work there.

    38. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      From my understanding of how patent lawsuit work, the person getting sued doesn't have to do everything to be infringing and the patent doesn't have to cover everything a product is doing to claim it's infringing.

    39. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      You have to do everything specified in an independent claim to be infringing. Doing part of something covered in an independant claim doesn't count; if it did, the computing industry would be in far more hurt than it is already.

    40. Re:Much more specific than the summary suggests by PitaBred · · Score: 1

      That would be the "novel" part of the test. So, basically, confirming what I said, and adding nothing to the conversation in the process. Go team!

    41. Re:Much more specific than the summary suggests by s1lverl0rd · · Score: 1

      You censored the wrong word.

    42. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      It's also worth noting that the barrier for being "skilled" is pretty low. If it takes anything much more than an average new graduate (and anyone who's been to university knows how low the average is there) to come up with, it's not obvious enough. Not to mention that a lot of things are retrospectively obvious. It's trivial to say "I could have though of that", but nine times out of ten, you didn't, and certainly didn't apply for a patent.

    43. Re:Much more specific than the summary suggests by Anonymous Coward · · Score: 0

      Sudo enables you to execute tasks with different user privileges.
      Graphical interface is not news also. This is for a while now (e.g. firefox)
      Making program monitor your activities and work depending on that is not new (e.g. preload)
      Siting in background and doing things depending on other programs (any antivirus)

      So which part of this program is inovative and deserve monopoly rights because of great good for mankind?

      I would like to fill patent for browser which renders everything rotated 46 degrees counterclockwise. Then I'll wait till somebody finds that useful in spacestations.

    44. Re:Much more specific than the summary suggests by MobyDisk · · Score: 1

      Agreed. That's probably the real point. Monitoring the APIs to detect the need for privilege escalation, rather than configuring it ahead of time.

  4. Thought all was safe on the crazy patent front? by EraserMouseMan · · Score: 1, Troll

    What rock did you just crawl out from under?

    1. Re:Thought all was safe on the crazy patent front? by Captain+Splendid · · Score: 1

      What rock did you just crawl out from under?

      The one where /. FUDs TFS for pageviews?

      --
      Linux, you magnificent bastard, I read the fucking manual!
    2. Re:Thought all was safe on the crazy patent front? by Foofoobar · · Score: 1

      Does your mother count as a rock?

      --
      This is my sig. There are many like it but this one is mine.
  5. Using a *NIX desktop would suck... by stakovahflow · · Score: 4, Funny

    without "sudo". My thanks to Micro$oft for inventing that great program! --Stak

    --
    Holy happy hippy crap!
    1. Re:Using a *NIX desktop would suck... by marcansoft · · Score: 5, Funny

      Meh, I rarely use sudo. I guess I'm just not too used to it. So su me.

    2. Re:Using a *NIX desktop would suck... by sopssa · · Score: 2, Insightful

      Same here, sudo as it is incredibly inconvenient. When you're performing tasks that require root on Linux, you usually have to type in many commands at once to establish that task.

      It's a lot more convenient to just su for root, do the thing and then su back, instead of writing the goddamn sudo all the time.

    3. Re:Using a *NIX desktop would suck... by marcansoft · · Score: 3, Insightful

      Wait, you su back? You do realize that that leaves your root session in the background and complete accessible, right? The proper way to "unsu" is to just exit the shell (exit, ^D, etc).

    4. Re:Using a *NIX desktop would suck... by tomhudson · · Score: 1

      Meh, I rarely use sudo. I guess I'm just not too used to it. So su me.

      Everyone knows any real BOfH uses the root account, even if they're not supposed to. Hmmm - let me be the first to fix that - Especially if they're not supposed to.

    5. Re:Using a *NIX desktop would suck... by some_guy_88 · · Score: 1

      The good thing about sudo though is that your environment variables and path shortcuts like ~ still work because you're not actually switching users.

    6. Re:Using a *NIX desktop would suck... by internettoughguy · · Score: 1

      I used to run my Centos install as root, being a stupid windows user, and one day i was playing around in thunar (which actually has red bar at the top, to warn you not to..), and I accidentaly deleted my usr/var folder. In all fairness I learnt a lot about bash and the LFS heirachy trying to get back to Init 5 though, I think in the end I copied the folder over from a fedora ISO, still a bit glitchy to this day though.

    7. Re:Using a *NIX desktop would suck... by stakovahflow · · Score: 1

      Not exactly true... _sudo_ & _su_ use root's credentials by default (including env vars...) to run executables, scripts, etc. Neither _su_ nor _sudo_ is exactly infallible, but it is easier to escalate permissions on a system using _sudo_, if only for the ability to use a boot disk and edit the _sudoers_ file, adding the "NOPASSWD: ALL" option to the user's primary group (or, possibly, username), thus giving the group or user the ability to run any command, minus prompting for a password... ("sudo su" or "sudo passwd root", anyone?) Side note: Really, the easiest hack for gaining local Linux admin rights would have to be at the _grub_ boot loader prompt, editing the kernel string to add the "single" option. (especially Redhat based systems, btw...) One could just remount the / filesystem with write access and type "passwd root", changing the root password... This is another useless fact for another time, however... Regardless of whether you are a _su_ or _sudo_ user, beware (meaning: Yes, it is cool to be able to do anything on a system, but why bother risking system stability running everything as root?) Boys and girls, just remember to use your elevated permissions sparingly, for safety's sake! Alright, kidz, have phun! --Stak

      --
      Holy happy hippy crap!
    8. Re:Using a *NIX desktop would suck... by some_guy_88 · · Score: 1

      the easiest hack for gaining local Linux admin rights would have to be at the _grub_ boot loader prompt

      That's not a hack. If you have physical access to the machine you could also boot into another O/S or get out your screw driver and remove the hard disk if you wanted. Or just pull out a hammer and execute a very effective denial of service.

  6. This is why software patents shouldn't be allowed by PinkyDead · · Score: 5, Funny

    ...because I couldn't bothered reading all that shit.

    --
    Genesis 1:32 And God typed :wq!
  7. This just in! by Anonymous Coward · · Score: 0

    Groklaw posts an article against some action by Microsoft! Slashdot reports on it!

    Doubters abound! Questions Arise!

    Who's right? Who's wrong?

    Nobody cares.

    Interestingly, the word of the day is accuracy.

    1. Re:This just in! by CannonballHead · · Score: 1

      Who's right? Who's wrong?

      Neither, who's on first.

    2. Re:This just in! by donaggie03 · · Score: 1

      No, he's on second!

      --
      Three days from now?? Thats tomorrow!! ~Peter Griffin
    3. Re:This just in! by Anonymous Coward · · Score: 0

      No, What's on second.

  8. $andwich by bunhed · · Score: 1

    $> sudo bill make me a sandwich

    1. Re:$andwich by MrSenile · · Score: 1

      sudo: command not found: Microsoft has just charged your account for attempting to access 'bill' to make 'sandwich'.

    2. Re:$andwich by CannonballHead · · Score: 1

      What is this error syntax you use and where did it come from? ;)

      Microsoft Windows XP [Version 5.1.2600]

      (C) Copyright 1985-2001 Microsoft Corp.

      C:\Documents and Settings\Administrator>sudo
      'sudo' is not recognized as an internal or external command,
      operable program or batch file.

      C:\Documents and Settings\Administrator>

    3. Re:$andwich by sopssa · · Score: 1

      His Linux distro is pretty fucked up if it lets Microsoft to bill him.

    4. Re:$andwich by MrSenile · · Score: 1

      Well damn. I knew I shouldn't have bought SCO's version...

    5. Re:$andwich by DaVince21 · · Score: 1

      Yeah, but on Windows you can do:

      format c:

      without complaints.

      Well, maybe like 10 years ago.

      --
      I am not devoid of humor.
  9. Kill software patents by rolfwind · · Score: 4, Interesting

    The big industry writes them up just as protection from patent trolls and then collude to keep small competition out (ie Microsoft was threatening that Linux was stepping on its patents back in the day).

    Patents were made to spawn innovation - bypassing secretive guilds by incentivizing the opening of knowledge to public domain in exchange for a limited time monopoly. Projects and society are way too fluid now to keep many inane details secret anyway. There needs to be a study of which types of patents coming in provide useful knowledge to the People, and which majority are just wastes dumps of text - and amend the system accordingly.

    I would urge the USA to do this now, while it is the leading superpower in which others follow suit. It may have been to our advantage in the past, but not so in the future, imo.

    1. Re:Kill software patents by Anonymous Coward · · Score: 0

      First you have do define what are software patents! really there isn't such thing!

      For example, say I built a mechanical lock, such that when you insert the wrong key, a cover on the lock's front panel open, and display a list of people who have the right key (and their phone numbers?)

      Is the above a novel idea? perhaps. If I describe how to build my contraption and the patent office determines there isn't prior art, and its non-obvious (which it is imo) I will be granted a patent.

      How's this different from the MS contraption? it's not. And no software is involved.

    2. Re:Kill software patents by JesseMcDonald · · Score: 1

      Patents were made to spawn innovation - bypassing secretive guilds by incentivizing the opening of knowledge to public domain in exchange for a limited time monopoly. Projects and society are way too fluid now to keep many inane details secret anyway.

      True. However, even if it were possible to keep these details secret, I would still say that secrets which you have a chance of learning or rediscovering are superior to public knowledge you're coercively prevented from using.

      I'm opposed to all patents, but if they're going to exist anyway I wish the PTO would at least attempt to limit the rate at which they're granted. For one thing, it would reduce the difficulties they have enforcing the "non-obvious" requirement. My suggestion would be that they grant a specific number of patents each year; perhaps 100 or 500. All the patent applications would be accepted confidentially, and an impartial panel representing the PTO would periodically choose the applications whose publication represents the greatest present benefit to the PTO's constituents, the public, at expiration. The duration of the patent would be chosen by the applicant. Present benefit decreases the longer you have to wait, so a patent with a longer duration offers less present benefit than the same patent with a shorter duration and would be less likely to be accepted. Estimating the costs and benefits of each patent application remains a problem, but the current approach—simply assuming that benefits outweigh costs for every "non-obvious" patent—is even worse in this regard, as no cost/benefit analysis is even attempted.

      The accepted applications would be published immediately, so that others know not to implement them, and would confer on their inventors the traditional transferable patent-monopoly privilege for the requested duration from acceptance, subject to invalidation based on prior art (or fraud). The rejected applications would be destroyed for confidentiality's sake, but could be resubmitted for the next session.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    3. Re:Kill software patents by JesseMcDonald · · Score: 1

      ... whose publication represents the greatest present benefit to the PTO's constituents, the public, at expiration.

      I just realized that reordering certain phrases in this sentence "for clarity" completely changed the meaning. What I intended was:

      ... whose future publication following expiration represents the greatest present benefit to the PTO's constituents, the public.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    4. Re:Kill software patents by Anonymous Coward · · Score: 0

      [...] bypassing secretive guilds by incentivizing the [...]

      And here we were, thinking you were a normal human being. Get out, lawyer/CEO/marketeer scum!

    5. Re:Kill software patents by Anonymous Coward · · Score: 0

      The problem is that US is behind EU, in most countries over here software patents are not recognised nor practised.
      Well, the US is turning into a 3rd world country anyhow :P

    6. Re:Kill software patents by Anonymous Coward · · Score: 0

      in exchange for a limited time monopoly.

      15 years is not a limited time when you're talking about computer science.

    7. Re:Kill software patents by True+Grit · · Score: 1

      Patents were made to spawn innovation - bypassing secretive guilds by incentivizing the opening of knowledge to public domain in exchange for a limited time monopoly. Projects and society are way too fluid now to keep many inane details secret anyway.

      The patent concept was also invented with the idea of the physical widget in mind, at a time when making things was an expensive proposition. A real physical 'thing' that had to be *manufactured*. The goal: make companies more likely to make the massive investments in R&D, time, effort, material and capital acquisitions, tooling, retooling, e.g. making the tool that made the tool that finally made the widget itself, and then the final manufacturing process, renting the floor space, hiring the workers, setting up the 'assembly line'. For many 'real widgets' this is all expensive as hell. A limited monopoly was seen as a way to offset those expenses. As far as that all goes, it kinda makes sense, although we could always quibble about the length of the granted monopoly, or other relatively minor things, but...

      Where is the equivalent massive expenditures involved in creating software? Software is not physical, its electronic, ephemeral (and never mind also being closer to an expression of mathematical algorithms than to something you see and hear and feel and touch like a physical thing). Most of the 'manufacturing process' goes on in the coders' heads, not on a shop floor.

      And the 'worst-case' scenario (or best-case depending on your pov): Capitol investment? One cheap beige-box computer. Raw materials? Caffeine & cold pizza. Infrastructure? Mom's basement.

      As soon as you look at the history of the patent and *why* it was created, the more today's picture seems out of focus. Its goal was never to simply reward the one who 'got there first', its original purpose was to help offset the real costs of inventing, so it would be financially worthwhile for someone to even try to do it at all. This is why it was simply a bad idea to apply it to a non-physical widget, because the real and practical reasons for doing this with physical widgets, do not really apply to software.

      And don't even get me started on 'business method' patents... grrr...

  10. Stop with the alarmist headlines already by techno-vampire · · Score: 1, Insightful

    I know Slashdot loves to exaggerate things in headlines, but this is absurd. Microsoft has not patented sudo's behavior. At most, it has applied for a patent who's claims could be twisted to make it look like they're trying to patent sudo. Calm down, everybody, it's just an application, the patent hasn't been awarded and, if it's as ridiculous as the summary claims (and I have my doubts about that, too) it's unlikely to be granted.

    --
    Good, inexpensive web hosting
    1. Re:Stop with the alarmist headlines already by alexborges · · Score: 1

      Yes... your paranoia, people, is not justified. Microsoft never attempts to patent the obvious and then claim bogus issues with competitors.

      --
      NO SIG
    2. Re:Stop with the alarmist headlines already by Sockatume · · Score: 0

      So your argument is sometimes, therefore always? Jumping at shadows and concocting specious justifications post hoc makes Microsoft's opponents look like quacks.

      --
      No kidding!!! What do you say at this point?
    3. Re:Stop with the alarmist headlines already by lilo_booter · · Score: 2, Interesting

      Yes, MS has applied for a patent on sudo's behaviour and that is what the title is ridiculing - as should we. Regardless of their success or failure, we're entitled to point and laugh.

    4. Re:Stop with the alarmist headlines already by reebmmm · · Score: 3, Informative

      Not true. This is an ISSUED patent; see the patent number: 7,617,530. You can also check its status in public pair (http://portal.uspto.gov/external/portal/pair):
      10-21-2009 ISSUE.NTF Issue Notification 1
      10-01-2009 IFEE Issue Fee Payment (PTO-85B) 1
      10-01-2009 LET. Miscellaneous Incoming Letter 1
      10-01-2009 WFEE Fee Worksheet (PTO-875) 2
      10-01-2009 N417 EFS Acknowledgment Receipt 2
      08-24-2009 NOA Notice of Allowance and Fees Due (PTOL-85) 10

      I'll draw your attention to the first and last lines in the excerpt from the file wrapper.

      That said, the claims DO NOT cover sudo.

    5. Re:Stop with the alarmist headlines already by jack2000 · · Score: 2, Funny

      Microsoft's behavior is not a shadow, rather it's darkness, a very specific kind of darkness mind you, it grows, squirms and twitches, it has physical form and it's like a cluster of tentacles as it grabs towards you..

    6. Re:Stop with the alarmist headlines already by techno-vampire · · Score: 1
      Yes, MS has applied for a patent on sudo's behaviour and that is what the title is ridiculin

      No, the title is claiming that Microsoft has patented that behavior, and that's what I'm objecting to.

      --
      Good, inexpensive web hosting
    7. Re:Stop with the alarmist headlines already by techno-vampire · · Score: 1
      Not true. This is an ISSUED patent;

      If so, the summary is wrong because it says Microsoft has filed a patent, not been awarded.

      --
      Good, inexpensive web hosting
    8. Re:Stop with the alarmist headlines already by lilo_booter · · Score: 1

      Got that from what you said the first time round - and since you repeated yourself, so shall I - we're still entitled to point and laugh.

    9. Re:Stop with the alarmist headlines already by alexborges · · Score: 1

      My argument is always, therefore always.

      The attack on Open Source through SCO by proxy was not a "shadow". It was a blatant, obvious attempt to instil fear in the market, and the same goes for the "communist OS" shit they peedled a few years back. The shit they pass as an ODP spreadsheet is not a shadow. Their ISO tactics for their fucking ooxml shit is not a shadow.

      No shadows man. This is rock solid evidence that they are out to get us. And we do and will strike back every single time.

      This is war. Im used to it. I suggest you get used to it too.

      --
      NO SIG
    10. Re:Stop with the alarmist headlines already by MrSenile · · Score: 1

      Microsoft's behavior is not a shadow...

      I think Microsoft see themselves more as Vorlons, personally...

    11. Re:Stop with the alarmist headlines already by Dunbal · · Score: 1

      At most, it has applied for a patent who's claims could be twisted to make it look like they're trying to patent sudo.

            And this doesn't bother you? Obviously you haven't hanging been around many IP lawyers lately...

      --
      Seven puppies were harmed during the making of this post.
    12. Re:Stop with the alarmist headlines already by techno-vampire · · Score: 1

      I'm not saying it doesn't. My only complaint is that AFAICT not only is the headline overly alarmist, it's directly contradicted by TFS.

      --
      Good, inexpensive web hosting
    13. Re:Stop with the alarmist headlines already by selven · · Score: 1

      An application for a patent is an intent to have a patent and is thus morally equivalent (in terms of Microsoft, not the USPTO) to having the patent. A failed bank robbery is still a crime - the intent to rob a bank was there.

    14. Re:Stop with the alarmist headlines already by Anonymous Coward · · Score: 0

      So your argument is sometimes, therefore always? Jumping at shadows and concocting specious justifications post hoc makes Microsoft's opponents look like quacks.

      Do as I did and re-read his post. You injected the word "always" into the discussion. Nice strawman attempt. What he was saying is that, having done so in the past, it is worth consideration that MS has not changed its ways and that it would not be untoward to speculate that they might be acting in the same manner in this case.

    15. Re:Stop with the alarmist headlines already by True+Grit · · Score: 1

      I know Slashdot loves to exaggerate things in headlines, but this is absurd.

      No sir, this is not absurd... this *is* Slashdot!

      I'd guess the editors consider any TFA that generates 600+ posts to be a "good day's work", irrespective of the presence or absence of exaggeration and/or absurdity, *especially* if they don't have to invent the absurdity themselves, but merely link to it...

      :)

    16. Re:Stop with the alarmist headlines already by Sockatume · · Score: 1

      It would help if you demonstrated "always" before concluding it.

      War? This isn't fucking Hackers.

      --
      No kidding!!! What do you say at this point?
  11. "patent this obvious idea" by Anonymous Coward · · Score: 5, Funny

    Patent Office: "Rejected."

    Microsoft: "sudo patent this obvious idea"

    Patent Office: "Okay."

    With apologies to xkcd.

  12. They didn't get it on their first try... by BobMcD · · Score: 5, Funny

    MS: Grant me this patent.

    USPTO: No!

    MS: Sudo grant me this patent.

    USPTO: Okay...

    1. Re: They didn't get it on their first try... by IorDMUX · · Score: 3, Funny

      alias sudo='wouldyoukindly'

      It seemed necessary...

      --
      >> Standing on head makes smile of frown, but rest of face also upside down.
    2. Re:They didn't get it on their first try... by BobMcD · · Score: 0, Redundant

      Okay, since that got modded up, I feel guilty. I totally stole it.

      For bonus points, I stole it from what must be the Obligatory xkcd:

      http://xkcd.com/149/

    3. Re:They didn't get it on their first try... by MrNemesis · · Score: 2, Funny

      > sudo make me a sandwich

      > I'm sorry Dave, but under USPTO 7617530 I can't allow you to do that

      --
      Moderation Total: -1 Troll, +3 Goat
  13. Just like XKCD by kabloom · · Score: 0, Redundant

    Microsoft walked up to the patent office, and said "Give me a patent." The patent office said "No, there's prior art." Microsoft asked again "Sudo Give me a patent." The patent office replied "OK."

    http://xkcd.com/149/

  14. Link by Anonymous Coward · · Score: 0

    http://xkcd.com/149/

    1. Re:Link by Anonymous Coward · · Score: 0

      That's not a link. It's a URL. Loser.

  15. Interesting circumlocution by jfengel · · Score: 3, Insightful

    In an attempt to patent a thing rather than the software itself, they say:

    One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to perform acts comprising:

    In other words, it's not the operation itself, or the software, but the actual _disc_ that they're claiming. The medium, not the message, as it were. At least it's a physical thing.

    I don't know if "downloaded software" would violate the patent, or if they'd try to claim that having it on the server's discs would violate it. (Surely they wouldn't try to claim that your hard disc on which you've downloaded it would violate the patent, would they?)

    1. Re:Interesting circumlocution by Theaetetus · · Score: 3, Informative

      In an attempt to patent a thing rather than the software itself, they say:

      One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to perform acts comprising:

      In other words, it's not the operation itself, or the software, but the actual _disc_ that they're claiming. The medium, not the message, as it were. At least it's a physical thing.

      Yep... This makes it an "article of manufacture", rather than a "process". The whole Bilski thing up before the Supreme Court only applies to processes; an article of manufacture comprising computer-readable instructions isn't affected, under In Re Beauregard.

      I don't know if "downloaded software" would violate the patent, or if they'd try to claim that having it on the server's discs would violate it. (Surely they wouldn't try to claim that your hard disc on which you've downloaded it would violate the patent, would they?)

      Oh, yeah, they would. You download the software and save it to your hard drive... you just created a computer-readable media (the hard drive) having computer-readable instructions (the software) that, when executed, cause the computer to perform those acts. You're infringing by making and using the patented invention (you don't need to make all the parts of the invention - you don't need to have a hard drive fabrication lab... You just need to be the one to 'assemble' the invention).

      But don't worry, they wouldn't sue you. Instead, they'd go after the people who sold you the software, as it's a component of a patented article of manufacture with no noninfringing uses.

    2. Re:Interesting circumlocution by Chris+Burke · · Score: 1

      In other words, it's not the operation itself, or the software, but the actual _disc_ that they're claiming. The medium, not the message, as it were. At least it's a physical thing.

      That's always the case. Technically, a pure algorithm (software) is still unpatentable. So they always throw in the "A medium to store the code, and a general purpose computer to execute it" bit to make the software a component of a physical device that does something in the real world rather than abstract math and thus a patentable invention.

      --

      The enemies of Democracy are
    3. Re:Interesting circumlocution by Anonymous Coward · · Score: 1, Informative

      IANAL but that's what's known as a CRM (computer-readable media) or Beauregard claim. For a deeper understanding see here:

      http://www.1201tuesday.com/1201_tuesday/2009/09/happy-birthday-beauregard.html

      If you can't be bothered, the point is by saying CRM Microsoft can go after someone who makes software to do this as well as/rather than the end user.

    4. Re:Interesting circumlocution by Anonymous Coward · · Score: 1

      Wrong....given past actions, they are likely to sue BOTH the reseller of the software, AND the user who downloaded it, so as not to miss a potential cent.

  16. Just curious by Anonymous Coward · · Score: 0

    Patent troll has been a business model for some time now, just wondering if Patent Troll was also a job title or at least the name of a department? Are they kept in the basement or is Microsoft upscale enough to build them their own bridge to live under?

    1. Re:Just curious by spitzak · · Score: 1

      "Patent troll" means a company that does not produce any product and only sues for patent infringements.

      This is not what Microsoft is doing, Microsoft is either making a defensive patent or actively trying to prevent competitors by outlawing obvious solutions, depending on your pov.

    2. Re:Just curious by internettoughguy · · Score: 1
      Since we're being pedantic: It remains to be seen if they actually do use this patent, or if they troll some Linux or OSX tool with it.

      In another instance, Microsoft has for all purposes phased out FAT, that doesn't stop them trolling TomTom with it.

    3. Re:Just curious by spitzak · · Score: 1

      I think FUD is the correct term for "Linux infringes hundreds of our patents but we won't say which ones".

      Supposedly the TomTom suit was a patent defense, however I question it as there were several other navigation-specific patents they used as well and it seems strange that they threw in one that every camera manufacturer in the world is violating.

      A "troll" actually tries to collect money. Microsoft is not using patents this way.

  17. So what, they can have it. by smoker2 · · Score: 0, Flamebait
    sudo is shit. What is the point anyway ? Either you've got root, or you assume it with sudo and have exactly the same privileges.

    sudo allows a permitted user to execute a command as the superuser or another user, as specified in the sudoers file. The real and effective uid and gid are set to match those of the target user as specified in the passwd file and the group vector is initialized based on the group file (unless the -P option was specified). If the invoking user is root or if the target user is the same as the invoking user, no pass- word is required.

    1. Re:So what, they can have it. by CannonballHead · · Score: 1

      As I recall, you can set up sudo to only allow certain commands. If you are careful with what commands you allow sudoers to run, you can limit the amount of root activity they are allowed.

    2. Re:So what, they can have it. by John+Hasler · · Score: 1

      > sudo is shit. What is the point anyway ? Either you've got root, or you
      > assume it with sudo and have exactly the same privileges.

      Wrong.

      man sudo
      man sudoers

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    3. Re:So what, they can have it. by HeronBlademaster · · Score: 1

      It's not about having root, it's about not having a root shell open. If I need to run /bin/foo as root, then it's preferable to run it with sudo than by invoking "su" and then running it as root, because with sudo I do not run the risk of forgetting to exit the root shell and then doing something else stupid in that shell.

      Your argument may now be "well don't be stupid", but that's an entirely different issue, and doesn't mean we shouldn't have sudo around.

    4. Re:So what, they can have it. by Culture20 · · Score: 1

      I never run any sudo command except for "sudo su -" any more. I've had too many times where sudo cached cred and ran without asking for my password, then out of habit I typed the password anyway. I'd rather have a root shell since it's what I want most of the time anyway.

    5. Re:So what, they can have it. by Dunbal · · Score: 1

      What is the point anyway ? Either you've got root, or you assume it with sudo and have exactly the same privileges.

            It's one thing to have to give a single (presumably trusted, limited) process permission to execute, and another thing entirely to blindly trust the OS and give it permission to do anything, anytime (that's called Windows).

            It's like having your dad's car keys when he's on vacation out of town, vs. driving your dad somewhere.

           

      --
      Seven puppies were harmed during the making of this post.
    6. Re:So what, they can have it. by icebraining · · Score: 1

      su -c /bin/foo

    7. Re:So what, they can have it. by HeronBlademaster · · Score: 1

      That's fine, but that has one big problem: it requires users to know the root password. On a large multi-user system, that's likely undesirable.

      A big benefit of sudo is that (if I'm not mistaken) it lets you specify particular programs that users can run. For example, I may want a user to be able to "/etc/init.d/apache2 restart", but nothing else.

    8. Re:So what, they can have it. by HeronBlademaster · · Score: 1

      I usually use a root shell myself, but you have to admit it's not always the best answer. (For example, multi-user environments where you don't want normal users to have full root access but where they still need some elevated privileges.)

    9. Re:So what, they can have it. by Anonymous Coward · · Score: 0

      sudo is shit. What is the point anyway ? Either you've got root, or you assume it with sudo and have exactly the same privileges.

      Isn't it a shame that there will always be the dull students in the back of the room who always seem to miss the point?

  18. How is any part of that flamebait? by HangingChad · · Score: 2, Interesting

    Just because it's software doesn't mean that it can't be brilliant and stunningly innovative.

    The suggested punishment might be a little extreme, but the idea is sound. We need some kind of penalty for companies filing junk patents for the electronic equivalent of exchanging oxygen for carbon dioxide across a thin, moist membrane.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  19. Seems to be describing what Ubuntu (Gnome) does by ericthughes · · Score: 3, Interesting

    when you attempt to mount a drive that is not defined in fstab. Ubuntu pops up a "enter your password" dialog. M$ maybe up to some dirty old tricks here...

    1. Re:Seems to be describing what Ubuntu (Gnome) does by CannonballHead · · Score: 1

      Gnome (or whatever the name of the program it uses to do mount "management", I forget), I believe, wraps the mounts. If you simply run "mount" when not logged in as root, it fails and says you don't have permission to do that. Presumably, using a GUI is no different ... except that the GUI knows you need to do it with sudo, so it does it for you. It's little different from writing your own script "mount" to override the real "mount" ... and simply have your script run mount as sudo. That's not UAC, that's just wrapping a command with sudo because you know it requires it.

  20. ARE YOU KIDDING? by gbutler69 · · Score: 1

    Look at Ubuntu 8.04, 8.10, and 9.10 and tell me how this is different? It isn't.

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  21. It's the other way round actually... by pandrijeczko · · Score: 4, Funny

    ...with Windows' lax control of permissions allowing just about anybody to run as a super user, surely they should have a patent for "sudon't" which would probably be infinitely more useful?

    --
    Gentoo Linux - another day, another USE flag.
    1. Re:It's the other way round actually... by Anonymous Coward · · Score: 0

      Wait, you mean when I create a Windows "super user" account (a.k.a. administrator), I can run as a super user?

      Wait wait, can just about anybody create a "non-super user" account and use that instead if you didn't want to run as a super user?

      Oh yea, you can.

  22. Liunx schminux by wmduncan · · Score: 1

    Come one now - your bias is showing... sudo existed on UNIX before Linus Torvalds was a gleam in his father's eye....

    1. Re:Liunx schminux by Me!+Me!+42 · · Score: 1

      Glad to see someone else is paying attention.
      Good work!

      --
      -- My apologies if the above facts contain any opinions, or vice versa! --
    2. Re:Liunx schminux by spitzak · · Score: 3, Informative

      You are thinking of just the root account, or maybe "su" which is really "login as root".

      "sudo" as in "run a single command as root and furthermore examine the commands before running them and restrict them to a set, and furthermore examine the user trying to run sudo to select the restricted set" was developed after Linux was popular.

      However I believe a good deal of the work was done on BSD and other Unixes as well.

    3. Re:Liunx schminux by Anonymous Coward · · Score: 0

      $ man su
      "The su command is used to become another user during a login session.
      Invoked without a username, su defaults to becoming the superuser."... ..."-c, --command COMMAND
      Specify a command that will be invoked by the shell using its -c."...

      Can su be used as an privilege escalation tool?
      user1@home:~$ su user2 -c "rm -rf /home/user2"
      Yes, it'll do the job.

      So, should the "freedom" of writing some kind of GUI to run some kind of software as another user be taken away from us (I bet it'd be a matter of a few hours)?
      Hell no, software can be protected, ideas really *should* not.

    4. Re:Liunx schminux by value_added · · Score: 1

      You are thinking of just the root account, or maybe "su" which is really "login as root".

      Aaargh. su(1) is certainly not "login as root".

      NAME
          su -- substitute user identity
       
      SYNOPSIS
          su [-] [-flms] [-c class] [login [args]]
       
      DESCRIPTION
        The su utility requests appropriate user credentials via PAM and switches
        to that user ID (the default user is the superuser). A shell is then
        executed.

    5. Re:Liunx schminux by Anonymous Coward · · Score: 0

      You are thinking of just the root account, or maybe "su" which is really "login as root".

      su switches to a user. If not specified, the target user is root.

      Just a slight correction.

    6. Re:Liunx schminux by Anonymous Coward · · Score: 0

      >> You are thinking of just the root account, or maybe "su" which is really "login as root".

      Hey Dumbass,
      su has more than one feature. Check out the -c option in the man page.

    7. Re:Liunx schminux by k8to · · Score: 1

      sudo predates linux.

      --
      -josh
    8. Re:Liunx schminux by k8to · · Score: 1

      0.5 seconds spent searching the internet:

      "The program was originally written by Bob Coggeshall and Cliff Spencer "around 1980" at the Department of Computer Science at SUNY/Buffalo. The current version is under active development and is maintained by OpenBSD developer Todd C Miller and distributed under a BSD-style license.[5]"

      http://en.wikipedia.org/wiki/Sudo

      --
      -josh
  23. What does functionality have to do with anything? by 91degrees · · Score: 3, Insightful

    There are thousands of patents for devices that duplicate the functionality of another. Hell, the diesel engine has exactly the same function as a petrol engine, and much of the functionality of a Newcomen engine (pressure difference driving pistons to provide a motive force).

    The patent is on the process. Not the end result.

    Now the process is pretty much indistinguishable from sudo as well, but if you're going to criticise at least criticise for the right reasons.

  24. This IS already being done in Linux by gbutler69 · · Score: 2, Interesting

    And I'm not just talking about sudo/gksudo etc....look at "Policy Kit". This is EXACTLY what this Patent describes. EPIC FAIL Microsoft! The FREE SOFTWARE WORLD has OUT INNOVATED YOU AGAIN! Been doing this for at least more than a year. Been in design/documentation/talked about for even longer.

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:This IS already being done in Linux by CannonballHead · · Score: 1

      This is EXACTLY what this Patent describes. EPIC FAIL Microsoft! The FREE SOFTWARE WORLD has OUT INNOVATED YOU AGAIN! Been doing this for at least more than a year. Been in design/documentation/talked about for even longer.

      And UAC was in Vista, which was publically released in 2007, almost three years ago (it was released in January of 2007)... maybe MS should claim prior art. ;)

    2. Re:This IS already being done in Linux by dgatwood · · Score: 4, Insightful

      This patent was filed more than four years ago, in April of 2005. This filing predates Red Hat's announcement of PolicyKit by about a year. And PolicyKit probably wouldn't cover this even if it predated the Microsoft concept because it doesn't meet the "automatic" criteria, AFAIK.

      And for anyone thinking that this is a patent on sudo, it is not. It also is not a patent on Apple's AuthorizationExecuteWithPrivileges, though it is much closer to that. It differs from the Mac OS X design in that it:

      • Executes when the privilege violation occurs without requiring the app to be aware. This is, of course, a really dangerous idea for reasons I'll get into momentarily.
      • Displays a list of accounts with the appropriate privilege. This is arguably not that useful on most OSes, but it is important if you have a rights system that is way too complicated....

      It further differs from sudo in that it presents a GUI (in addition to the two ways above).

      Regarding launching a GUI window when a privilege violation occurs, this is precisely why Windows got the "Allow or Deny" reputation it got. You really don't want to authorize every little action. Further, when it comes to a typical desktop environment, a rights system should not be so complex that there are more than about two classes of users anyway---those who have the rights to modify system files and those who are limited to their own files. Therefore, something like sudo, PolicyKit, AuthorizationExecuteWithPrivileges, etc. is generally a much better design because it puts the application in control of the experience and allows you to run a series of actions with elevated privileges, forcing apps to be designed with proper privilege separation, and reserving elevated privileges for only the minimum portion of the code necessary. The Windows "automatically throw up a GUI when you get a permission denied" design has a significant risk of creating user indifference towards important security notifications, which results in a significantly less secure system in the long run.

      Also, I'm under the impression (based on the patent) that Windows is temporarily elevating the privileges of the application itself, which means that you now have a much larger chunk of code that must be checked for security holes, lest malicious individuals co-opt the application for nefarious purposes. Such a design also makes it very hard to adequately use code signing to ensure the authenticity of the code running with elevated privileges, thus allowing security holes in the app to readily be exploited and turned into the equivalent of root holes just by the user clicking "Allow".

      In short, it's a terrible security design filled with myriad fundamental design flaws, all codified in a patent filing for all to mock. I certainly won't lose sleep over this patent getting approved. No one should reasonably want to implement the sort of security architecture that would violate this patent.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    3. Re:This IS already being done in Linux by jim_v2000 · · Score: 1

      No, it's not like PolicyKit either. You apparently have no idea what the patent is describing. Let me help you. If you want to do something on your computer, but you don't have the rights, and your account does not have rights elevation privileges, the system described in this patent will show you an account that does have access, and you can type in the password for that account to get the job done. As far as I know, sudo, gksudo, and PolicyKit do not do this.

      Everyone's getting caught up in the privilege escalation part and missing that the whole point of the patent is that it allows you use the rights of a different user to perform an action, and it shows you that user instead of you having to type in a name.

      --
      Don't take life so seriously. No one makes it out alive.
    4. Re:This IS already being done in Linux by WoOS · · Score: 1

      > Executes when the privilege violation occurs without requiring the app to be aware.

      Well, that also seems to be patented previously, at least in Europe, http://depatisnet.dpma.de/DepatisNet/depatisnet?action=bibdat&docid=EP000001255394B1 (couldn't find an english version). Admittedly on a grander scale (network instead of computer) but I doubt that step has sufficient patentability.

      The thing which shocked me most about the patent is that it completely lacks the "Previous Arts" section. I had been looking forward on MS winding itself in explaining why what they invented was not covered by previous art like Ubuntu (since 2004). But nothing! If the USPTO granted that without requiring detailed differentiation in the patent from previous art, it should really be closed.

    5. Re:This IS already being done in Linux by EvanED · · Score: 1

      The first parts of your post are fine... but I have problems starting about here:

      Also, I'm under the impression (based on the patent) that Windows is temporarily elevating the privileges of the application itself, which means that you now have a much larger chunk of code that must be checked for security holes, lest malicious individuals co-opt the application for nefarious purposes.

      How is this different from the Linux sudo model or Apple's AuthorizationExecuteWithPrivileges? With that model, you start a process under sudo and it gets admin rights for the duration of the process.

      By the "proportion of the code running with elevation" metric, Windows should actually be better in this regard, since the time between when the process starts to when it first elevates will be run without admin rights.

      Such a design also makes it very hard to adequately use code signing to ensure the authenticity of the code running with elevated privileges...

      As opposed to Sudo, which doesn't check the signature of the executable being run at all (at least AFAIK)?

    6. Re:This IS already being done in Linux by dgatwood · · Score: 1

      How is this different from the Linux sudo model or Apple's AuthorizationExecuteWithPrivileges? With that model, you start a process under sudo and it gets admin rights for the duration of the process.

      With AuthorizationExecuteWithPrivileges, privileges are elevated for a single helper binary that (assuming it was written well) is a narrowly defined piece of code that does the task requiring elevated privileges and then quits, shedding any additional privileges it may have obtained. This makes a much smaller target for attack because in order to compromise the security of the root helper, you would have to first compromise the non-root application sufficient to execute arbitrary code, then find a second exploitable vulnerability in the much smaller root helper code. By contrast, if you elevate the privileges of the main process, you just have to wait for the user to do something that elevates privileges on the process, then compromise the much larger, more easily attacked main application process.

      With sudo, reality is somewhere in-between, because you could conceivably type "sudo -s" or "sudo /usr/bin/startx", but I think you'll still agree that for most practical uses, running sudo is safer than su because your shell isn't elevated in privileges and you can't hose certain things without explicitly requesting extra privileges with sudo.

      As opposed to Sudo, which doesn't check the signature of the executable being run at all (at least AFAIK)?

      I was thinking more of the ServiceManagement framework in Mac OS X (new in 10.6), whose SMJobBless function requires the helper to be signed and provides additional security around that signature.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    7. Re:This IS already being done in Linux by shutdown+-p+now · · Score: 1

      With AuthorizationExecuteWithPrivileges, privileges are elevated for a single helper binary that (assuming it was written well) is a narrowly defined piece of code that does the task requiring elevated privileges and then quits, shedding any additional privileges it may have obtained. This makes a much smaller target for attack because in order to compromise the security of the root helper, you would have to first compromise the non-root application sufficient to execute arbitrary code, then find a second exploitable vulnerability in the much smaller root helper code. By contrast, if you elevate the privileges of the main process, you just have to wait for the user to do something that elevates privileges on the process, then compromise the much larger, more easily attacked main application process.

      Nothing stops you from using the latter scheme (with a single elevated binary running in a separate process) on Windows, either. It has a complete set of API to request and control elevation.

        Unfortunately, a lot of existing software, written for XP, doesn't do that, and still needs elevated privileges. The only options are to run it elevated from the get go, or to implement the scheme described in the patent (not using it is another option, but it may be unacceptable depending on the software in question).

    8. Re:This IS already being done in Linux by gzipped_tar · · Score: 1

      consolehelper?

      --
      Colorless green Cthulhu waits dreaming furiously.
    9. Re:This IS already being done in Linux by kbielefe · · Score: 1

      How is this different from the Linux sudo model

      That's actually a good question. I can imagine Microsoft engineers asking the same question and concluding that people think sudo is a good thing, so automatic user friendly sudo everywhere is by extension a good thing. That belies a fundamental misunderstanding of what makes sudo good.

      The answer is not in sudo's capabilities, but in how sudo is typically used as one tool in the context of an overall security policy. There are a select few applications that automatically prompt for privilege elevation, and those applications are carefully monitored, do the least amount possible with increased privileges, and the application developers know those apps will be run with administrator privileges and design and are held accountable for security accordingly.

      There are other applications that are much easier to run with root privileges. Take xsane (scanning software) as an example. It doesn't automatically prompt for privilege elevation. It will give you a permission denied message. If you run it with sudo, it pops up a big scary warning saying proceed at your own risk. That's because in order to scan files, you need read and write access to one device, not god-like power over the entire system, and if you ask on the forums, you will be told precisely how to give xsane just the permissions it needs, and no more. If one were to be implemented, people would want the Linux version of the software in this Microsoft patent to do the same thing, not prompt for a password that opens up a ton more potential security holes.

      Knowing when to use something less powerful instead of sudo is an important, pervasive, and ongoing conscious part of the "Linux sudo model." That's how it's different.

      --
      This space intentionally left blank.
    10. Re:This IS already being done in Linux by EvanED · · Score: 1

      I can imagine Microsoft engineers asking the same question and concluding that people think sudo is a good thing, so automatic user friendly sudo everywhere is by extension a good thing.

      I suspect it was more an effort to make programs that assume admin rights (of which we all know there are tons) less obnoxious. I mean, that'd really suck to work with a program for 10 minutes, go to do something, and have the operation denied because you didn't start it with sudo. That's the sort of thing that would cause all but the very very most security-focused people (i.e. not me) to turn off UAC.

      (After all, Windows NT has had the ability to start programs as other users (like su) for a long time now; that particular ability isn't new. It's only the on-demand escalation that is.)

      Knowing when to use something less powerful instead of sudo is an important, pervasive, and ongoing conscious part of the "Linux sudo model." That's how it's different.

      I still don't particularly buy the differences you state though, or at least buy that it's a particularly useful tradeoff.

      First of all, there's definitely a security-vs-usability tradeoff here. If xsane fails with a permission denied error, the user has to go and investigate how to set up things right, then do it. Even if the permission denied dialog itself gave instructions, users don't really read them. (Though in that extreme, I start to lose empathy.) Compare that to the UAC world, where you get a popup that you have to clear to continue. Lose a little security, but gain quite a bit of convenience. (Especially if it's something you do infrequently. If you do it often, then setting things up right with the Unix model will mean it works smoothly, while you'll still get a UAC prompt each time with the Windows model.)

      Now note that even the security increase in the Unix model isn't absolute. How do you set it up to get the necessary permissions? You add yourself to the 'scanner' group or whatever to get permissions to the necessary device nodes. Okay, in the case of the scanner, this is not a big deal, but what this means is that if you trust a particular program more than you trust other programs you run from having access to a resource, then you should run that program as root. This fact shouldn't be a surprise; it's basically why we need sudo in the first place.

      But my contention is that the set of programs that fit the "asks for UAC rights on Windows but would be better satisfied by more granular permission changes" (like xsane) is very small, and that almost everything that asks for UAC elevation falls into the "run this program as sudo" category. Certainly my anecdotal "feeling" supports this contention, but I also did a slightly more careful experiment when I first switched to Vista. The result of it was that almost every elevation request I got for a month (I kept a log) was for some action where the equivalent on Linux would have required sudo rights anyway. The main exceptions were (1) changing environment variables (in Vista the terrible dialog where you change user-local and system-wide variables is the same, and MS didn't go out of their way to make it possible to change user-local ones) and (2) this one crappy hardware monitoring software I was using for some reason.

      Basically everything else was like system config changes that would have required root on Linux or program installations, which also require root on Linux. (Well, okay, you can usually do configure/make/make install without root. But only then if you're really masochistic, because that drops you back to the hell of resolving dependencies that made Linux a PITA to use before package managers. Virtually none of the package managers out there work without root.)

      So theoretically speaking... I can buy your argument. Practically speaking, I think it makes basically no difference whatsoever.

    11. Re:This IS already being done in Linux by EvanED · · Score: 1

      privileges are elevated for a single helper binary that (assuming it was written well) is a narrowly defined piece of code...

      And there's the rub. As the other person replying to you said, the situation isn't much different on Windows. You can still have well-written programs that behave the way you want.

      The problem with the Windows security model is much more with crappy programs due to the crappy security model in the past than it is with any real objective problems in today's model. ...you would have to first compromise the non-root application sufficient to execute arbitrary code, then find a second exploitable vulnerability in the much smaller root helper code

      I don't necessarily buy this either, maybe because I don't know enough about the OS X security model.

      Let me ask this: are the helper programs application-specific, or are they things like 'install' that are system-wide?

    12. Re:This IS already being done in Linux by Anonymous Coward · · Score: 0

      So, yes, it is exactly like PolicyKit. It shows all users that have the necessary privileges.

    13. Re:This IS already being done in Linux by MikeBabcock · · Score: 1

      However, what it does allow for hypothetically is "Mr. Manager, I need you to come authorize this change on my PC for me" in a domain setting.

      Oooh, *shudder* I just felt a ripple in the force.

      --
      - Michael T. Babcock (Yes, I blog)
    14. Re:This IS already being done in Linux by dgatwood · · Score: 1

      The vast majority of helper tools I've seen are application-specific. There's nothing stopping you from running something built-in through that mechanism, but it isn't commonly done, judging from the apps I've seen. That said, your mileage may vary. :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    15. Re:This IS already being done in Linux by dgatwood · · Score: 1

      Agreed for the most part. As you said, if one were to implement something in Linux, odds are they would implement it as part of the install process, not part of the app, and it would make the permissions changes needed (and do this once), not run the entire tool as root where the user could accidentally save a scanned image as /boot/vmlinuz or whatever.... :-)

      On the other hand, one could reasonably ask why xsane should need elevated privileges to capture and control a non-keyboard, non-disk USB device in the first place. I tend to prefer the Mac OS X policy on this one. In Mac OS X, an application can control a scanner from user space with ordinary user (not admin) privileges. That seems much more sensible to me as a general policy. Secure things that reasonably need to be secured for reasons of data privacy (disks and keyboards) or system protection (certain parts of the filesystem hierarchy such as /etc, /usr, and /var), let daemons request exclusive access for devices where it is needed (like printers), and leave things that don't really need a security policy unsecured.

      Unless, of course, you're talking about an ancient SCSI scanner, in which case I can understand the desire to keep those interfaces reserved for use by code running as root, if only because of the complexity of sorting out these rights relative to other SCSI devices like disks....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    16. Re:This IS already being done in Linux by kbielefe · · Score: 1

      one could reasonably ask why xsane should need elevated privileges

      It's not really elevated privileges as much as specific privileges. It's very simple to set up a user who can scan images, but not install software, for example. It just happens that elevating your privileges using sudo is the easiest way to grant all the specific privileges.

      At any rate, scanner use in Linux is mostly as you describe, with most normal users having non-admin access to them by default. I believe the exceptions are generally in the hardware that isn't identified automatically as a scanner, for whatever reason.

      You're looking at it from the point of view of "what's the point of limiting access to a scanner?" That misses the big picture. The Linux/Unix way is first to set safe defaults for all devices, and then to carve out narrow exceptions. When the security policy fails, we want it to fail safe. In other words, access isn't being denied because scanner access is necessarily a security hazard, but because access to devices in general is. It's a deliberate trade off of ease of installation for security.

      --
      This space intentionally left blank.
    17. Re:This IS already being done in Linux by MarkKB · · Score: 1

      Regarding launching a GUI window when a privilege violation occurs, this is precisely why Windows got the "Allow or Deny" reputation it got. You really don't want to authorize every little action.

      The implication is that it would only do this only when it detects you don't have sufficient privileges, and then prompt you for an admin user name and password who has these privs. This is a Good Thing - it bars from malicious software taking advantage of silent elevation for a period of time (on systems such as gksudo). It also makes running as limited users feasible on Windows (as opposed to Windows XP, where you could do almost nothing on a limited account.)

      Admittedly, what the patent describes is not the same as UAC (as described below), otherwise it'd be far more chatty than it is now. I did hear that in the early builds of Longhorn (post-2004 reset) that had UAC, it was far more chatty than it was when Vista was released, so it may have been the way it was originally

      (However, Windows does detect if a program is denied privileges without asking for UAC, then asks you if you want to configure it so it will launch as admin next time you launch it (after prompting, of course.)

      Also note that on Windows Vista and up in limited accounts, UAC shows you a list of admin accounts and prompts for their password when you click on one. I've noticed quite a few people are not aware of this, so I might as well throw it in.

      Further, when it comes to a typical desktop environment, a rights system should not be so complex that there are more than about two classes of users anyway---those who have the rights to modify system files and those who are limited to their own files.

      By this definition, every OS's rights management system is overly complex.

      A simple explanation is this: Windows uses a system where rights are defined both at the user, admin and system level. Some users may have rights over files that other users don't. The system described in the patent would scan for users that have privileges to operate on the file, and bring them up.

      Right now, I believe (I may be wrong) UAC merely brings up a list of users with greater privileges than the current user (i.e. admin users.)

      Also, I'm under the impression (based on the patent) that Windows is temporarily elevating the privileges of the application itself, which means that you now have a much larger chunk of code that must be checked for security holes, lest malicious individuals co-opt the application for nefarious purposes. Such a design also makes it very hard to adequately use code signing to ensure the authenticity of the code running with elevated privileges, thus allowing security holes in the app to readily be exploited and turned into the equivalent of root holes just by the user clicking "Allow".

      One might assume that the system described in the patent may be able to theoretically detect only the function in which the part requesting elevation is being run and elevate it only for the duration of it's run. That's not what UAC does either, although it does do something similar.

      UAC works in two main ways:

      a) the program is explicitly told to elevate. This happens at launch, and will elevate the entire program.
      b) the program uses COM to elevate and run a portion of code (usually in a DLL file). This can occur any time during the program's run time, and will only elevate the function being run.

      I'm not sure if Linux has an equivalent for the latter, so if it does, I wouldn't mind knowing. But the former is basically the equivalent of gksudo.

      (Arguably, non-elevated-ness shoould not be an excuse for not performing security audits of your code, since anyone can sudo/runas your software. Realistically, I recognise that one may not have the time if one is independent, but then I believe you should get someone to review or look over your work.)

      I'd like to add that in Windows Vista and above, there's no concept of a user like Linux's 'root'. Even when an app is elevated, there are restrictions on what it can do.

    18. Re:This IS already being done in Linux by MarkKB · · Score: 1

      One might assume that the system described in the patent may be able to theoretically detect only the function in which the part requesting elevation is being run and elevate it only for the duration of it's run. That's not what UAC does either, although it does do something similar.

      After I posted this, I thought of another method this could be done: the OS prompts the user, then turns around and does the task itself. This would prevent code vulnerabilities (apart from OS ones), although we arrive again at the point where the OS is far more chatty than what we have now.

      it may have been the way it was originally

      Designed. It may have been the way it was originally designed.

      Even if you use Preview you can still muck up.

  25. Prior art? by Dumnezeu · · Score: 1

    Didn't OS X do this already?

    --
    Yes, it's sarcasm. Deal with it!
    1. Re:Prior art? by Ash-Fox · · Score: 1

      I think you missed out how Linux, BSD in the links in the summary which existed before OS X were doing it.

      --
      Change is certain; progress is not obligatory.
    2. Re:Prior art? by Anonymous Coward · · Score: 0

      NeXTStep did this as well, way back at least 1993 (when I first started using them, I'm sure it was in there with version 1.0). It was a service in the services menu to run as a user or root.

  26. POLICY KIT! by gbutler69 · · Score: 0, Redundant

    http://hal.freedesktop.org/docs/PolicyKit/

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:POLICY KIT! by CannonballHead · · Score: 1

      That's something like the 8th time you've posted this.. :)

    2. Re:POLICY KIT! by Anonymous Coward · · Score: 0

      The claims say that it'll give you a list of users who can perform an action if you don't have the rights. It also says that it prioritizes the list of users based on factors such as frequency of use (presumably use of whatever you're trying to access) and association with the user.

      So I'm interpreting that as PolicyKit, except when you don't have permission, it has built-in hooks into the user management system to give you a list of people who are most likely to be able to help you. That actually sounds like a really good idea to me. Maybe not 17-year-monopoly good though.

    3. Re:POLICY KIT! by Anonymous Coward · · Score: 0

      And they only got one person modding them up...

    4. Re:POLICY KIT! by recoiledsnake · · Score: 1

      From a post above:

      This patent was filed more than four years ago, in April of 2005. This filing predates Red Hat's announcement of PolicyKit by about a year.

      --
      This space for rent.
    5. Re:POLICY KIT! by shutdown+-p+now · · Score: 1

      You really do not want to go there. The initial release of PolicyKit happened in 2007. The patent was filed in 2005. If PolicyKit does indeed match the claims of the patent, then all it means is that it violates the patent. It's definitely not prior art. Mentioning PolicyKit in this context just makes the matter worse, not better - you may just as well add a "so sue them" to every one of your posts.

    6. Re:POLICY KIT! by True+Grit · · Score: 1

      You really do not want to go there. ... If PolicyKit does indeed match the claims of the patent, then all it means is that it violates the patent.

      I don't know...

      I'm sure the PK devs obviously "don't want to go there", but if this turns out to be another example of multiple independent 'inventions' of the same idea (a not uncommon event in the annals of scientific discovery), then to me that would point to a problem with the patent system just as much as finding prior art for a 'bad' patent would.

      MO, of course, but what irks me about this system is that winner is not determined by any qualities of their implementation of the idea (what implementation?), or who had the idea first (no way to always determine that) but simply which one was rich enough to afford the patent attorney who got their application rammed through the USPTO first...

      Just sayin'

  27. I have prior work by rkuris · · Score: 5, Interesting

    I am the original author of "priv", which came before sudo, and I didn't see any mention of it. This utility was published in Unix World back in 1987, and basically did the same thing. Does this mean "priv" is exempt from this patent?

    --
    Get rid of everything Micro and Soft: Buy Viagra and/or Linux
    1. Re:I have prior work by Anonymous Coward · · Score: 1, Insightful

      That's not how patents work. It's no so much a question of which came first as it is of whether you can outspend Microsoft in court.

    2. Re:I have prior work by Theaetetus · · Score: 1

      Since the Examiner specifically looked at sudo and said "gee, this invention is patentably different", I'm gonna say yeah, you're not affected by this patent.

    3. Re:I have prior work by whatajoke · · Score: 1

      Does this mean "priv" is exempt from this patent?

      How much money can you spare for getting justice?

    4. Re:I have prior work by Anonymous Coward · · Score: 1, Informative

      Just because there exists prior work does not mean that it is taken into consideration by the Examiner of the current application. The applicant is required to disclose to the USPTO relevant prior work, in this case mention of sudo, priv, etc. Based on the search results found by the Examiner, and all disclosed information provided to the Examiner, the Examiner determines whether the current application is patentable over existing art. Of course, the Examiner may not be aware of relevant art, which leads to undeserving patents being awarded. However, an issued patent can be challenged by issuing a reexamination.

      Also, note that the title of the article and the rant at groklaw is a bit misleading. The invention does not cover prompting for an admin password, or the current user's password, in order to execute the desired task. Instead, the invention patented is limited by the claims to a GUI which displays a list of accounts which have the needed permissions to execute the desired task, and allowing the user to select one of the accounts and entering a password for the selected account.

    5. Re:I have prior work by earlymon · · Score: 1

      According to this, you're late:

      http://www.sudo.ws/sudo/history.html

      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    6. Re:I have prior work by earlymon · · Score: 1
      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    7. Re:I have prior work by bigbird · · Score: 1

      What, with a user id > 500,000? Where were you in the 1990's? :)

    8. Re:I have prior work by rkuris · · Score: 1

      Well, not on slashdot. I was hiding in an obscure part of the universe.

      --
      Get rid of everything Micro and Soft: Buy Viagra and/or Linux
  28. Waiting on this story... by Caviller · · Score: 1

    Company X patents government.

    Company X today has patented the business process know as 'government'. Governments are now required to give X dollars in license feeds per year to Company X in order to stay a sovereign country. Failure to pay fees will result in abandoning you right to sovereignty and becomming a subsideary of Company X. USPTO's response said that this will spur inovation and development of countries by helping them all work as one instead of all the different types there are today.


    Comments:

    Well....(Score: 5, Sad)
    Aparently America has already forgot to pay the fees....lol, i kid,i kid....maybe ;)

  29. Re:This is why software patents shouldn't be allow by nitehawk214 · · Score: 5, Funny

    I couldn't bothered reading all that shit.

    Oddly enough, that is exactly what the patent examiner said.

    --
    I'm a good cook. I'm a fantastic eater. - Steven Brust
  30. POLICY KIT! by gbutler69 · · Score: 2, Interesting
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  31. POLICY KIT! by gbutler69 · · Score: 1
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  32. Re:This is why software patents shouldn't be allow by jamstar7 · · Score: 4, Insightful

    Thanks for telling us that those claims are too complicated for you to read. Please make sure to put that on your resume, because if I was a potential employer looking to hire you for anything even remotely technical, I'd want to know that you give up whenever a discussion gets remotely above the complexity of "M$ sux0rz."

    Since when do programmers need to be patent lawyers? Patents are written in fluent legalese, not plain $HUMANLANGUAGEOFYOURCHOICE.

    --
    Understanding the scope of the problem is the first step on the path to true panic.
  33. POLICY KIT! by gbutler69 · · Score: 1
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  34. Actually the summary is basically correct by Anonymous Coward · · Score: 0

    If using an Administrator action on a Linux system you already get a GUI dialogue to see if you wish to elevate your privileges for that one action, that involves putting in a password but it is the same action.

    However the real reason the article is correct is because the patent is actually patenting the notion of elevating your privileges, it chooses to describe how that might work in terms of the UAC of Vista/Win7 but it does not limit itself to that implementation.

    So, in effect, Microsoft is patenting sudo

    1. Re:Actually the summary is basically correct by CannonballHead · · Score: 1

      If using an Administrator action on a Linux system you already get a GUI dialogue to see if you wish to elevate your privileges for that one action

      Before the action is attempted. So it's an application (a GUI) that is "wrapping" the administrator actions. It already knows what requires elevated permissions and lets you know beforehand. UAC catches attempts at actions requiring elevation by applications and asks you if you want to allow that/asks you to elevate your privileges ... basically "on the fly." The application does not have to know beforehand that it requires elevation.

      This is rather different from sudo...

    2. Re:Actually the summary is basically correct by spitzak · · Score: 3, Insightful

      It is not uncommon to pop up the sudo dialog in response to a permission-denied error from exec(). Therefore this patent does describe already-existing art. You and a dozen other posters seem to think the error detection has to be in the same process that actually does the access violation.

    3. Re:Actually the summary is basically correct by Rockoon · · Score: 1

      It is not uncommon to pop up the sudo dialog in response to a permission-denied error from exec().

      Exec only does it when the current user doesn't have rights to execute the program. It does not cover the case where the current user has the rights to execute the program, but neither the user nor the program has the rights to do what the program is trying to do.

      A good clear example would be a shell script which attempts to delete another users files. In Microsoft Land, the user is prompted for increased privileges prior to denying permission, while in Linux land its simply permission denied.

      --
      "His name was James Damore."
    4. Re:Actually the summary is basically correct by spitzak · · Score: 1

      Unless Microsoft are idiots, they are doing this using user-space libraries that respond to errors returned by system calls by instead invoking the privledge escalation.

      Therefore this is trivial to implement on Linux, such as with a wrapper libc. However I would agree that perhaps this has never been tried, though I would look into the implementations of various security packages on Linux and other systems, including 3rd party stuff for Windows.

    5. Re:Actually the summary is basically correct by Rockoon · · Score: 1

      I wouldn't say that its never been tried. Windows already does it with UAC.

      Its not exactly a clean solution, because there are some things that wont trigger UAC just because the session doesnt have the rights to do something.. (registry and folder virtualization, for instance)

      --
      "His name was James Damore."
  35. Policy Kit! by gbutler69 · · Score: 0, Redundant
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  36. Policy Kit by gbutler69 · · Score: 0, Redundant
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  37. Policy Kit! by gbutler69 · · Score: 0, Redundant
    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  38. Food by gmuslera · · Score: 0

    Operating systems for gourmets: Linux make coffee, and now Windows make sandwichs (not sure what makes OS/X, but it Cocoa flavored)

  39. Re:This is why software patents shouldn't be allow by 1729 · · Score: 5, Insightful

    Thanks for telling us that those claims are too complicated for you to read. Please make sure to put that on your resume, because if I was a potential employer looking to hire you for anything even remotely technical, I'd want to know that you give up whenever a discussion gets remotely above the complexity of "M$ sux0rz."

    That's not a technical description: it's legalese. I've done my share of technical writing, ranging from scientific journals articles to user and developer documentation, but I'd never be able to get away with producing such incomprehensible gibberish.

  40. Moot Point by kwiqsilver · · Score: 0

    This patent is a moot point anyway, because it falls under my patent for a system where a user authenticates his identity by means of a unique user identifier and a secret password, before the system allows him access.

  41. in microsoft's defense by Dan667 · · Score: 1

    the idea of sudo is probably completely new to them even after decades to think about it.

    1. Re:in microsoft's defense by Sulphur · · Score: 1

      the idea of sudo is probably completely new to them even after decades to think about it.

      Dough or psuedo?

      --

      Financial advice 60 % off
      Sig offtopic

  42. I know how we will get them! by Hurricane78 · · Score: 0

    we will trap them in their own greed:

    Just pitch the idea to the government, to put huge fines invalidating stupid patents like these. Like 10% of the business's sales volume. Then tell them, how to easily make money, by invalidating such a pointless patent.
    Now just let the greed work its way...

    With huge holes in the goverment budget, and them making more money this way, then the companies could ever bribe them with, this could actually work.

    Now all we need is someone hot who can meet for a dinner with some politicians.
    Let's all put some money in a anonymous account, and pay a escort girl to turn their heads, until they obey like dogs. ^^

    Damn, that could actually work! Hormones are always a safe attack vector. And since you can buy them for money...

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  43. Another pointless article on patents by harlows_monkeys · · Score: 1

    Pretty much any patent analysis by people who have not read the claims and specification is worthless. Slashdot should just ban all articles about patents, since said articles are uniformly worthless.

    1. Re:Another pointless article on patents by recoiledsnake · · Score: 1

      I liked the days of the nice legal analysis of the SCO time by GrokLaw. Now it has become a front for PJ's baseless and rambling anti-MS rants. In short, PJ has turned into a troll.

      --
      This space for rent.
  44. I'm sorry, what? by warrax_666 · · Score: 3, Insightful

    copyright doesn't protect against duplicating functionality

    You say that like it's a bad thing.

    (Independent innovation can be affected by the patent system. That in itself is absurd.)

    --
    HAND.
    1. Re:I'm sorry, what? by dkh2 · · Score: 1

      I can only imagine the legal battles between Newton and Liebnitz over what ultimately became the Calculus we use today.

      --
      My office has been taken over by iPod people.
  45. Get it dumbshit by Anonymous Coward · · Score: 0

    Actually, that's a *furore*.

  46. Re:This is why software patents shouldn't be allow by ShatteredArm · · Score: 1

    I, for one, never understood why programmers have such a hard time with legalese. Quality programmers should make sure their software is as computationally universal as possible, which is exactly the reason for having "legalese."

  47. Re:This is why software patents shouldn't be allow by Waffle+Iron · · Score: 1

    Thanks for telling us that those claims are too complicated for you to read.

    It's not just those claims. There are MILLIONS of software patent claims in existence. In theory, every developer needs to check every piece of code they write against all of those millions of claims. Otherwise they could be infringing on someone's patent. It's a completely unreasonable burden.

    This isn't the old days where if you invent a new cotton gin, you could just look under "cotton gin" in a card index to find out if you're infringing.

  48. Not sudo. by Jugalator · · Score: 1, Troll

    Read the first claim. It's far more specific than what sudo does. Sudo is just about elevating rights via a command, this is much more specific.

    --
    Beware: In C++, your friends can see your privates!
    1. Re:Not sudo. by shutdown+-p+now · · Score: 1

      It's interesting that the patent examiner was perfectly aware of su, sudo, gksu, kdesu, Ubuntu integration with gksu to call it as needed automatically, etc. Look at the "Other References" section of the patent:

      "GKSU: A gtk+ su front end Linux Man Page" retrived at http://www.penguin-soft.com/peguin/man/1/gksu.html

      Lawrence, "Using Sudo", Linus Tutorials, May 12, 2005, retrieved at http://web.archive.org/web/20050530041932/www.developertutorials.com/tutorials/linux/using-sudo-050511/page1.html

      Miller, "Sudo Manual", Jul. 11, 2004 retrived at http://web.archive.org/web/20040711020526/http://www.gratisoft.us/sudo/man/sudo.html

      Miller, "Sudoers Manual", Jul. 11, 2004, retrived at http://web.archive.org/web/20040711020555/www.gratisoft.us/sudo/man/sudoers.html

      Quick HOWTO: Ch09 : Linxus Users and Sudo, Dec. 23, 2005, retrived at http:web.archive.org/ web/20060203023004/http://www.linuxhomenetworking.com/wiki/index.php/

      "The KDE su Command", Nov. 20, 2004, retrived on http://www.linfo.org/kdesu.html

      "The Ubuntu Quick Guide. Chapter 3. Applications Menu: System Tools.", retrieved on http://people.ubuntu.com/.about.mako/docteam/quickguide/ch03s07.html

    2. Re:Not sudo. by True+Grit · · Score: 1

      I want to have whatever that earlier mod was smoking...

      Seriously guys, agree or disagree, this post is nowhere *near* to 'Troll' status.

  49. Pseudocode by failedlogic · · Score: 3, Interesting

    I think a better solution would be for the patent to be described using pseudocode or some variation thereof. Since this is afterall a software patent, the application should be written in a form that is legible to others in the field. It would also lead to easier settlement of a dispute since previous art could more easily be compared with pseudocode.

  50. ...and then there was the time... by Anonymous Coward · · Score: 0

    ... and then there was the time Micro$oft and Apple both stole the windows GUI concept from Xerox's Palo Alto Research Center (a la smalltalk) and then paid their lawyer$ million$ to fight about which of them (minus Xerox, of course) owned the "look and feel" of it?

  51. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    Until you find references that actually can be used to reject those claims, instead of just making some crap argument like "OMGZORS IT'S SUDO WITH A GUI", you can sit and spin, buddy.

  52. So? by Anonymous Coward · · Score: 0

    I just patented the BSoD! Take that!

  53. Mod parent up by Lonewolf666 · · Score: 1

    Individual patent claims may be stupid and a waste of time, but it is the huge numbers of patents that really makes the system fail.

    A way to fix that would be to drastically increase the required inventive step, so only extraordinary inventions would get patent protection at all. Those extraordinary inventions would be much less numerous and it would be possible again to do an exhaustive search if your code was already patented by someone else.
    But I don't think that will happen anytime soon. It would be easier to remove the patent system completely.

    --
    C - the footgun of programming languages
    1. Re:Mod parent up by icannotthinkofaname · · Score: 1

      But I don't think that will happen anytime soon. It would be easier to remove the patent system completely.

      I'm gonna take a guess that you're the kind of guy who, when his computer fills up with too many source code files, just uses `sudo rm -rf /` rather than picking through your disk and deleting only the files that you want to delete.

      --
      Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    2. Re:Mod parent up by Lonewolf666 · · Score: 1

      No, I just have my doubts if the higher standards would stick when the patent examiners are under pressure to process patents fast and management really wants to see more approved patents because those bring revenue.
      A decision by Congress to grant no more patents, period, would be far more clear cut and not so easy to water down.

      --
      C - the footgun of programming languages
  54. sudo precedes Linux by earlymon · · Score: 2

    "sudo" as in "run a single command as root and furthermore examine the commands before running them and restrict them to a set, and furthermore examine the user trying to run sudo to select the restricted set" was developed after Linux was popular.

    I seem to recall using it long before Linux appeared.

    http://www.gratisoft.us/sudo/history.html

    http://www.gratisoft.us/sudo/readme.html

    Unless there's some nuance in your quote that I'm missing.

    BTW - gratisoft.us appears to mirror sudo.ws

    --
    Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    1. Re:sudo precedes Linux by spitzak · · Score: 1

      You are right it appears it is a good deal older than Linux.

      I remember it came from BSD but for some reason never heard of it until after Linux existed.

    2. Re:sudo precedes Linux by earlymon · · Score: 1

      My use of it was always limited - I had to go look that up myself!

      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
  55. Re:This is why software patents shouldn't be allow by unix1 · · Score: 1

    I don't know that I'd use the test of patent language understanding to identify good technical job candidate, not for most jobs anyway, not yet anyway... unless every programmer will be required to be a patent lawyer too. ... a selectable help graphic wherein responsive to receiving selection of the selectable help graphic ... Nobody knows what it means, but it's there to make it confusing and sound like they "invented" something.

  56. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    That is how the US Patent system works. Anybody can patent any BS. Then, if you do not agree with the BS, challenge it in court and prove there is prior art etc. MS would not be able to enforce that BS so easy.

  57. In fairness to Microsoft ..... by Anonymous Coward · · Score: 0

    they did disclose sudo as art to the examiner during prosecution.

  58. Dear Newbs, su came before sudo by BitZtream · · Score: 5, Informative

    If you're going to claims something copies 'sudo' with 'Linux' please realize that sudo copies su which was around long before Linux.

    sudo has more features than su, yes. Everything that 'copies' sudo has more features as well.

    Although the patent in this case does not copy sudo, or gksudo or OSX. The patent covers something that detects an authorization (NOT AUTHENTICATION) failure and gives an opportunity to elevate privileges and continue rather than denying the request.

    su, sudo, gksudo and the OS X applet all require knowledge in advance that elevated privileges are required.

    Do I think the difference is worth patenting? No, its the next logical step. However, if you're going to rant and rave about what Microsoft is patenting, at least realize they aren't patenting a clone of something you've been using for years.

    You only make the rest of the OSS world look stupid to the powers that be when you rant and rave and you are completely ignorant of whats being done. We lose credibility and get written off as raving lunes when you respond like this. So please, shut the hell up.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  59. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    If that passes as something technical where you work, you can keep that job... I'll keep working on actual technology instead of fucking with gibberish like that. I know it may limit my work options but so far I've been happy.

  60. So why does MS deserve a monopoly on this by bugs2squash · · Score: 1

    Sure, it's a neat idea and all, but why should I agree not to implement the same idea in my own way. If I can figure out how to do something in a different way (for example with different code) then I don't see why I should be prevented from doing so. The same goes for the car starter analogy. I don't see why the public benefits from being told how to do these things. If someone had put an electric starter motor on a car and kept the details secret about how he had done it, someone later would have figured it all out without the help of the patent. I just don't see what valuable rights the patent holder is giving up in exchange for the monopoly. The obviousness criteria should be applied to the method of doing something, not to the thing being done IMHO.

    --
    Nullius in verba
  61. Another reason (on top of the many) to not use M$ by __aakdpj1217 · · Score: 0

    Yep another one of those reasons to move to Linux.

  62. Dennis Ritchie already patented this by argent · · Score: 3, Informative

    Dennis Ritchie patented the setuid bit in what was probably the first software patent ever, and released the patent to the public domain. I think that counts as a slam dunk prior art, no?

    1. Re:Dennis Ritchie already patented this by Wowlapalooza · · Score: 1

      Dennis Ritchie patented the setuid bit in what was probably the first software patent ever, and released the patent to the public domain. I think that counts as a slam dunk prior art, no?

      Not even close. setuid/setgid automatically raises the user's privilege to a specific UID/GID when it is invoked. The patent covers presenting a GUI to the user when they try to execute something, and have insufficient privilege, having them pick a user/account with sufficient privileges to execute the command, authenticating, and then executing the command with the temporarily-elevated privileges. It's only roughly similar to setuid/setgid in the last part of the process -- running a command with temporarily-elevated privileges.

      "sudo" is the closest analogy, but still not really the same thing, since it doesn't pop up with a GUI every time you try to run something with insufficient privileges...

  63. Substantial difference by Anonymous Coward · · Score: 0

    As other posters have mentioned, this is different because it's kind of an automated watchdog system that lies in wait for someone to run something that needs elevated permissions--and then it prompts them to give those permissions. Sudo doesn't watch for a place where it might be needed. You have to call it specifically. If you try and run something that you're not allowed to, it says "you can't run this", and you say "darn--okay, sudo program". This patent is for software where when you run any program that needs high permissions, it says "you can't run this, unless you give me an admin password, so please give me an admin password".

  64. Just like PolicyKit by Jeremy+Visser · · Score: 5, Informative

    That's true. It's still a crappy patent application though, since it basically covers showing a password dialog box with eligible user accounts (along with some details about their associated privileges) when an operation requires elevated privileges.

    Indeed. In fact, this patent reminds me more of PolicyKit (which is GUI-based) than sudo. See screenshot, which almost exactly matches how I visualised the patent after reading the initial claims.

    1. Re:Just like PolicyKit by Dachannien · · Score: 1

      Actually, that looks a whole lot like what was claimed. Unfortunately, the changelog for PolicyKit indicates that the initial version was done in March 2006, which is too late to be prior art.

    2. Re:Just like PolicyKit by recoiledsnake · · Score: 1

      From a comment above:

      This patent was filed more than four years ago, in April of 2005. This filing predates Red Hat's announcement of PolicyKit by about a year.

      --
      This space for rent.
    3. Re:Just like PolicyKit by Anonymous Coward · · Score: 0

      MacOS X has a similar feature too. I'm not sure when it was introduced, but back in november 2003 someone pointed out it could be spoofed.

  65. found in all Linux systems by nurb432 · · Score: 1

    And a bunch of others. Just an FYI the world does not circle around the LInux/Microsoft rivalry. Some of us are in neither camp and just want to get our jobs done, without all the bickering.

    --
    ---- Booth was a patriot ----
  66. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  67. Re:This is why software patents shouldn't be allow by compro01 · · Score: 5, Insightful

    Law is the programming language for the system of society. The problem is, rather than doing exactly what you told it to do, regardless of whether that's what you wanted it to do, the system makes every possible effort to interpret the code in such a way so that it doesn't have to do what you instructed it to do.

    --
    upon the advice of my lawyer, i have no sig at this time
  68. Patent office needs to be revoked of sudo access by Darkk · · Score: 3, Funny

    The patent office needs to be revoked of sudo access.

  69. Quit Complaining and Start doing something. by Anonymous Coward · · Score: 0

    You have no room to complain for the following reasons:

    1.) The GNU/*NIX community knows MS is a patent troll.
    2.) You know MS is out to get you.
    3.) You have had tech out since 1979 that is open sourced, but not patented or
    copyrighted.

    Your argument sounds something like this:

    1.) I live in a neighborhood filled with thieves.
    2.) I saw some thieves casing my house.
    3.) Hey, I will leave my front door open while I'm out, it will be great.
    4.) Oh no, I've been robbed! How could this happen to me!

    Here's the obvious question: Why hasn't someone in the GNU/Linux or Unix world
    patented their stuff? Patent it, give it to a community trust of some sort, and
    protect civilization from Microsoft. It doesn't take a genius.

  70. Groklaw is wrong by Anonymous Coward · · Score: 2, Interesting

    The claims presented on their web page do not conflict with sudo.

    sudo works in a very different way: sudo is about the user saying "i need to be a different user so I can run command Y"

    This feature is about the operating system saying "user X, in order to do Y, you need more privilege."

    The two concepts are quite different.

    Maybe Groklaw folks should use Vista/Windows7, as well as Unix, and try to understand the difference(s) between the roles of the two.

    1. Re:Groklaw is wrong by Wowlapalooza · · Score: 1

      The claims presented on their web page do not conflict with sudo.

      sudo works in a very different way: sudo is about the user saying "i need to be a different user so I can run command Y"

      This feature is about the operating system saying "user X, in order to do Y, you need more privilege."

      No, read the claims. The patent covers actually authenticating the user and then elevating their privilege to invoke the command. It's a superset of sudo, that kicks in automatically on an "insufficient privilege" condition and has a GUI frontend. Groklaw got it essentially correct.

  71. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 1, Interesting

    I will say it again. Let companies keep their trade secrets. I would rather see companies come up with something and pay their engineers money to improve it over the competition than have to throw money at the USPTO and Lawyers. Hell, I would rather see the Marketing department get some of that money to advertise why product X is better than Y than to hold a monopoly and sit around collecting money. Look at the vast amounts of money that get thrown around on patent litigation whether a patent has obviously good standing or clearly has prior art. If you want to contest another's patent or defend your own, you are going to have to cough up a lot of money, money that could be going into R&D making your product even better. Businesses should be constantly innovating with the fire of innovation on their asses. Everyone wins in this scenario because the person with the best product makes the most money and the losers can try again next time to come up with something that is either cheaper, faster, or of higher quality (pick 2). The consumers would also win because they would have a constant slew of people actually putting on a song and dance for your money rather than the business-as-usual methods of expecting consumers to pay tribute to you because you're the only game in town.

    Imagine if the Internet had come out in the time of software patents. The Internet in its current form started in bits and pieces. Imagine how long it would have been to have an internet where half the technologies we have didn't exist and the other half cost a prohibitive amount of money. Microsoft, Apple, Oracle/Sun, Adobe, and a lot of other tech giants owe a lot of where they are now on not having a nuisance patent system.

  72. I don't get it by rinoid · · Score: 1

    From the OP description:
    "the functionality of 'sudo' which is found in all Linux systems"

    Why is it you Linux boys always think everything was invented on Linux?
    Unix

    From http://en.wikipedia.org/wiki/Sudo

    The sudo ("su do", pronounced /sudu/, though /sudo/ is also common, as is /sjudu/) command is a program for some Unix and Unix-like computer operating systems that allows users to run programs with the security privileges of another user (normally the superuser, a.k.a. root). Windows has a command runas which has similar functionality.

  73. Prior Art by Anonymous Coward · · Score: 0

    This has been on unices not quite forever, but you can see it from there. Prior Art baby. If they try to press this at all, it will flop like a house of cards. Is this '48 patents'? If the others are like this one, they have nothing, but some strange desire to fund the US patent office by getting patents that obviously cannot hold water.

  74. sudo sux by Anonymous Coward · · Score: 0

    heh heh heh

    command not found? your laggin.

  75. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  76. Re:Patent office needs to be revoked of sudo acces by FunPika · · Score: 2, Funny

    No, we just need to disable Microsoft's access to run /usr/sbin/grantpatent as root in /etc/sudoers. ;)

    --
    After years of not using a signature, I am going to make one to say the following: Fuck Beta
  77. Multiple issues getting mixed up here by Anonymous Coward · · Score: 4, Insightful

    There are multiple issues getting mixed up in the Groklaw article and the discussion on Slashdot.

    A patent application has three hoops to jump through to be patentable:

    35 U.S.C. 101 - the claims must be patentable subject matter. The question of "is software patentable" is what the Supreme Court is deciding in In Re Bilski. This is the largest issue most of the Slashdot community seems concerned about, and it's obviously a big issue right now. These claims, as written, may be patentable subject matter under current 101 criteria. This is why there were written with all the "computer readable media" language.

    35 U.S.C. 102 - the claims must be "novel" subject matter. This is what people object to when they yell "BUT I DID THIS BACK IN 1990!"

    35 U.S.C. 103 - the claims must be non-obvious subject matter. This is what most people appear to be objecting to in the present discussion....if sudo existed before this patent, then laying down Microsoft's GUI idea on top may be obvious. (This is NOT a Section 102 issue). This is the part where the patent office (and examiner) screwed up. Even if the examiner couldn't find a reference that taught exactly what Microsoft claimed, he/she should have at least rejected the now-issued claims as obvious. Maybe he did, but half-assed the rejection...who knows.

    The Groklaw article points out an "obvious" patent and yells that is shouldn't be patentable subject matter. Those are two separate issues. Yes, it's probably obvious. Depending on your view of software patents, it should or should not be patentable subject matter. That fact that it's an "obvious" idea will NOT in any way be affected by the Supreme Court's decision in Bilski (that case is about patentable subject matter under Section 101).

  78. M$ and Patents! Set NERD RAGE TO WARP 9!!! by Anonymous Coward · · Score: 0

    Good job disagreeing with the slashdot groupthink, now you are a troll. The proper response to anything rgarding patents and M$ is outrage. Nothing else will be accepted.

  79. And? by Anonymous Coward · · Score: 1, Insightful

    If you wrap your program with a shell script roughly as

    #program
    program
    if $exit_status = DIDNT_HAVE_PERMISSION do gksudo program; done

    It violates the patent?

    That's stupidity on so many levels

  80. BS by Anonymous Coward · · Score: 0

    More and more bullshit keeps on coming from msft. I wonder where is the limit.

    They should get some recognition, maybe an award or something

  81. Adding Fuel to the Fire... by Anonymous Coward · · Score: 0

    Surprised haven't seen this mentioned yet ... look at the file date (2005). This likely was submitted during Vista's development:
    "Cancel or Allow"?

  82. Not really needed anyway. by TravisHein · · Score: 1

    But doesn't the numerous back doors and severe drive by invokable kernel security flaws already allow arbitrary privileged execution.?

  83. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    It would be fine if legalese actually did that, but it doesn't. Mathematics is clear and concise. Legalese appears to have been designed primarily to be incomprehensible by normal people without extensive effort, thereby increasing the demand for people who are fluent in it (ie lawyers).

  84. All Linux Systems? by Anonymous Coward · · Score: 0

    sudo isn't installed by default in *most* Linux systems. I believe the program you're looking for is su.

  85. Other References for Dummies by Anonymous Coward · · Score: 0

    "Andy Rathbone, "Windows XP for Dummies", 2001, Wiley Publishing Inc., pp. 62-64, 66, 106-107, 128 and 314. cited by examiner ." ... Really?

  86. Re:This is why software patents shouldn't be allow by Dachannien · · Score: 1

    Actually, the examiner rejected the application three times and forced the applicant to amend the hell out of the claims before allowing it.

  87. oh, lol by smash · · Score: 1

    and with all the "M$ is evil!" fanbois here continually claiming that UAC is nothing like sudo - they've even got some (albeit) flimsy support for their claim.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  88. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    That's why all competent lawyers are excellent programmers.

  89. Re:This is why software patents shouldn't be allow by gzipped_tar · · Score: 1

    Nah, real programmer use his own secret LISP code to transform legalese into Klingon automatically.

    --
    Colorless green Cthulhu waits dreaming furiously.
  90. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 5, Informative

    As an ex-programmer/technical writer who is now a lawyer who's also worked at the USPTO as an examiner (during law school), I feel I must weigh in on the language issue. Patents and patent applications are neither technical documents nor legalese. They are a unique and bizarre hybrid of the two which, quite frankly, I think no one understands. The claims, specifically, since the specification is sometimes actually intelligible in a meaningful way. Everyone (examiners, phositas, judges, lawyers) has trouble dealing with claims and their meanings. The fact that we require pre-litigation court hearings to determine what a claim means (Markman hearings) AFTER the USPTO has already reviewed and approved the claims, which requires determining what the claim means, should be a sufficiently strong indicator that the current style of writing for patents is uncommunicative and ineffective.

    To speak more directly to software patents, the USPTO doesn't recognize such a thing literally. Moreover, in general the PTO doesn't look upon the software field as a true technical/engineering discipline, and so looks down upon software/programming expertise in it's examiners. If it appears that the PTO doesn't know a thing about how software works or what is out there as prior art, it is because generally it doesn't know a thing. The field of endeavor isn't recognized or utilized, and examiners often interpret claims to avoid dealing with software (as they don't have the background knowledge to know how to begin researching the prior art).

    Software may or may not be patentable ideologically, but as long as the field is given short shrift and basically sneered at by the PTO, no patent process will make sense for the majority of software/business method patents.

    AC for obvious reasons.

  91. They didn't patent sudo. by Eric+Smith · · Score: 3, Informative
    Not a single claim of this patent would be applicable to sudo. The independent claims 1, 2, and 9 don't apply to sudo, because they describe significant behavior that is not part of sudo. By extension, none of the dependent claims can apply to sudo either.

    You can still argue over whether it meets the obviousness criterion, but trying to spin this a "Microsoft patents sudo" is deliberately spreading FUD.

  92. Re:This is why software patents shouldn't be allow by geekmux · · Score: 1

    I couldn't bothered reading all that shit.

    Oddly enough, that is exactly what the patent examiner said.

    True, but it was even worse than you think. The patent examiner, barely 7 pages deep into Microsofts EULA for patent reading, said: "Oh, fuck this."

  93. New commercial by caywen · · Score: 1

    I'm Steve Ballmer, and sudo was MY idea.

  94. Re:This is why software patents shouldn't be allow by icannotthinkofaname · · Score: 1

    I, for one, never understood why programmers have such a hard time with legalese.

    We learn many languages. Legalese is not one of them.

    Could you read C code before you studied C? Did you know Java before you knew Java?

    If legalese documents would include some sort of comment or remark before each section summarizing what the section's about, I think we could get people to understand the document before they decide it's tl;dr.

    . . .

    brb, patenting commenting. ;P

    --
    Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
  95. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 1

    First thing we do, let's kill all the lawyers.
    --William Shakespeare

  96. Anonymous Coward by Anonymous Coward · · Score: 0

    Microsoft must be suffering from Cryptomnesia.

  97. software patents by falconwolf · · Score: 1

    I don't condemn all software patents. Just because it's software doesn't mean that it can't be brilliant and stunningly innovative.

    I do. Software is already protected, it's called copyright. Software does not need to be patented.

    Falcon

  98. Prior Art by NickGnome · · Score: 1
    Because he thought of and did it first.

    Just so, Bob Coggeshall and Cliff Spencer (with a couple brownie points to SUNY Buffalo) apparently have the prior art on sudo itself...

    while slapping a happy face on things (GUI) should go to Xerox PARC.

    The only difference between us and the "cave men" is knowledge. They had all of the same stuff. They just didn't realize what could be done with it.

  99. Re:This is why software patents shouldn't be allow by garyebickford · · Score: 1

    Now THAT would make an interesting successor to Brainf*ck.

    --
    It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
  100. Re:This is why software patents shouldn't be allow by syousef · · Score: 2, Insightful

    Law is the programming language for the system of society.

    Well it's syntax is obscure and imprecise, it's practitioners are mostly B-Ark material, and people write horrible code with it.

    --
    These posts express my own personal views, not those of my employer
  101. Re:This is why software patents shouldn't be allow by submain · · Score: 4, Funny

    the system makes every possible effort to interpret the code in such a way so that it doesn't have to do what you instructed it to do.

    So law is interpreted. Wonder why our justice system is so slow...

  102. Really something needs to be done about the system by falconwolf · · Score: 2, Insightful

    You do something by barring software patents, Once that's done listen to the economists who have studied patents and encourage innovation by ending patents.

    Falcon

  103. Re:This is why software patents shouldn't be allow by sjames · · Score: 1

    I can't speak for all programmers, but THIS programmer has several problems with it.

    Firstly, it is the world's most ill-defined "programming language". Show 1000 competent programmers a given body of source code and you will recieve the same description of what it does 1000 times. Show 1000 lawyers the same contract or law and you will receive at least 100 different descriptions of what it means, none guaranteed to stand up in court.

    Next, unlike legalese, programming languages absolutely must pass "the compiler test". If it won't compile, it cannot ship. As low as that standard may be, it's higher than the bar for a boilerplate contract. I've read legalese that doesn't even parse being used on "standard contracts" for utilities, apartment rentals, etc.

    Legalese combines the wordiness of COBOL with the spaghetti nature of the original BASIC, line numbers and all.

    The users of legalese routinely and shamelessly apply patches to patches of patches until nobody is actually sure how it might read if they were all applied in order or even what order they should be applied in. They don't even try, they just throw a few more patches in and see what sticks. It's no wonder that all a legal "code review" can ever manage is an opinion or five.

    Computer code must at least tip it's hat to usability. Legalese doesn't even pretend to try to be comprehensible to those it applies to.

    Computers and their programs have the good sense to give up and core dump when all hope of correct execution is lost. If computers operated the way the legal system does, a segfault would cause the offending pointer to be loaded with the nearest technically legal address (correct or not) and execution resumes.

    Programmers have enough sense to recognize that all programs have bugs. We also recognize that if a computer program spews a bunch of nonsense, we should ignore the result and fix the code until it makes sense again.

    Finally, all you have to do to avoid ever having to deal with source code is don't be a computer programmer. There are many fine jobs available where you need never see it nor pay someone else to help you out with it. To avoid ever dealing with legalese or having to pay someone to wrangle it for you, you must go live in a cave cut off from all human contact.

    In fact, even that may not be enough. Someone may find you and wave a bunch of legalese at you claiming it says you have to move. If you attempt to ignore it, eventually law enforcement will show up and if you press the point drag you into court LITERALLY at gunpoint where you will be forced to deal with it or be imprisoned until you capitulate.

  104. alternatives to patents by falconwolf · · Score: 3, Insightful

    before we scrap software patents, we need to provide developers with an alternative.

    There are alternatives such as trade secrets and first mover advantage. Actually by scrapping patents you may encourage innovation, if a business wants to it's market share then it will innovate. As it is patents may discourage innovation. Tell me, why should I spend millions of dollars to invent something if I can be slapped with a lawsuit claiming infringement? Because patents are issued companies have to horde them just to use for self protection. With a thousand patents if another business comes along and threatens a patent infringement lawsuit then one of those patents may save the business because of mutually assured destruction. This forces businesses to spend more on defense than on innovation.

    Falcon

  105. They didn't patent sudo. Read the patent. by falconwolf · · Score: 1

    They're trying to patent what sudo does with a GUI interface.

    Systems and/or methods are described that enable a user to elevate his or her rights. My 2 plus year old Mac did that when I got it. "Sudo was first conceived and implemented by Bob Coggeshall and Cliff Spencer around 1980 at the Department of Computer Science at SUNY/Buffalo."

    Falcon

    1. Re:They didn't patent sudo. Read the patent. by Rockoon · · Score: 1

      You didnt read the patent, did you?

      --
      "His name was James Damore."
  106. Re:This is why software patents shouldn't be allow by Rubinstien · · Score: 1

    Somebody should mod this AC up. Interesting, at least.

  107. Re:This is why software patents shouldn't be allow by stephanruby · · Score: 1

    Thanks for telling us that those claims are too complicated for you to read.

    He tried. You obviously didn't.

  108. Sudo patent? by childoftv · · Score: 1

    $ patent sudo
    -bash: patent: command not found
    $ sudo patent sudo
    password:
    $

  109. Microsoft security at its finest by Anonymous Coward · · Score: 0

    So I want to escalate my privilege but don't want the hassle of attacking the professional administrators' accounts?

    No problem - Just try to do what I shouldn't and see what names the system gives me...

    Brilliant! Brenda from accounts has the elevated privilege because she had her boss harass the admins until they gave in.

    I'll just wander over to her desk and check her monitor and under her keyboard for post-its with her password

    And Microsoft are so proud of this that they patented it?

  110. gksu and sudo... by BrokenHalo · · Score: 1

    Although sudo is available on all Linuxes, it was derived ultimately from (I think) a BSD creation dating from about 1980. Oh, hang on, Wikipedia says it was written by "Bob Coggeshall and Cliff Spencer ... at the Department of Computer Science at SUNY/Buffalo. The current version is under active development and is maintained by OpenBSD developer Todd C Miller".

    I'm sure Apple must use some functional equivalent to gksu in OS X for privilege escalation when required. I know sudo is available from the command line in OS X by default if one has "enabled" the root user, which I guess just about every command-line cowboy must have.

    So if anybody's got any money to fight the patent in court, I guess Apple might be a good candidate if the BSD developers can't.

    1. Re:gksu and sudo... by geminidomino · · Score: 1

      I'm pretty sure that's why Microsoft will leave Apple and Canonical alone and go for somebody smaller first, then start screwing with the big guys once they've got a few decisions in their favor under their belts.

    2. Re:gksu and sudo... by BrokenHalo · · Score: 1

      Microsoft will... go for somebody smaller first, then start screwing with the big guys once they've got a few decisions in their favor under their belts

      Thing is, there's so much prior art around from the days when Microsoft was playing around with piddly little toy single-user operating systems, Microsoft doesn't have a prayer of defending a patent written by some overpaid half-asleep attorney.

    3. Re:gksu and sudo... by lamapper · · Score: 1

      You and I both know that they do not intend to go to court, ever. They only hope to intimidate and get their way through FEAR, look at tomtom and many others.

      I hope they pick on a little guy who can get his legal fees handled by others so they can once again be put in their place. I too agree there is so much prior art that they do not have a leg to stand on. But stand and intimidate they try...cowards.

      I will check the date they released this and if more recent, I will set my 7 year clock from that date. (For seven years from the date of the reset, I will NOT purchase anything Microsoft. If after 7 years of good behavior their actions dictate they are worthy of being considered again for my hard earned $$$$, I will once again consider Microsoft products...just not for seven years from the date of the infraction.)

      If enough people follow suit, perhaps it will be too costly for a business to choose to mess them over, perhaps.

      --
      Is your Internet Throttled? Install DD-Wrt, OpenWRT or Tomato to learn the truth! Google: 1Gbps/1Gbps: 5 Communities
  111. sudo does that? by Lord+Bitman · · Score: 1

    And here I thought sudo did the opposite of that.

    Sudo let's you say "I know I need more privileges to run this program. Here is the user I would like to run it as instead."

    this patent let's you say "Run this program" and have the OS respond "That won't work, you probably want to run as Steve or Administrator. Shall I run it as one of them?"

    This is very, very different, no matter how little you notice since behind-the-scenes, a program is calling "sudo" when it guesses it needs to. This is another thing, like one-click-shopping, which was probably "obvious" to everybody, but discarded as poor UI ("I'd rather the user need to explicitly ask for privileges, to prevent mistakes.")

    But this is not what sudo does.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  112. anyone know what happens by ILongForDarkness · · Score: 1

    if someone patents an invention but then poorly implements. Say MS gets a patent for a "completely secure system" but it ends up being found that their is a bug in the code. Can people then reverse engineer/distribute something that implements the same thing? After all the product doesn't do what the patent claims so IMHO it isn't covered by the patent.

  113. We keep hearing this meme by Anonymous Coward · · Score: 0

    We keep hearing this meme and it's as wrong now as it's ever been.

    MS trolled 238 patents against Linux.

    No court case.

    Just FUD.

    Still trolling patents.

  114. Re:This is why software patents shouldn't be allow by PinkyDead · · Score: 1

    I know this is petty - but what the heck.

    CajunArson, what hope is there for me reading 20 odd points of a complicated patent application, when you can't even read 9 characters of a user name?

    --
    Genesis 1:32 And God typed :wq!
  115. su isn't sudo by Anonymous Coward · · Score: 0

    su isn't sudo, su makes your effective userid different until you change it again or log out.

    sudo makes your effective userid different for the actions of one exec().

  116. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    Law is the programming language for the system of society.

    Thou shalt not kill
    Thou shalt honor thy mother and father
    Thou shalt not steal

    etc, etc... somewhere along the line, this got converted into "Whereasmuch as the first party causes the cessation of breathing functionality in the case of the second party, said action is expressly forbidden..." then rattles on for six pages...

  117. sudo is safe from MS by Anonymous Coward · · Score: 0

    You should read manuals and you will find out, that sudo is the derivative of su, and su is not 'super user', but 'switch user', so that it allows you to act or perform actions as any other user in the system, if you know the password. Only when not specifying -u option it defaults to 'root' user.
    Microsoft's patent is to elevaiting privilegies, that is only a part of sudo or su.

    --
    disik
    denis1482@yandex.ru

  118. sudo -u by catman · · Score: 1
    From man sudo:

    sudo allows a permitted user to execute a command as the superuser or another user, as specified in the sudoers file. I have never used UAC which seems to be what the patent is about, but it seems to me that the process described lowers the security of the system. As usual, Microsoft puts ease of use ahead of security.

    But to elevate his or her rights to perform a task, the user will often need to find or remember an administrator account name. This may be disruptive; a user may need to call someone to figure out the name, find some scrap of paper somewhere on which the user wrote it down some time ago, and the like.

  119. I created Sudo for Windows in 2005 by akutz · · Score: 1

    I created Sudo for Windows (sudowin) in 2005. It is a free, open source project available at http://sudowin.sf.net/.

    --
    -- -a
    1. Re:I created Sudo for Windows in 2005 by glenmark · · Score: 1

      I created Sudo for Windows (sudowin) in 2005. It is a free, open source project available at http://sudowin.sf.net/.

      Ya beat to mentioning it, Andrew... *grin*

      --
      *** Quantum Mechanics: The Dreams of Which Stuff is Made ***
    2. Re:I created Sudo for Windows in 2005 by akutz · · Score: 1

      I even wrote a security practical for SANS on sudowin (http://bit.ly/4b3Ohb) and how I achieved the program on Windows. Microsoft's filed patent directly apes how I created sudo for Windows.

      --
      -- -a
  120. Prior art + obvious and trivial = WTF? by Anonymous Coward · · Score: 0

    1. One or more computer-readable media having computer-readable instructions therein that, when executed by a computing device, cause the computing device to present a user interface

    This has prior art for some time now, the rest is obvious and trivial.

    End of Discussion.

  121. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  122. Didn't They Already Patent This? by SenFo · · Score: 1

    Not to say that this is a duplicate story, but am I the only one that remembers this Slashdot post from years ago? It's obviously a new patent, but is it not essentially the same patent?

  123. Patent would not cover sudo by millert · · Score: 1

    This doesn't sound like it would cover sudo to me, or even a GUI-wrapper for sudo. While I am not a patent attorney, I have been hacking on sudo for the past 15+ years.

    My reading of the patent indicates that it is geared towards GUI-based environments where the user may need to perform some action (such as setting the clock in a control panel) that requires increased privileges. The actual "invention" appears to be that the user is able to perform an action as a different user without having to type in the name of that other user when authenticating. One example given in that patent is the ability to click on a name in a list of privileged users as opposed to having to type in a user name.

    Sudo simply doesn't work this way. When a command is run via sudo the user is actively running the command as a different user. What is described in the patent is a mechanism whereby an application or the operating system detects that an action needs to be run with increased privileges and automatically prompts the user with a list of potential users that have the appropriate privilege level to perform the task.

  124. Re:This is why software patents shouldn't be allow by ShatteredArm · · Score: 1

    None of those are computationally universal. Is euthanasia considered killing? Is self-defense exempt? What if your mother and father are trying to kill you? What is the penalty for stealing? It needs to rattle on for six pages in order to cover all the bases.

  125. Re:This is why software patents shouldn't be allow by MikeBabcock · · Score: 1

    And as the GP said, that's why we have lawyers.

    Feel free to essentially study the law yourself and become your own un-barred lawyer, but thats an investment in time and energy I'd rather put into other things and pay a lawyer for those bits of advice when I need them.

    There are chronic do-it-yourselfers out there, and more power to you, but that doesn't make changing your own oil better than paying a mechanic (or lube tech) for the job instead either.

    --
    - Michael T. Babcock (Yes, I blog)
  126. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    I thought it was Human Action. Law is nothing more than the exit 1 function with questionable error handling.

  127. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    the system makes every possible effort to interpret the code in such a way so that it doesn't have to do what you instructed it to do.

    So law is interpreted. Wonder why our justice system is so slow...

    The Garbage Collector only runs when there's a revolution.

  128. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    Should I quote you or someone else when I use this paragraph?

  129. You didnt read the patent, did you? by falconwolf · · Score: 1

    I did read the patent application. The only thing different I see is that what MS did was add a list of users who have the required permissions. Sudo doesn't do that but I wouldn't be surprised if there were utilities for OS X and *unix that does the same thing. Now I'm no expert in reading the legaleses of patent applications and I may of missed something.

    As it is I don't think it's enough of a novelty to qualify for a patent, if I believed in software patents but I don't.

    Falcon

    1. Re:You didnt read the patent, did you? by Rockoon · · Score: 1

      You didn't read the patent application, did you?

      sudo does not trap access violations and trigger an escalation prompt. The linux kernel doesnt do this either. Hell, I dont know of a single distro that has a version of this either.

      There is an operating system which does something similar to the patent, and thats Windows (both Vista and 7) .. the only difference between that patent and the existing UAC is the inclusion of a list of users with rights.

      This has nothing to do with sudo-like behavior, because sudo simply doesnt catch access violations and act on them.. it never did, and it never will. sudo must be invoked prior to launching the application, while UAC (and everything detailed in this patent) has no such requirement.

      --
      "His name was James Damore."
    2. Re:You didnt read the patent, did you? by falconwolf · · Score: 1

      Can you read?

      Falcon

  130. Close but no sudo by Arimus · · Score: 1

    sudo = Program to run when YOU know you need more privileges.
    MS thingy = Program that runs when it decides you need more privileges.

    MS thingy = receipe for dumb users to give permission when they shouldn't.

    sudo = way to stop dumb users (just don't add them to the sudoers file).

    --
    --- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
  131. In Ubuntu, whenever I try to mount a drive by falconwolf · · Score: 1

    but don't have the necessary privilege, I am presented with a list of users who do have such privilege and I am prompted pick a particular user and to provide that user's password.

    Thanks, I thought there might be a utility that does that. This is better. And worse. I want to install Ubuntu on my Mac and I don't want to need to set privileges for each user to mount drives. Right now I have 3 user accounts on my Mac, only one is an admin account and the only reason that account is used to update the system and for installations. I also have external hard disk drives I use as backups, currently I keep a running backup by copying saved files to an external drive. I want to set up rsync for that though, I also clone my drives.

    Falcon

  132. Old News by Anonymous Coward · · Score: 0

    This sounds awfully familiar. Oh yeah! They already patented this back in 2004.

  133. Re:This is why software patents shouldn't be allow by OldSoldier · · Score: 1

    Problem is most lawyers don't write comments in their "Programs".

  134. Re:This is why software patents shouldn't be allow by jwhitener · · Score: 1

    "the system makes every possible effort to interpret the code in such a way so that it doesn't have to do what you instructed it to do"

    Na, it just hasn't been tested in every possible environment. It probably worked very well in the limited scope of testing that the original programmer did. 5 years from the creation date, society is using "society environment 2.1" instead of 2.0, and the code has unexpected errors in the new societal operating system.

  135. Re:This is why software patents shouldn't be allow by Anonymous Coward · · Score: 0

    Your post is long and informative. You appear to be saying the USPTO is clueless. Personally, I think they know exactly what they are doing every time they award an obvious patent to companies such as Microsoft. I believe the USPTO has a political and trade agenda, and is not as clueless as you say.

  136. Re:Wah! Wah! by DaVince21 · · Score: 1

    You're missing the poi--

    Wait, you're a troll. Nevermind then. Hope you'll contribute something more interesting next time.

    --
    I am not devoid of humor.
  137. Re:This is why software patents shouldn't be allow by True+Grit · · Score: 1

    fluent legalese

    Wait a sec, I think we have a new candidate for best oxymoron since 'Military Intelligence'.

    I like it!

  138. Re:This is why software patents shouldn't be allow by True+Grit · · Score: 1

    Law is the programming language for the system of society. The problem is, ...

    My gut tells me the problem with your analogy (no offense, it is a nice effort; at least you didn't use cars in it), is more profound:

    The vast majority of users of a programming language view it as a *tool*, where normally (outside of obfuscation contests) one of its most valuable traits is considered to be *clarity*.

    The vast majority of users of Law's legalese language view it as a *weapon*, whose ability to completely avoid clarity altogether is considered to be its most valuable trait. Indeed, it would be utterly useless to its practitioners, considering the purpose for which they use it, if it could *not* do this.

  139. Re:Patent office needs to be revoked of sudo acces by True+Grit · · Score: 1

    No, we just need to disable Microsoft's access to run /usr/sbin/grantpatent as root in /etc/sudoers. ;)

    I have a simpler, quicker solution that doesn't even require messing with any conf files:

    'rm -f /usr/sbin/grantpatent'

    Or find whichever idiotic package that installed that crazy-ass binary, and nuke *it* from orbit...