Stories
Slash Boxes
Comments

Dev.SN ♥ developers

posted by Dopefish on Monday February 17 2014, @10:00AM   Printer-friendly
from the government-should-mind-their-own-business dept.
mattie_p writes "MIT students won a hackathon last November with a non-functioning demo of Tidbit. The concept is to replace web advertising revenue with a tiny amount of Bitcoin mining on the user's browser. Out of the blue, the students were hit by a subpoena from the New Jersey Attorney General demanding that the founders 'turn over sensitive information including source codes, hosting websites, and all of the Bitcoin wallet addresses associated with Tidbit.'

At first MIT council referred the students to legal assistance from the EFF, who quickly came to their defense. Now there is a petition going around requesting the MIT administration support the students directly. Parallels are being drawn to Aaron Swartz, possibly because one of the authors of the recent petition is Prof. Hal Ableson, although details of the two cases have very little in common.

MIT President Reif has now come out strongly in support of the students--and in favor of academic freedom from interference by government."
 
This discussion has been archived. No new comments can be posted.
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by furiousoyster on Monday February 17 2014, @04:12PM

    by furiousoyster (594) on Monday February 17 2014, @04:12PM (#1026)

    I'm not sure I understand what you mean. The mining scripts under discussion use Javascript and are subject to exactly the same privileges and restrictions that already exist for Javascript in the browser. Tidbit doesn't change what a site can do with your computer at all. Or am I missing something?

  • (Score: 2, Interesting) by cx on Monday February 17 2014, @05:37PM

    by cx (239) on Monday February 17 2014, @05:37PM (#1099)

    Script mine_coins.js might do that at some point in time on a site A. However, that might change. Unless you inspect the script every time you load it, you won't know now, will you?

    So we have a script that does something which has to be communicated back to the site (otherwise how do they get the results of the work). But it might communicate it to another site (cause they use different domain for computation results processing, to 'streamline the process'). Tomorrow it will be upgraded to communicate with multiple other machines (in order to more efficiently process the workload, yadda, yadda). Call me paranoid but that spells botnet to me.

    Now security.
    First, it is easier to hide nefarious stuff in 5 (10? 50?) megs of math heavy code than in a two page straightforward DOM manipulation library.
    Second, even if we consider your machine is protected from rooting/snooping by whatever sandbox the browser of your choice implements, it doesn't protect the rest of the world from actions originating from your machine.
    Third, considering heavy CPU load normal when you browse the net is a great incentive for malicious people to replace legit scripts on servers you access with something else. Today every time my computer slows down for no obvious reason, I go through running processes to find the culprit and then check what that process(es) talk to. But if every site I visit ramps up my CPU load significantly, I will get used to it. Mining bitcoins? Participating in DDOS? Cracking passwords? I wouldn't know unless I check every time.