Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:I agree (Score 2) 312

Again, if I have a PDF with DRM in it

As the doctor in the joke said, "then don't do that". First, buying DRMed content is unethical - you're contributing to the problem. Second, if you happen to run across some PDF with DRM, you can probably take it out and shoot it using a Calibre plugin.

You have to run your e-book in some piece of software and unless you're willing to write your own e-reader you can assume that it's disposable content.

There are many Free Software PDF and ebook readers which have no DRM capabilities. I use Zathura, for example.

But anything you can do with software you can do to your digital content, even something as mundane as deleting it.

Again, that shows a remarkable lack of understanding of computer security, particularly the notion of privileges. My browser can read /etc/hosts, but can't delete it, even though "software" as a whole can. That's because I don't give it permissions to do so. Similarly, you can also not give your PDF and ebook readers permission to delete the file.

Besides, even if that wasn't true, it's anything you can do *with software*. But why exactly are you limited to that? Try this: copy the file to an USB drive, unplug it, and then run the PDF reader. Hard to delete that, innit?

Comment Re:Better, but still worthless (Score 1) 217

Your average CCTV camera has a lower resolution than a 30 year old camcorder, and while there are attempts to bring the resolution up currently there is neither the bandwidth, storage, or processing power to capture/process all of that data cheaply enough to be widely distributed.

Sure there is, if instead of trying to stream high-def video to the mothership, the feed is processed on the spot and only the digested information (e.g., iris hashes) is sent.

Comment Re:Seize wallet or real coints? (Score 1) 198

As the sibling post said, they don't. But unlike cash, Bitcoin are extremely divisible (you can send 0.00000001 BTC to someone), so the same practical problems (not having enough coins and bills to pay for things) don't really apply.

There are economic consequences of having a fixed supply, of course, but that's a different issue.

Comment Re:lol (Score 1) 219

Now I'll grant you that a malicious extension could modify a link somewhere that causes *my* JavaScript code to do something on behalf of the user, but even in that case, the risk is no greater than it would be with cookies.

Well, if you used cookies, you could set them as HttpOnly, which would prevent even your JavaScript code from accessing them.

That said, I was thinking more about that scheme vis-a-vis using HTTPS, and in particular in the case of a man-in-the-middle attack. The problem with JS crypto is that you can't securely deliver the code to the browser, so all bets are off if you have an attacker that can modify the stream.

Slashdot Top Deals

There are two ways to write error-free programs; only the third one works.

Working...