Slashdot Mirror


Slashback: Bundestux, Kerberos, Blizzard

Slashback tonight with several updates and amplifications, starting with a nice report on the current state of the effort to put Linux into the heart of the German government, but also bits on Starcraft, cleaning up UNIX config, and Kerberos.

This deserves a hearty 'Jawohl!' DocSnyder writes: "Since the Bundestux campaign started collecting votes in favor of putting Free Software into the German parliament (Bundestag), more than 25000 people have done so. A lot of online discussions - in addition to Heise News and Linux-Community.de, even some Bundestag parties have put up their online forums - are very active to share user experience about GNU/Linux and Free Software. (Sorry for most of the linked sites speaking German, it's simply too much to translate at once.)

After several open letters and press releases have been exchanged between lobbyists and politicians, some information about a research performed by the German company Infora appeared on Heise News (english version), recommending an all-Microsoft infrastructure with the exception of some security-critical services like e-mail. The detailed paper is still not available.

An internal test (english version) between the Bundestag administration, SuSE, IBM and Microsoft confirmed that GNU/Linux and Free Software are in fact ready for the Bundestag's IT infrastructure, yet the testers don't like the copy&paste method used by KDE and recommend Windows for the desktops.

Last week, the Bundestag members (MdB) Jörg Tauss and Hans-Joachim Otto have been invited by Heise for an online chat with the community. While Jörg Tauss is a clear supporter of open standards and Free Software, Hans-Joachim Otto takes the internal test as well as Infora's research as primarily relevant for the coming decision.

On Saturday, MdB Uwe Küster summarized some details in an interview. He considered the decision - officially due Feb 28 - as almost finalized. The solution would show GNU/Linux on most servers, Windows XP and Office XP on the desktops, keeping proprietary data formats and lock-in interfaces up to the next upgrade cycle, which in fact would have been problem number one to solve.

All in all, the community has provided lots of experience, ideas and solution paths which finally seem to be largely ignored in the decision finding process towards the successor of a homogenous Microsoft Windows NT4 infrastructure, which has to be replaced until 2003 when Microsoft will no longer provide support for NT4."

That's a lot of cleaning up to do! maffew writes "A lot of feedback and ideas have been flying around since my article How to fix the Unix configuration nighmare was featured on freshmeat and slashdot. So we've created an ongoing web site and mailing list for people to continue discussing, organising, and hopefully in the end coding. It's all at unixconfig.sourceforge.net.

Meanwhile here's a link to the permanent home for the nightmare article. This is where I'm making revisions and adding links."

Raise your hand if this would mean seeing it for the 4th time ... Chris Brewer writes "In case you've been living on a different planet, The Fellowship of the Ring picked up Five Baftas, the British equivalent of the Oscars, including Best Director, Best Film, and Peoples Choice. During a live interview (Real only) after the awards, Peter Jackson announces that a preview for The Two Towers will be shown from the March 22 screenings of The Fellowship."

At long last ... something? If you've followed the strange relationship Microsoft has had with Kerberos, you may feel grateful to the anonymous coward who writes: "It would seem that Microsoft is granting the world a royalty-free, non-exclusive license to implement their Kerberos extension."

Here's some comfort for Starcraft players. An Anonymous Coward writes "As stated on Blizzard's battle.net service, the latest Starcraft patch supports UDP play, so some of the compelling reasons to use bnetd have been addressed. Whatever you may think of Blizzard and the DMCA, at least it shows Blizzard is listening to its fans."

11 of 309 comments (clear)

  1. MS Kerberos, a corporate culture of wrongness by WasterDave · · Score: 5, Interesting

    Yipee! They published their wire protocol:

    "All data is encoded as little-endian."

    Oh, god. Look, since the start of time itself binary data on the net has been big endian. No, you do not know better.

    Head->table: Bang! Bang! Bang!

    Dave

    --
    I write a blog now, you should be afraid.
    1. Re:MS Kerberos, a corporate culture of wrongness by Rob+Riggs · · Score: 5, Informative

      Byte ordering is arbitrary if you don't give a hoot about interoperability or standards. It's not called "network byte order" for nothing. It's the default byte ordering for all RFC-defined internet protocols -- including Kerberos itself.

      Almost all network software uses "hton*" and "ntoh*" functions to convert the byte ordering from host to network byte order and reverse. On big-endian machines they happen to be NOPs. So now what? Everyone implementing the protocol on big-endian machines has to implement their "itoh*" and "htoi*" ("idiot to host", "host to idiot") functions. And to implement any software portably you'll need the same functions on little-endian systems as well. OK, so now you can write your non-portable apps without the "ntohl" -- that's OK if don't care about playing nice with others. Those of use who work in heterogenous environments and write software for a living do care.

      Sure, network byte ordering is arbitary. But big-endian was chosen long ago and causes no harm. What Microsoft did is just a good way to piss off folks who care about everyone playing nice on the internet.

      --
      the growth in cynicism and rebellion has not been without cause
    2. Re:MS Kerberos, a corporate culture of wrongness by Rasta+Prefect · · Score: 5, Insightful

      Um, I don't mean to flame, but why does it matter? Byte ordering strikes me as rather arbitrary.

      Yes, it's completely arbitrary. Which means that since Kerberos is supposed to be Big Endian, Microsoft had no compelling reason to screw with it. Its arbitrary, but by no means interchangable. Now when using Kerberos you actually need the check every time you use an integer to determine which way 'round it ought to be, thus allowing for a whole new class of bugs. Hooray.

      --
      Why?
  2. Linux on desktops by blibbleblobble · · Score: 5, Insightful

    So the linux clipboard (or lack of compatibility thereof) provides enough reason for them to buy and use Windows/Office XP?

    Sounds like a reason to fix the shitty broken clipboard, then. I'll be grateful when I can at last paste from KMail into Mozilla.

  3. Microsoft bows to outside pressure? by AndyDeck · · Score: 5, Interesting
    I'm practically speechless here... Microsoft has actually relinquished a proprietary lock.

    I am neither expert enough at Kerberos nor Samba to know if the above-referenced web page (Here in case you missed it) is truly sufficient for interoperability, but it sure looks like it.

    And the critical language is at the bottom:
    Microsoft grants you a perpetual, nonexclusive, royalty-free, world-wide right and license under any Microsoft copyrights in this specification to copy, publish and distribute this specification, and to implement this specification in your products.

    and

    Microsoft is not currently aware of the existence of patent(s) and/or pending application(s) that are essential to the implementation of this specification. However, if Microsoft becomes aware or has any patent(s) and/or pending applications that are essential to implement this specification, Microsoft will grant you a royalty-free license under applicable Microsoft intellectual property rights essential to implement this specification for the sole purpose of implementing this specification. Microsoft expressly reserves all other rights it may have in the material and subject matter of this specification. The licensing commitments made hereunder do not include any license for implementation of other published specifications developed elsewhere but referred to in this specification.


    Translation: You can use this spec in your products. It's not covered by any of our current or pending patents, and even if it is, you can still use it royalty-free.

    Other related specs are not rendered licensed or royalty-free, so they MAY have kept a loophole - but this looks sincere so far.

    Amazing news, really.
    --

    The Crystal Wind is the Storm, and the Storm is Data, and the Data is Life
  4. Two Towers Trailer at END of Movie by cybermage · · Score: 5, Funny

    Most people, at least in the US, don't bother to sit through the ending credits; so, they'll miss the trailer for Two Towers unless they're told about it as the trailer will run, properly, after the movie.

    Of course, given what theaters pay their workers, let's hope they actually tack it to the end and not the beginning. ;)

  5. Re:That darn clipboard by Bilestoad · · Score: 5, Insightful

    Here's why Linux isn't making up ground on the desktop. When someone says something doesn't work right the response is RTFM, or that it is supposed to be like that. If Linux is going to succeed in environments like the German government then intuitive or ingrained use patterns should be the norm, no matter how much geeks like the other way and no matter how much it might seem like windows. Geeks can turn it back the other way if they like, they know how.

  6. Starcraft by Anonymous Coward · · Score: 5, Interesting

    Actually the UDP support has nothing to do with bnetd. Starcraft was ported to Mac OS X, which doesn't have a working IPX protocol that they could use. So rather than try to graft IPX onto the Carbon version of Starcraft they created a new UDP version for LAN play with OS X, then added UDP to the other versions afterwards.

    There were a few posts to insidemacgames.com's forums by the Blizzard techs who made the patch.

  7. Re:Copy and paste of all things... by spitzak · · Score: 5, Informative
    No, they are probably complaining about the simple inability to cut & paste text.

    It is true that selection and middle-mouse click will work between all X applications.

    However Windows users are used to ctrl+x and ctrl+v. Most X apps initially supported this by simply making ctrl+x do nothing (because the text was already selected) and making ctrl+v do the same as middle-mouse click. This is how current KDE applications work.

    This worked pretty good, but it turns out most Windows users were also used to selecting the text they wanted to replace and then typing ctrl+v to replace it. This unfortunately changed the clipboard and the paste did not work. They do have a point that this is confusing to anybody coming from Windows.

    There are several kludges an app could do to detect this and do what the user expects, but it appears the solution adopted, first by Motif programs like Mozilla and then by GTK and several other toolkits, was to have 2 clipboards, one for the selection and another for the most recent ctrl+x. In many ways this is an ideal solution, as in fact the middle mouse is really equivalent to drag & drop and is best combined with that mechanism, not the clipboard.

    The problem now is that KDE apps (and quite a few others, I'm sure) do not understand this. Typing ctrl+v still pastes the selection. Since this is usually the same as the clipboard except for the "select and replace" Windows reflex it probably isn't any worse than before. However the opposite way is a pain, as ctrl+x in KDE does nothing and ctrl+v in a newer program then pastes and older ctrl+x, which I am sure drives the user nuts.

    Yes the next version of KDE will fix this.

    PS: the newest versions of FLTK match GTK as well, it had the same problem as KDE.

  8. Re:Listening to which fans? by Bowfinger · · Score: 5, Interesting
    Be reasonable. D1 was great in its day. I lost thousands of hours to it. But D1 is a dead product, superceded by D2. If you liked the original, you will probably like D2 even better. It's the same basic game, but with far, far greater variety and replay value. Of course, if you didn't like D1, you may not like D2 either. To each his own.

    There is no replacement for StarCraft. There doesn't appear to be one on the horizon. I think it is remarkable that a company like Blizzard continues to support and enhance it. How many other companies are still provding free patches for five-year-old games? How many other companies even provide bug fixes for old products like this with little sales potential?

    I too am concerned about Blizzard's actions with respect to bnetd. I understand their legitimate need (and their right) to control the spread of the Warcraft III beta, but they overreacted. I hope this is just an aberration. Too many companies seem to have run out of fresh ideas of their own, so they use the legal system to suppress fair competition. It would be a shame if Blizzard has joined that list.

    Yes, Blizzard has problems. If you look at their overall record, I think Blizzard is still one of the good guys. There don't seem to be many of them left. Give Blizzard a little slack, at least for a while longer.

    But that's just my $0.02 worth.

  9. Read the X clipboard explanation before commenting by Guy+Harris · · Score: 5, Informative

    If you plan to comment on the "cut and paste" issue, please read the X clipboard explanation, in detail, and make sure you fully understand it before commenting.

    X - or, at least the X11 Inter-Client Communication Conventions Manual (ICCCM) - does specify a clipboard that works like the MacOS/Windows clipboard. Selecting text does not have to copy to that clipboard; it merely has to set the "primary selection". The middle mouse button can paste the "primary selection". Ctrl+C and Ctrl+X can copy/cut to the clipboard, and Ctrl+V can paste the clipboard even if you've subsequently selected something else (in which case it replaces the selection with what you're pasting).

    Motif and GTK+, for example, work that way. Qt 1.x and 2.x, as used by KDE 1.x and 2.x, didn't; Qt 3.x, as used by KDE 3.x, works that way.

    The KDE announcement speaks of the primary selection and the real clipboard as both being clipboards; that was, as far as I know, done to avoid "frightening the horses", i.e. to work around the confusion that some people suffer from, thinking that selecting text copies it to "the clipboard". The ICCCM doesn't call them both clipboards (it calls them both selections; for better or worse, that's standard terminology inside the innards of X, but you don't have to call them "selections" when talking to users).