Slashdot Mirror


User: emaveneau

emaveneau's activity in the archive.

Stories
0
Comments
27
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 27

  1. Trusting distributed clients on Distributed Computing Program Hidden in Kazaa · · Score: 1
    Core65.exe which is auto-downloaded by Folding@Home's Linux client also has a surprise. Try "strings Core65.exe | grep NSA", and you'll get 458 word rant starting with
    "Why shouldn't I work for the NSA? That's a tough one. But I'll take a shot. Say I'm working at the NSA, and somebody puts a code on my desk..."
    Apparently it is just some quote from "Goodwill hunting" which Folding@home picked up by statically linking with some library. But it'd be prudent to chroot all distributed clients and all net connected services.
  2. Re:this is a serios problem on Beware Employment Contracts · · Score: 2
    By default your employer owns everything which is within the scope of employment, which means
    • if it is the kind of work the employee is paid to perform,
    • occurs substantially within work hours at the work place, and
    • is performed, at least in part, to serve the employer.
    Not all have conditions have to be met, 2/3 is enough. e.g. Miller v. CP Chemicals Inc., F.Supp. 1238 (D.S.C. 1992)

    Miller was a supervisor who worked at CP Chemical's quality control lab. He created a program for making computations necessary for in-process adjustments to one of CP's products. Miller was paid by the hour and created the program primarily at home on his own computer during off hours, and without any overtime pay. Nevertheless, the court held that the program was created within the scope of Miller's employment and was therefore owned by CP Chemicas, not Miller. The first and third factors favored CP, while only the second favored Miller. [Software development: a legal guide, Stephen Fishman, Nolo Press]

    So your Mona Lisa and book are safe unless you have brain dead representation and cannot prove the third factor in your favor.

    Now if you make your exhaust system for your own car you're safe, but if the exhaust system is meant to help your employer (say a NASCAR team), then it's theirs.

    IANAL, I'm stretching software case history to apply to other fields, but for software IP ownership this should be spot on.