Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Openly Provides Kerberos Interop Specs

Posted by ryuzaki0 on from the it's-still-copyrighted-material dept.

konstant writes: "Microsoft has published a document on its TechNet security site providing most of the information in the infamous CAB file plus sample code. There appears to be no onerous license this time." Well, it's not the *whole thing* but has lots of useful info about Microsoft's Kerberos implementation. Strange note: the page where this appears has a footer that says, "Last updated January 21, 2000," but when I did a search on Microsoft.com during our little tussle with them last month, I didn't find it.

2 of 119 comments (clear)

  1. Did MS back off or what? by carlhirsch · · Score: 5

    but when I did a search on Microsoft.com during our little tussle with them last month, I didn't find it.

    What ever happened with that tussle, anyhow? Did MS slink away when Andover's lawyers got tough or what?

    -carl

    --
    . We've got computers, we're tapping phone lines, you know that ain't allowed - Talking Heads, "Life During Wartime"
  2. Re:Whoa, Microsoft supporting GNU tools? by Carnage4Life · · Score: 5

    Wow, MS is recommending interoperability with Solaris using GCC! Personally, I never thought I'd live to see this.

    It's not too surprising once you realize the amount of people with *nix backgrounds that they hire. I have three friends who work there and they all either own a Linux box or have hacked Open Source projects at one time or the other.

    The problem with MSFT isn't that they are evil or that they are out to screw Open Source but that they truly believe that the Microsoft Way will advance technology and bring the coolest technology to the masses. It is this belief in their rightness that makes them (at least at the developer level) dangerous to Open Source and third parties. After all, if you believe that without MSFT technology the world would be in the dark ages and your mom wouldn't even be able to use a computer without MSFT wizards and GUIs, then you'd begin to have a certain kind of tunnel vision which would border on delusional.
    Basically what I'm trying to say is this, they don't go out of their way to not be interoperable, it simply is that interoperability never crosses their minds when creating software.