Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:why? (Score 4, Insightful) 778

Are there still security issues with having JS enabled?

Javascript is used by most malware installation systems. The typical route is that a trustworthy hacked site is modified to include a <script> tag with its source on the malware hosting domain. The resulting script will then use some mechanism to attempt to install malware, either simply dropping an executable download on the visitor and hoping they run it, or attempting to exploit either a browser or a browser plugin bug. Turn off javascript, and the exploit is never downloaded, so can't run.

There are also direct browser attacks that would require javascript to function, e.g. http://www.mozilla.org/security/announce/2013/mfsa2013-53.html or http://www.mozilla.org/security/announce/2013/mfsa2013-46.html (to pick a couple from the last month or two).

So, yes, your system is still less secure if you have JS enabled than if you don't.

Comment Re:Apache doesn't copy-paste code from the kernel (Score 1) 224

The HUGE difference there is that Apache doesn't have code copy-pasted from the kernel.
Themes generally have a lot of code, in some cases most of their code , copied directly from the default theme. That means the theme, the entire theme, is under the GPL.

Well, sure. But not *all* of them.

In a more borderline case, say a small extension that doesn't use any code copied directly from the original project, there is a simple test for "derivative work". You said "Linux build" of Apache. The same source will build and run on FreeBSD or Mac OSX. That strongly suggests it's an independent work from the Linux kernel. On the other hand, a WordPress plugin can only run as part of WordPress. You can't consume compile a WordPress plugin for VBulletin instead. Therefore it's not separate and indrpendent from WordPress.

Ok, but that leaves a few problems. The various binary-only hardware drivers for Linux will only compile and run on a Linux kernel. Are you saying, therefore, that these can't be distributed with Linux without violating the GPL?

Comment Re:Only if the other work doesn't extend the GPL w (Score 1) 224

> a distributor can distribute something that is "the work" alongside (and potentially intermingled with) something that isn't "the work" without causing the two to become mixed

I'm not sure how you can have it "intermingled with" but not "mixed", but les pretend that sentence somehow makes sense.
You pointed to the aggregation clause. You looked at the second half of the sentence, how about the first half of the sentence you point to:

        A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work,

        and which are not combined with it ..

So that applies to "separate and independent works" which are NOT extensions of the original work.
So would that apply to the stuff on http://extensions.joomla.org/ ? Interesting URL, isn't that? Your argument can make sense only if you claim that Joomla extensions aren't extensions of Joomla.

"Mere aggregation" is when two SEPARATE works such as Apache and Firefox are burned to the same disk.

The lines are more blurred than you suggest. What about, say, the Linux kernel and Apache? The latter makes use of the services provided by the former, in much the same way that a plugin for a web application uses services provided by that application, but does that mean Linux builds of it can only be distributed under the terms of the GPL? Most people seem to assume otherwise, and I fail to see the practical distinction between the two cases discussed here.

Comment Re:As the song asks... (Score 1) 358

Some of us are working for startups that demand 80 hours a week of our time and don't have any time left for personal projects.

Is there a reason why the entire stack of line-of-business code created for this startup has to consist entirely of "non-open-source projects"?

Because the owner says so, and I don't have enough influence to convince him otherwise?

Because providing our code to competitors could cause us to lose our competitive edge?

Because there's no point releasing code that wouldn't be useful to anyone other than us?

There are a whole stack of reasons for not open-sourcing business code, which is why 99%+ of businesses never do it.

Comment Re:HTML is a container (Score 1) 224

It applies to derivative works, in the true legal sense of the term "derivative work."

It *also* applies to anything that is combined with GPL code to form "a larger program". This could be interpreted as anything linked (and in GPLv2 this was explicit; GPLv3 is [presumably intentionally] more ambiguous, e.g. to cover interpreted or run-time linked programs).

Comment Re:Quoted the plain text of the license, silly (Score 1) 224

You're missing the effect of the "mere aggregation" clause (the paragraph after 5(d) in GPLv3), which means a distributor can distribute something that is "the work" alongside (and potentially intermingled with) something that isn't "the work" without causing the two to become mixed and without requiring their additional content to be GPL-licensed. The GPL only requires the two to be considered the same work if one is actually derivative of the other. It would be pretty hard to argue that CSS or images are derivative of the original code, IMHO. Javascript less so, but still tricky and could go either way. The question is do they combine to form "a larger program", or are they independent programs communicating over an open channel. The latter is a pretty convincing explanation, so they would be considered an aggregate rather than a single work by the GPL, IMO.

(This is not legal advice. Consult a qualified expert rather than rely on this.)

Comment Re:Is the science repeatable? (Score 2) 69

You have to not only recover it, but to read it as well. And the fine article from the post indicates they were able to actually conduct genetic analysis on it. That pulls the maximum viability date in quite a bit.

Which is why the article you cited goes on to state "[t]he DNA would cease to be readable much earlier — perhaps after roughly 1.5 million years, when the remaining strands would be too short to give meaningful information." Given that 1.5Myear figure, why is 700Kyear surprising? It's not like they're expecting a technological breakthrough to make that 1.5My figure possible: we can already sequence pretty-much any single DNA strand we want, and reconstruction from short fragments is also an existing and thoroughly-developed technology.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...