Slashdot Mirror


Slashback: Mars, Linksys, Torrent

Slashback tonight brings updates and followups on several recent Slashdot postings. Among other things, Linksys says they're not violating the GPL, and Tiger Direct says that Michael Robertson's claims about Microsoft targeting Lindows buyers are way off base. Speaking of which, Microsoft has decided it makes more sense to embrace schools than to alienate them with hard-nosed licensing policies on donated PCs. Also, a torrent file for the Red Hat 9 version of Ximian's latest desktop, and more. Read on for the details.

Fork carefully or be forked preemptively. BSD Forums writes "The leader of the open-source JBoss Java application server environment said that if the group of developers that left his organization attempts to splitâ"or "fork" as it's called in the industryâ"the JBoss code base, he would sue them. Marc Fleury, president of JBoss Group LLC, Atlanta, said he is prepared to take legal action if the group of developers who left the JBoss Group to form a new company, known as Core Developers Network LLC, attempts to diverge from the JBoss code base."

They can learn in the classroom, or outside it. MVP writes "Fridrik "frisk" Skulason, of F-Prot fame (you know, that good old DOS free for personal use antivirus, up-to-date & usable for windows), has a very acid reaction against the decision of University of Calgary to start teaching virus-writing classes (see previous Slashdot thread)."

Just let me control the textbooks ... After a few stories like this one, it may please some people to see at least a partial turnaround from Microsoft on computers donated to schools without Windows licenses. Patrick Cable II writes "I got an interesting letter from Microsoft today at work. Microsoft has started a "Fresh Start" program for educational instutions that basically makes it so schools who have had computers donated to them without licenses or media can get media and a letter stating the computer is licensed to use a Windows operating system (98 or 2000). More information can be found here. Anyone think they're trying to figure out a way to deal with the whole Linux thing?"

Software in the Public Interest has yet to respond with a lower licensing fee for Debian.

More fun than "The Winds of War." For fans of Kim Stanley Robinson, space exploration and colonization, space elevators et cetera, reader Unbeliever writes with new that Hurd will soon meet Mars. "No, not GNU/Hurd, but Gale Ann Hurd. Hurd just signed a deal with Sci-Fi to produce Kim Stanley Robinson's Red Mars as a Sci-Fi 6-hour miniseries. Red Mars is the first of the Robinson's Red/Green/Blue Mars Trilogy, an 'almost plausible sci-fi' future-history approach about Colonizing and Terraforming Mars. The trilogy looks at the technological, sociological, personal, and political challenges of terraforming a different planet. Also of interest to Slashdotters in general is Robinson's ideas on the growth of multi-national corporations into Meta-Nations, and their effects on world politics."

But doesn't that make it radio their way? In the recent Radio Your Way review, our reviewer said of the device that it had "[n]o off button! As far as I can tell, once you turn the device on there is no way to manually turn it off other than to wait for it to enter sleep mode after several minutes. Very annoying."

Another reader writes with this workaround: "In any mode, hold down the stop button (a little square under the play button) for 2-3 seconds to turn off the unit. This is listed in the manual, which you are right, is a very poorly done Korean effort."

Calm down that jerking knee, then apply ice. In response a post which raised the question of whether Linksys was in violation of the GPL by not distributing, nor offering links to, the source code for the software controlling their 802.11g base stations. A representative from Linksys-PR sent in this note about the "missing" source code:

Linksys is a strong proponent of both Linux and the Open Source movement. The code within our routers is using User Space code without linking dynamically or statically to any GPL (GNU GENERAL PUBLIC LICENSE) code. Any code which does not have a static or dynamic link to anything covered by the General Public License is not GPL'ed, and can be considered closed source.

We regret it took some time to respond to this posting. To assure timely responses to inquiries like this in the future, please use the following procedure which complies with the requirements of the General Public License:

1. Please put your request in writing or in an email addressed to info@Linksys.com
2. You have to request the code for the specific modules you want. It is not valid to issue a request for any "code you may be using."
3. Technically, you are also supposed to provide us with a self-addressed stamped envelope, along with funds to cover the cost of providing the code to you. But Linksys will handle requests on a case-by-case basis. Thank you."

Straight from the Tiger's mouth. Tiger Direct Executive Vice President Richard Wallet wrote to contradict Michael Robertson's claims that Microsoft was targeting Tiger Direct customers who purchased Lindows systems to offer them steep discounts on Windows XP. Wallet writes:

"TigerDirect is not selling any version of Windows for $50. We are selling Microsoft Windows XP just like any other reseller and we are in compliance with all of Microsoft's licensing agreements, no better, no worse, and no different.

TigerDirect does sell low-cost systems with the Lindows operating system. TigerDirect also sells low-cost systems with Microsoft Windows XP. TigerDirect even sells systems with NO operating systems. The only parties who can tell us which products are or aren't worth selling are our customers. Neither Microsoft nor Lindows has a significant influence on what we buy and sell. We aim to serve our customers with the products they want at the very best values available and world-class customer service.

TigerDirect did in fact perform a survey of its customers as it does on a regular basis. Contrary to the author's claim, this survey was not only sent to Lindows buyers. It was sent to everybody who bought systems from TigerDirect during a specific time period. The purpose of the survey was to help us better serve the needs of our customers by getting a better understanding of what they're using the systems for, what they're running on them, and why they purchased what they did. The result of the survey is going to be to help us better align our PC product mix to increase sales."

Many monkeys make slick visuals. IamTheRealMike writes "Hi all, there is a BitTorrent of the XD2 RPMs for Red Hat 9 available, please be gentle with it. It comes as a directory that contains a readme and an ISO - make sure you read the readme first as there is a bug in the installer you need to know about. When all is done and you've read the instructions, just mount the ISO using the loopback device and point the installer at it. For all those who have been trying and failing to get it using the mirror network, this might provide a useful alternative."

61 of 344 comments (clear)

  1. License protection? by The+Bungi · · Score: 5, Insightful
    Marc Fleury, president of JBoss Group LLC, Atlanta, said he is prepared to take legal action

    JBoss is open source... doesn't the license protect the guys that walked out? Does this mean that Mr. Fleury will sue me as well if I do a JBoss knockoff?

    1. Re:License protection? by ctid · · Score: 5, Informative

      He's prepared to take legal action if the guys who walked out fork the code and call the new product JBoss. I understand the Fleury's organization has trademarked "JBoss".

      --
      Reality is defined by the maddest person in the room
    2. Re:License protection? by The+Bungi · · Score: 5, Insightful

      Possible. But I wonder how "based on JBoss" or "from the original developers of JBoss" would fly in that situation. After all, if you're taking GPL'ed code (or any other type of license for open software) and aggregating it to create your own (obviously open) software solution, you can't help but say "this is based on the code for product X".

    3. Re:License protection? by rimu+guy · · Score: 3, Informative

      I'm sure what Mr Fleury means is that he owns the JBoss trademark (it is a trademark, see the little â in the logo?), just like Linus owns the Linux trademark.

      If the Core developer group forks the code, then they JBoss LLC would be within thier rights to prevent the Core Developer Network using the trademark.

      The CDN guys would have to come up with their own name for the app server.

      They should be able to do it sucessfully. And it would be another case of history repeating itself. JBoss used to be called EJBoss, but Sun stomped on them for using _their_ EJB trademark.

    4. Re:License protection? by d3faultus3r · · Score: 2, Funny

      Or you could follow linksys's lead and not mention it at all.

      --
      read my blog
      musings on politics and technol
  2. Put your questions in writing or e-mail by Angry+White+Guy · · Score: 5, Funny

    1. Please put your request in writing or in an email addressed to info@Linksys.com

    I think that you forgot something, or the post office got way more efficient.

    --
    You think that I'm crazy, you should see this guy!
    1. Re:Put your questions in writing or e-mail by Fzz · · Score: 5, Interesting
      It's amazing what will get there, so long as the address is unique. I once addressed a postcard to:
      username@sun.com
      Sun Microsystems,
      California, USA
      I couldn't remember either how to spell my friend's surname, or her address, but could remember her email address. And it reached her in a couple of days.
    2. Re:Put your questions in writing or e-mail by dschl · · Score: 5, Interesting

      My mother-in-law delivers mail in a small town of about 5,000 people. My favourite post-office story is from a few years ago, when they received an envelope with a child's handwriting on the outside. The envelope contained only two words on the outside - "Mom", and the name of the small town.

      The post office staff figured it out, and the mail went through. I think they used the postmark, which identified the city from which it was sent, and successfully guessed which divorced / separated woman had children living in that city.

      --
      Slashdot - the place where you can look like a genius by restating the obvious
    3. Re:Put your questions in writing or e-mail by u38cg · · Score: 2, Interesting
      A few years ago, in mid-January, my mother received a Christmas card - a bit late, but given that the only thing written on the envelope was her name, we forgave them.

      I suppose it helps that only a dozen people in the UK have our surname, but even so, it must be tempting to just chuck such items away.

      --
      [FUCK BETA]
  3. Why package RPMs as an ISO? by Wesley+Felter · · Score: 3, Insightful

    BitTorrent can distribute directories of files, so why add the extra obfuscation?

    1. Re:Why package RPMs as an ISO? by TummyX · · Score: 4, Interesting

      Cause then you know you have an *exact* copy of the CD. I hated having to download individual files cause you'd never know if you got them all properly. Try running an MD5 sum on 10000 files.

    2. Re:Why package RPMs as an ISO? by kyoko21 · · Score: 2, Informative

      Actually, bittorrent performs a check sum for you during download so you don't have to MD5SUM all 1000 or so RPMS.

    3. Re:Why package RPMs as an ISO? by parkanoid · · Score: 4, Informative

      BT checks file integrity by SHA1 hashing; MD5ing the files is redundant, unless you do not trust the original seed.

  4. What is xd2? by m0nkyman · · Score: 4, Funny

    What is XD2, or is this something that all the cool kids know about, and I don't, so you won't tell me, because I'm not one of the cool kids, and by the way here's my lunch money, please dont't hax0r my box, I didn't say nothing to you, please?

    --
    ~ a low user id is no indication I have a clue what I'm talking about.
    1. Re:What is xd2? by stefanlasiewski · · Score: 3, Funny

      Dude, it's eXtreem Deathmatch 2, a new multiplayer mod for Halflife 2.

      Why aren't you playing it right now!?

      --
      "Can of worms? The can is open... the worms are everywhere."
  5. Sickening by Rosco+P.+Coltrane · · Score: 5, Funny

    Speaking of which, Microsoft has decided it makes more sense to embrace schools

    Kids beware, Microsoft now embraces schools. Learn to recognize Microsoft employees : they're the funny-looking people with long raincoats waiting for you outside the school.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:Sickening by csguy314 · · Score: 2, Funny

      MSPusher: Psst... Hey kid. [opens trench-coat, displaying many install cd's] You want a copy of Microsoft Office?
      Innocent Youth: Ummm, I don't know. I hear that stuff can be dangerous.
      MSP: All the cool kids are using it. You want to be cool doncha?
      IY: Well...
      MSP: Tell you what, I'll give you this copy of Office for free. All you have to do is sign this license...

      --
      This is left as an exercise for the reader.
  6. JBoss fork - misleading headline by ninjaz · · Score: 5, Informative
    Quoth the article:

    "I did think about them forking," Fleury said. "If they fork JBoss, that's another problem. If there's a new JBoss, if they fork it and call it JBoss I would sue them. There is only one version that we control."

    So, a suit was only threatened in the case the forked version used the same name as the original (presumably on trademark grounds).

    1. Re:JBoss fork - misleading headline by OMG · · Score: 2, Informative

      Telkel was Marc's first try to make money for a living.
      Telkel failed. Marc didn't give up, stayed with open source and continued the work on JBoss.
      When JBoss.org has been registered in the past there didn't exist such a thing as the commercial service company "JBoss Group". In the early days of JBoss Group they had a separate "area" on JBoss.org (or even their own domain, can't remember). Today JBoss.org does attract a lot of people, so they want to leverage that for the commercial service group. As a result the domain jboss.org was transfered from Marc to the JBoss Group LLC.

      Remember: The developers that are part of JBoss Group are still developing HEAD and fixing bugs on it for free. The code is released under LGPL and thus safe from being bought by MS.

  7. JBoss Certification Hassles by sbszine · · Score: 4, Insightful

    I've said this before (when the original article was posted), but I still suspect the JBoss split is related to their Sun certification troubles.

    There's an interesting ZDnet article here that talks about JBoss not being 100% kosher J2EE, and the main group's ongoing dispute with Sun. I think that the breakaway group intendeds to fork JBoss to make a more easily certified version, and this Slashback seems to support that somewhat.

    --

    Vino, gyno, and techno -Bruce Sterling

    1. Re:JBoss Certification Hassles by fm6 · · Score: 2, Interesting
      The cert. hassles might have helped raise tempers. But leaving JBoss won't make it any easier for these guys to get their code certified. Well, maybe a little, if you assume the working relationship between Fleury and his developers went sour. Java certification is a pretty controversial area right now, and there's a lot to suggest that Sun's process is pretty arbitrary.

      The Slashdot story and the Blog buzz all say this is about a bunch of developers wanting their own JBoss fork. The Core Developers party line is that they just don't want to be tied to JBoss to the exclusion of competing products. Any other explanations?

      Probably there's some truth to all these stories.

    2. Re:JBoss Certification Hassles by sbszine · · Score: 3, Interesting

      Well, according to Sun, the reason they won't certify JBoss is just that JBoss won't cough up the (reasonable) money for testing. Core Developers might be more inclined to pay if they create their own fork.

      Probably Sun will be the real winner as this encourages one fork or the other to give them some cash money. More bling bling gold chains for McNealy : )

      --

      Vino, gyno, and techno -Bruce Sterling

  8. One more thing by The+Bungi · · Score: 5, Insightful
    Tiger Direct Executive Vice President Richard Wallet wrote to contradict Michael Robertson's claims

    Here's a revolutionary idea. Instead of posting hysterical flamebait stories to the front page, how about you do your homework before the fact? Is it so difficult to email the guy beforehand and ask him for the real story? You sit on submissions for days sometimes, so how problematic would this be?

    I know that posting another "M$ is doing evil" story contributes to the bottom line with all the ad impressions and whatnot, but taken as a whole your FUD is no better than Microsoft's. And that puts you on the same ethical bandwagon.

    1. Re:One more thing by Wonko42 · · Score: 2, Funny

      I've tried on numerous occasions to contact TigerDirect regarding gaping security holes in their site, and I've never received a response. Perhaps the only reliable way to get a response from them is to post a story on Slashdot.

  9. about Linksys providing source code by narfbot · · Score: 4, Informative

    According to guy who reported Linksys possibly not providing source code, his contact within Linksys finally responded and said the lack of source with the WRT54G was unintential. His contact also said that previously they shipped their products with source code on a CD. I found this on the lkml shortly after the slashdot article.

    1. Re:about Linksys providing source code by andersen · · Score: 5, Insightful

      Thats fine. But as maintainer of BusyBox, which is being illegally shipped with their router without source in violation of the GPL, I had my lawyer send them a lease-compily-with-the-license letter on May 13th. Then did not respond. So I had my lawyer send them a letter letting them know we will sue them if they have not responded by June 16th. I don't care what their PR department says. I expect a proper response from their legal department or we will see them in court. I am tired of people trampling over the GPL and then giving a lame little "oops, sorry" when they get caught. When I walk into the local CompUSA, there is a isle filled with GPL violating routers. Until each of these routers includes a copy of the GPL'd sources, or includes a written offer to obtain the sources for the cost of the media, they will still be violating the GPL. They do not include the source with these routers. And they do not include a written offer for source. Therefore, they must offer source via their website to comply with the GPL. Anything less then that, and they are what microsft would term "software pirates" -- shipping software in violation of the software license agreement.

      --
      -Erik -- --This message was written using 73% post-consumer electrons--
    2. Re:about Linksys providing source code by Stephen+Samuel · · Score: 3, Interesting
      Platitudes about being friends of the OS movement aside -- The 'offer' that came from their PR group isn't even close to being within the bounds of what the GPL requires. If you read their response, they're demanding that I go into their binaries and figure out which pieces of GPL code they have in the machine, and then write them with a list.

      As a (pirate, at the moment) distributer of GPL software, it's their legal responsibility to inform us about which pieces of they're using so that we can then ask them for the source code. and given that they're the ones who violate the license, I figure that they should be the ones beending over backwards to make things easier for us not the other way 'round.

      Technically: having violated the GPL, on the code in their routers, they're now GPL limbo. They have lost all rights distribute the software, and must now do whatever it takes to satisfy the GPL copyright owners that they're not going to do this again.

      I take that back.

      They have to do whatever it takes to satisfy the GPL copyright owners period. Nominally, I would expect this to be something like payment of legal fees, putting a prominent notice on their website and distributing free source CD's via all of their distributors -- but there's no reason why it couldn't include a $500K 'administrative fee' as well.

      Of course, if they keep on stonewalling, some GPL owners could just refuse permission outright.

      --
      Free Software: Like love, it grows best when given away.
    3. Re:about Linksys providing source code by Anonymous Coward · · Score: 2, Insightful

      Really, all things considered, there isn't any reason why Linksys couldn't just use a BSD, NetBSD is more than likely suitable. So as for other works, in most cases, it's just as easy to implement the additional code for things such as IP updating.

      Personally, I would release the source to what's been released already. Then I would spend a few extra dollars on developers to make a BSD based system instead. After all, if the real guts have been done using a user mode program, then there's really no problem in porting it. If there has been some kernel mode items made as well, there's really no reason that can't be ported to BSD which often is well documented enough to do marvels in short time frames.

      I think that GPL software is worth how much I paid for it, but in the case of design wins such as LinkSys, I would definately try to sort things out nicely instead of noisy since it could simply provoke them to move away from Linux instead. This would do far more damage to the Linux community since if Linksys moved due to frustration with the GPL, then more companies are likely to see it as a problem and simply not use GPL at all.

      For Linux which is still growing and still breaking ground on market acceptance, it could be damaging if movements were made to chase corporations off instead of helping make the acceptance grow further.

      I would suspect that the best idea would be to request a conversation between a GPL knowledgable spokesperson and either a higher up manager or company lawyer at Linksys. The idea isn't to scare companies off of GPL, but instead to educate them on how to best comply to the GPL. Remember most companies are interested in doing the right thing, but when challenged with law suits and such, they may move on the defensive. After all, so far what I've heard from the previous people posting on the topic, I feel that there has been little effort to speak peacefully with Linksys and instead people immediately open conversations with threats.

      I am not from Linksys, but I do work for a company where we've had GPL problems in the past on occassion, nothing serious, but enough that we had to delay products in high demand for Linux since we were afraid we didn't meet GPL. Now we take the Linux platform less seriously and have lost interest in many ways. After all, Linux is harder to develop for, it is harder to market for, it is harder to win customers in general, and many people treat Linux and GPL in general as a religion and are in my personal oppinion dangerously phenatical about it. Now even though we've tried to comply to GPL as best as we can, we still worry that there is some loophole in GPL which people will complain about.

      A great example if you're wondering what I mean. Writing software using an LGPL'd Standard C++ Library was not allowed by our attournies since the LGPL considers "Work based on LGPL code" as code which "Must be released under GPL or LGPL", the problem is we've learned that there's a chance we could face risk of litigation because the Standard C++ library is mostly templates and using this code in your product touches on unsteady ground because you don't link to a template, instead it becomes part of your code. This set us back a few weeks and caused us to have to purchase a commercial version which didn't integrate as well due to linking issues. This meant that software which people have used and have written many nice articles about has been delayed in every version because we have to take the legal issues concerned more seriously on Linux than on any other system.

      I would generally gladly sep forward and say who I am, but I feel that the phenatics involved with this web site may not be responsible enough to judge my statements as my oppinion as opposed to the oppinion of the company I work for.

      P.S. - I'm also worried that I'll get 100,000 e-mails calling me a loser that can't even spell :)

    4. Re:about Linksys providing source code by black+mariah · · Score: 2, Insightful

      From the GPL, section 3:
      If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

      Unless they modified the source for your software, they don't have to distribute it. Would you prefer that Linksys start their own distribution site, possibly with outdated versions of your software, to distribute code that is easily available directly from you? I agree that there should be a note or something in the back of the manual stating what software the router runs on and, if applicable, where to obtain it. According to the GPL, if I'm reading it correctly, an alternative to distributing the code yourself is stating where the code can be obtained (assuming no modification).

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
  10. I know it's legal but ... by Rosco+P.+Coltrane · · Score: 4, Insightful

    2. You have to request the code for the specific modules you want. It is not valid to issue a request for any "code you may be using."

    Well then, what if I ask Linksys to send me any GPL code they're using ? is that valid enough ? because mething they'd have to send it to me.

    As for asking what modules I want specifically, how would I know without reverse-engineering the product ?

    I know the GPL allows users of GPLed code to require people to ask for the source code of whatever GPL stuff they're using, but when Linksys tells you you have to ask in writing, including a self-addressed stamped envolope, I call that bad will. It would show good grace if they provided a link to the sources on their site, and it would cost them less than processing snail mail.

    So Linksys, put your money where your mouth is and show you're a real proponent of Linux and OSS. Right now, you look like freeloaders who want to make the process of getting your sources as painful as possible.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:I know it's legal but ... by Anonymous Coward · · Score: 3, Informative

      Read the GPL. There is no requirement that the sources be made available except when requested and only to the one who requested it. AND the requesting party has to pay for shipping and handling. Linksys is being nice by providing the media for free.

      Linksys could in addition just send you the source on magnetic tape as per the GPL, but that wouldn't do you any good, would it, Linuxboy?

      What you think the GPL says and what is actually written are fairly divergent. Best you get to reading it if you want to know what kind of protections and rights it gives you and takes away.

  11. Ximian Desktop 2 by hendridm · · Score: 3, Informative

    If you're serious, it's Ximian Desktop 2, although I find it odd that someone with such a low user id would ask in such an lame way.

    1. Re:Ximian Desktop 2 by MikeFM · · Score: 2, Funny

      On behalf of all users with low user id's I reserve the right to be lame anytime we wish. Besides even those of us that are godlike in our geekness can't be 100% perfect. We're like Linux - only 99.99997% perfection. ;)

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  12. "Hurd just signed a deal with Sci-Fi" by Anonymous Coward · · Score: 5, Funny

    That makes sense, I always thought GNU/Hurd qualified as computer science-fiction

  13. Linksys improving, but... by renard · · Score: 4, Informative
    2. You have to request the code for the specific modules you want. It is not valid to issue a request for any "code you may be using."

    Fair is fair; however, it is Linksys who is distributing the programs in binary form to begin with. They cannot simply provide a copy of the GPL in the documentation with their product and say that this covers "all GPL code distributed with this product" without themselves identifying what software the product contains which falls under the GPL. Here, check out the TiVO website for an example of how it's done.

    -renard

    1. Re:Linksys improving, but... by Omnifarious · · Score: 3, Interesting

      Linksys should not require you to reverse-engineer their product to figure out which portions are GPL before they will comply with a request for the GPL portions of the code.

      This is clearly not acceptable.

      They need to tell you which portions are GPL so you can request them. Also, a SASE should be considered a distribution mechanism of unreasonable cost in time and effort to the person requesting the code. The Internet is ubiquitous, and practically every Linksys customer will have access to it. They should provide it for free download.

      If they're worried about everybody downloading it, they only need to require you to enter the serial number of one of their products. That would stop most random people who they didn't distribute a binary version to.

  14. This follow-up didn't make it to this Slashback... by Anonymous Coward · · Score: 3, Interesting

    The NY Times article on 'Thedeacon' had it all wrong, apparently because of a personal vendetta or simply bad journalism:

    http://forums.anarchy-online.com/showthread.php? s= ff915490517fe192403f903ca23ea861&threadid=143417&p erpage=20&pagenumber=1

  15. Liability? by McCart42 · · Score: 4, Interesting
    Mr. Skulason brings up an interesting point:

    There is also the question of what if some student manages to smuggle a virus out of the lab and releases it. Does the University's liability insurance cover any potential damage the virus might cause.

    I was wondering this same thing myself...I would think the University would be partly liable in a court of law, though I don't really know if it should be. They are supplying the resources the student needs to create the virus, and educating them on how to do it. Now if they can show that they took every reasonable precaution to prevent it from getting out and the student still somehow snuck it out, then they might be OK--but consider the biological parallel: it's like showing someone how to make anthrax, giving them the means to do so, and then not having a secure lab environment, thus creating a hazard to the community.


    Like I said though, it ultimately comes down to the student's will to pull the trigger, but considering that the University is supplying the gun...it's shaky ground.

    --
    "I may be quite wrong." - Socrates
  16. As much as I respect Skulason... by Arker · · Score: 4, Insightful

    ...and even though much of what he says is correct (most virus writers, particularly nowadays, are just script-kiddies and not particularly good programmers) I can't agree with his main point. There are very valid reasons to write viruses as learning experiments. And not just for people interested in working in security either - as pure CS there is a lot to be said for it.

    He gives the impression that all viruses are harmful, but that's simply not true and he must know that. Many viruses, including all the early ones, were pure CS experiments in artificial life. They had no 'payload', no destructive nature, they just try to survive and reproduce, the basics of biological life transplanted to the digital realm.

    Now writing a virus with a destructive payload and spreading it to other people's computers - that is clearly unethical, but I really doubt that's what they have planned in this class.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:As much as I respect Skulason... by mshomphe · · Score: 3, Insightful

      I think his main point was that virus writing is a trivial task. You can always take an existing virus and tweak it to do what you want. It's low tech and crude to write a virus.

      He was basically saying that explicitly teaching how to write virii was a bad idea:
      (1) It takes no skill,
      (2) you're horribly accountable for the actions of the students in your class,
      (3) and you'd be better off teaching more in-depth responses to virii. For example, why does a certain exploit work? What's vunerable,etc.

      I have to agree with him...

      --
      She sat at the window watching the evening invade the avenue.
    2. Re:As much as I respect Skulason... by Erasmus+Darwin · · Score: 2, Interesting
      "He was basically saying that explicitly teaching how to write virii was a bad idea: (1) It takes no skill,"

      I have to disagree there. Awhile back, I was working on a benign project that involved fiddling with and understanding the low-level details of DOS executables. Some of the best online sources I found were virus-writing tutorials.

  17. JBoss: Nothing to see here -- move along by heretic · · Score: 5, Informative

    As usual, the trade rag is unnecessarily alarmist and so is the referring /. blurb. The quote of interest is:



    "I did think about them forking," Fleury said. "If they fork JBoss, that's another problem. If there's a new JBoss, if they fork it and call it JBoss I would sue them. There is only one version that we control."



    Fleury's saying he would not sue over a mere fork, per se, but instead a violation of the JBoss trademark. In other words, if CDN forked the code but called it something other than JBoss, there would be nothing to sue about.

  18. Problems with Virus rant by Omnifarious · · Score: 4, Insightful

    "The current approach of reacting to the viruses is simply not working."

    While this is true, it has more to do with flaws in human nature - as long as 97.3% (according to the research of Dr. Vesselin Bontchev) of people do not react in an optimal way to a virus infection, viruses will continue to spread. I fail to see how development of more viruses will help in that regard.

    I'm pretty tired of programmers who think people should adapt to machines instead of machines to people. So, people don't react in an optimal way to a virus infection. Perhaps someone will have some new ideas about how to create software that either makes the behavior change required easier and less annoying than not changing behavior, or makes it completely unecessary. Software is for people. People aren't for software.

    Most virus writers are simply not of that caliber...forgetting the "script kiddies" and those that only modify existing viruses, the remainder write so bad code that (assuming the code shows their true abilities) they would have a hard time getting a real programming job.

    This whole section has nothing to do with the point. Sure it takes more skill to write anti-virus software, but that doesn't mean a thorough understanding of how to write a virus wouldn't be helpful. It also doesn't mean that teaching someone how to write a virus turns them into a low skill programmer.

    One could argue that all the pieces of source code lying around that are designed to reproduce themselves in their output are a form of virus, yet writing them is considered an interesting intellectual challenge worthy of a serious programmer.

    I have a few comments regarding this section. It says that "No removable media will be taken out of the laboratory." I hope that this implies an armed guard at the door, doing a full body search of the students as they depart, because anything else would be insufficient. But what about things like printouts of the virus source code? Assuming that the students are really able to create a working virus, I sincerely hope that they will not be able to take home a printout of it, only to type it back in on their home machine. I would very much like to see some assurances in this area.

    This requirement is predicated on the automatically assumed malicious intent of anybody who writes a virus. The school is trying to protect against accidents, not a deliberate attempt to unleash a virus on the net as a whole.

    Preventing source code printouts is only a very minor deterrent against such maliciousness. So I don't think think it's worth considering putting into practice as it invites circumvention by treating the people taking the class as if they were criminals. People treated as criminals from the outset are more likely to act like criminals.

    The vast majority of the anti-virus community condemns the part that involves writing viruses, considering it ethically unacceptable, pointless, and outright stupid. On all mailing lists in the anti-virus community, all real virus researchers have agreed that what you are doing is unacceptable, and simply stupid.

    You may be secure in your academic ivory tower, not caring that your course is going to help legitimize virus writing, and will only lead to more viruses being written in the future - more problems in the real world which YOU will be responsible for.

    You create a mess, and then we have to clean up after you.

    The only valid point in the entire thing.

    The rest of it is all predicated on the assumption that anybody who takes the course automatically has criminal intent. I prefer not calling people criminals until they commit a crime. Writing a virus shouldn't be a crime. Releasing one into the wild should be.

    The social consequences of making virus writing seem legitimate is a real consideration. Though, I have an unfounded suspicion that the attitude that it isn't legitimate tends to inhibit a-life research some.

    1. Re:Problems with Virus rant by Alan+Cox · · Score: 4, Insightful

      Antivirus software ultimately is irrelevant, as is just about every other piece of "after they get in" type software. Security has to be about "they didnt get in" and more importantly "they got in but couldnt do any harm".

      Take slammer, mix with chernobyl and add disk firmware erasure. By the time something like that hits you its too late to update your virus scanner.

  19. The "bug" in the Installer for XD2 by M1000 · · Score: 5, Informative

    Here is the readme if you're wondering about it before downloading that 473 MB file ;-)

    btw, I love bittorrent... downloading at 250-400 k/s !

    --

    Note!

    To Install Ximian Desktop 2 for RedHat 9 (x86), please do the following:

    1) Burn the ISO to a CD.
    2) Mount the CD, and run installer-i386. make sure you have network
    connectivity. The installer will need a file from ximian.com, but it's only
    300k.
    3) Select "Local Media" and point it at where you mounted the cd (usually /mnt/cdrom for RedHat)

    4) THIS IS IMPORTANT!
    You'll get to a point where you verify what packages the installer will
    install. LOOK AT THE VERSIONS of the packages that will be installed.
    Note all the packages that do NOT have 'ximian' in the version number.
    These need to be installed from RedHat 9 media BEFORE continuing.

    If you see any packages that lack 'ximian' in its version, QUIT THE INSTALLER,
    install the missing packages, and rerun the installer.

    5) After noting 4, and installing the "missing" packages, rerun the installer.
    In a few minutes, you'll be able to enjoy your new XD2 install!

  20. Concerns Linksys's GPL claims by Adam+J.+Richter · · Score: 5, Informative
    2. You have to request the code for the specific modules you want. It is not valid to issue a request for any "code you may be using."

    Section 3 of version 2 of the GNU General Public License provides three options for those wishing to distribute GPL'ed software: (a) "Accompany it with the complete corresponding machine-readable source code [...]" (as I understand it, Linksys did not do this), (b) "Accompany it with a written offer, valid for at least three years, to give any third party , for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code [...]", or, (c) an option available "allowed only for noncommercial distribution" (not the case of Linksys). So, I infer that Linksys is now trying to get close to following option (b).

    The problem that I see with Linksys's claim that "It is not valid to issue a request for any 'code you may be using.'" is that without written offers that specifically identify exactly what GPL'ed software Linksys is using, and without source code to begin with, we cannot be sure that we know all of the source code that Linksys is using. For example, we don't know everything that was linked into their busybox image, and we might not even know every kernel device driver they use.

    It seems that Linksys sees two different specificity requirements in the GPL. Firstly, they seem to think that a blanket offer to provide code without identifying the source code that they are referring to satisifies the written offer requirements of section 3b. Secondly, they seem to think that they are not obliged to fulfill the acceptance of that offer when it is made with the same level of specificity. Linksys seems to think that they are fulfilling the GPL's requirements if they provide an offer to do x, but refuse to actually do it if someone simply says, "okay, I accept your offer." In other words, Linksys is not providing enough information in their offer for people to fully avail themselves of it. This is similar to offering to provide source code, but providing no contact information by which people can accept the offer. I expect that under some sort of "reasonable man" standard, a court would decide that these shenanigans are not in the intended meaning of the GPL.

    If I were in Linksys's shoes, I'd just dump of all of the GPL'ed source code involved into a CD image, send out CD's as needed, and also put it on an FTP site, which would probably reduce the requests for physical media to about a dozen (and, besides, the media costs less than postage and it's useful to have a mailing list of likely Linux wireless access point developers).

    Personally, I am mostly interested in the 802.11g drivers, although I suspect that some useful software may have been linked into busybox, which might be helpful to have too. I am glad that Linksys is trying to conform to the requirements of the GNU General Public License. Hopefully we can help them actually achieve that.

    By the way, I just sent info@linksys.com a request for the source code to the kernel and any software linked against BusyBox. I sure wish I knew what other GPL'ed software is in the WRT54G.

    1. Re:Concerns Linksys's GPL claims by Dominic_Mazzoni · · Score: 2, Insightful

      You may be right, but it could be that they'd be perfectly happy with a request like "please send me all GPL software that's used in my Linksys Wireless 4-port Cable/DSL Router". That ought to be perfectly specific enough and that may have been all they wanted. That's very different than "send me all GPL software that you've ever shipped a product with", which is what they might have been trying to avoid.

  21. Power off buttons by Skater · · Score: 3, Interesting

    "In any mode, hold down the stop button (a little square under the play button) for 2-3 seconds to turn off the unit."

    The CD stereo (an aftermarket Blaupunkt) in my car does something like this: to turn it off, you have to press and hold the power button for three seconds. Otherwise, it just reduces the volume significantly but continues to play. I've seen other brands do this, too.

    WHY?

    When I hit the power button, I want the radio to turn OFF. Right at that moment. If I'm turning off the radio, there's a good chance that I'm doing so because it's distracting me and I need to concentrate on the traffic and roads around me. Now, I'm forced to keep my hand at the radio (making it useless for steering or operating other controls, and it restricts my ability to look over my shoulders to check traffic in the blind spots) for several seconds. It's annoying.

    When I look at new radios, that's the first thing I check: the power button must work instantly. (I didn't pick this radio myself--it was installed by the dealer when I purchased the car.)

    If the manufacturers want to include a "mute" feature, fine, just add another button for it. Or better yet, use a volume knob; my other car has one and it works perfectly.

    --RJ

    1. Re:Power off buttons by AvitarX · · Score: 3, Insightful

      Buttons suck on car stereos.

      I cannot find any aftermarket equipment that has a nob for the tuner, a nob for volume, a nob for the fader, and a nob for the balance and an equilizer that has levers.

      Why should I need to push about 8 things to decrease the trebble so I can here less static in the traffic report?

      And why can't I just spin a nob to get the sound behind me (Some times I can't deal with it infron of me as I drive).

      Because of this I slump along with my crappy factory supplied radio and an RF modulation changer.

      Also why do they make AM and FM bands have differnt presets? I could use like 5 presets spread between the bands and not need to wory about FM1 FM2 FM3 AM1 AM2 I only listen to 5 stations why should I need to worry about what band I am set to at all?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  22. Linksys code capers... by deleted_soul · · Score: 2, Insightful

    Somebody help me out here..

    If they aren't statically or dynamically linking to the code. Then exactly how are they linking to it? Magically? The had to compile the code to work with linux base right?

    What bits did they leave in the open? Unless you disassemble their bio's there is no way to tell wether their code was in binary before it was compiled. Its really not in their best interest to just say 'See look, this is how I did it', even though they accepted the terms of the GPL in good faith. Maybe tomorrow we will find out how well the GPL will hold up.

    I do believe that any company that accepts the GPL should not be allowed to turn and run the instant they drop their side of the bargain.

    Maybe there should have been a GPL gurantee that starts the moment they sell a product based on linux sources. At least for commercial companies, so they can't say they didn't understand the GPL.

    --
    this sig is classified..how about yours?
    1. Re:Linksys code capers... by SuiteSisterMary · · Score: 2, Informative

      They took linux, compiled it, and are running it on their boxes. They then wrote a program which runs, under Linux, on those boxes.

      End of story. They have modified NOTHING which is under the GPL, so they don't have to release their own stuff. They are NOT required to post the parts of Linux they're using on their website, they're required to give it to whoever a) owns their product and b) specifically asks for it. They're also allowed to charge the cost of giving it to the person; hence the self-addressed stamped envelope.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  23. Two can play at that game... by benjamindees · · Score: 2, Funny

    Send them a polite e-mail requesting every piece of GPL software you can think of. And please post it and the response on /.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  24. obligatory rude pun by Artifex · · Score: 3, Funny

    So does this mean that, if they want to use the JBoss name for their independent work, Mark Fleury says to "fork off and die?"

    --
    Get off my launchpad!
  25. Mars Will Never Be Terraformed by Saeger · · Score: 3, Interesting
    Red Mars is ... an 'almost plausible sci-fi' future-history approach about Colonizing and Terraforming Mars.

    It's only plausible if you still think that technology is advancing linearly, instead of exponentially, and only if you assume humans will still be stuck in our fragile biological form for a period longer than the centuries it takes to terraform a planet in the first place. So no, IMHO, I think we'll sooner end up ripping Mars apart (oh the humanity!) to make better use of its matter, than wasting space & energy by living on its limited surface area.

    (Yeah, I've had a slight problem suspending my disbelief for most SF in recent years :)

    I'd much rather see Iain Banks' Culture brought to the screen, though that would be just a tad bit more difficult.

    --

    --
    Power to the Peaceful
  26. Re:its nice of microsoft; open source scores big by Jason+Earl · · Score: 3, Insightful

    Microsoft started seeing schools that were making successful switches to Free Software, and so now they are backing down. Essentially it is the same situation as a knife-wielding mugger backing down when his victim pulls a gun on him.

    Microsoft can posture all it wants, but second hand computers invariably had a Windows license in some part of their career. Heck, most corporate PCs actually end up purchasing the license twice. Asking schools to purchase yet another license when the computer is given away is just ridiculous.

  27. TiVo for Radio? by JRHelgeson · · Score: 2, Funny

    My TiVo box, a loyal pal,
    A friend I Truly care for.
    Because It guarantees I'll see,
    The shows I wasn't there for.
    Two thousand shows I've "taped" so far,
    Each Night I "tape" a new one.
    Who knows, perhaps there'll come a day,
    I'll find the time to view one.

    Now I have an opportunity to get behind on all that radio talk show stuff that was previously unimportant.

    --
    Good security is based upon reality and common sense. Common sense is a function of having common knowledge.
  28. Ethical? by Nurf · · Score: 2, Interesting

    I think it is more like spreading viruses is illegal while writing viruses is unethical. And I don't think you have to actually write a virus just to know how they work either.

    Hm. I just can't see that. I have written more than one virus in my time. Nobody got hurt. I played with them on isolated machines. I learnt something from doing it. It was a challenge and it was lots of fun. For example, I set myself the challenge of writing a virus that infected DOS .bat files and that was written in DOS batch language. I succeeded. That was almost as much fun as doing the boot sector stuff.

    It turned out useful some time later when I had a non-bootable harddisk and only an assembler on a bootable floppy (a magazine cover disk :-) ) with which to fix it.

    And at the end of all this, nothing got damaged. No people got hurt. I had fun watching my code wander around my systems. I played in assembler, and eventually deleted the viruses and moved on to other things, like artificial life simulations and genetic algorithms. 14 years later, I still have people oohing and ahing over the leet assembler skills I use on their embedded projects.

    How was this unethical?

    --
    ---
  29. Re:Red Mars... by Fenris+Ulf · · Score: 2, Insightful

    Good god, listen to yourself.

    If Jackson can do LotR decently in 6 hours, I think 18 will be enough for Red/Green/Blue Mars. The first three Dune books are just as voluminous, and SciFi did them well in 12.

  30. The mail by fm6 · · Score: 2, Interesting
    The USPS truely isn't that bad..
    Actually, the current USPS does a very good job, all things considered. They have every right to resent the term "snail mail", though they're probably stuck with it.

    But it hasn't always been this way. Horror stories about lost mail and general screwups were legion. UPS wouldn't even be in business if the Parcel Post hadn't been a complete disaster for years and years.

    I'm old enough to remember when the USPS was the federal Post Office Department and the Postmaster-General was appointed by the President. The job always went to the chairman of the party in power, because of all the patronage jobs. Needless to say, efficiency and quality of service were not top priorities. Most of the USPS's unfortunate reputation dates from this period.

  31. The Dirty Secret Of The AntiVirus Industry by xdroop · · Score: 4, Informative
    Something I wrote for my own personal site.

    I'm getting sick of the juvenile hair pulling which passes for morning radio here in Ottawa these days, so this morning I was flipping around during the drive to a client site. I landed on one of the CBC stations, and they were talking about this uproar caused by the Calgary university teaching a course which included a module on how to write viruses.

    The controversy is that many of the anti-virus organizations say that they will not cooperate with the university if they are writing viruses. That it is irresponsible to give people the knowledge they can use to release even more viruses out into the wild.

    There were two interviews, one by someone against the course (and he was keen to point out that the virus writing component was the only component he objected to, and that the rest of the course was fine by him) and by the head of the Computer Science division at the university.

    According to the opponent, the problem was that there were quite enough viruses out there thank you very much and we did not need more people with the knowledge of how to pump out more. This was countered by the professor who pointed out that anyone who was in a fourth-year accredited computer science program all ready had the knowledge needed and could bang one out in a couple of hours. In other words, they already have the knowledge to write the viruses, so what is the big deal?

    The point danced around by both gentlemen is that there is a dirty little secret in the anti-virus community. The industry of virus detection and removal is by definition a reactive rather than a proactive process.

    Let's back up here for a little background. When you are writing a virus scanner, you only have two ways to detect a virus, which I describe as the what it is technique and the what it does technique. In other words, in using the first technique you recognize a virus because you have already seen this virus before and therefore know exactly what it is. The second technique is used to recognize a virus by what it does, virus-like activities.

    To put this into terms that everyone can understand, the what it is technique is similar to the police knowing that John Q. Criminal is a mugger because he's been convicted of mugging people in the past. The what it does technique is similar to the police witnessing John Q. Criminal hitting another citizen over the head and absconding with his wallet -- recognizing such behaviour as mugger-type activity, and reacting accordingly.

    Back to our world of viruses. The what it is technique is a list of signatures of viruses which have been seen before. A signature is a string of some kind, along with some other data (such as the expected location of said string in the suspect virus, the expected length of the suspect virus, and so on). With this information you can categorically say: "This is a virus." And all of us with virus scanners know about this, because it is this information which is constantly being updated by our vendors.

    The what it does method of recognition is much much harder. It is called heuristics, and it is supposed to recognize virus-like activity so that the requirement for an up-to-date signature file is no longer needed.

    To understand why this is so hard, consider this example. Suppose that I am a virus, and I am going to propagate myself. What I will have to do at some point is open a file to save myself so that I can be run at a later date. The operating system hosting me (Windows, for example) knows that I've asked to open this file. Now how is the virus scanner on the same computer supposed to know that I'm about to write myself out to that file, instead of being about to write out harmless Microsoft Word data? You can't determine the intent behind the program's request for system accesses -- and therefore you can not make intelligent decisions as to if you should intervene, preventing the request

    --
    you should read everything on the internet as if it had "but I'm probably talking out of my ass" appended to it.
  32. How dare you impose your will on me. by Damek · · Score: 2, Funny

    I like my "fragile biological form", and if I want to live on Mars one day, how dare you suggest you're going to rip it up. As a future citizen of Mars, I regard that as a declaration of war.

    In all seriousness, I have to say I think that is one of the most idiotic ideas I've ever heard. Most people like living in a biosphere. As much as I enjoy the works of Iain Banks, Ken MacLeod and Alastair Reynolds, and one day the universe probably will include many different cultures with body-changing, identity-shifting citizens, shouldn't there also be a place in that future universe for those of us who want to live on the planet of our choosing, in ways not too dissimilar from how humans have lived since the dawn of time?

    If you must, use the asteroids, there's plenty to share. At worst, use a planet with much less chance of being terraformed. But stay away from Mars.

    Frankly, I think you're deluding yourself if you really think technology is advancing so fast that we'll be ripping up Mars before terraforming it. Kurzweil is a prat, and most of what he says is nothing more than wishful thinking.