Re: I don't see a problem.
"The only negative consequence of this technology is the scenario of someone wanting access to content without, you know, paying for it."
So none of the ensuing plugins will have security consequences?
16426 posts • joined 16 Jun 2014
"The W3C, unable to reach agreement on how vulnerability disclosure should be handled, responded with something less than that, offering only voluntary guidelines instead a requirement."
Presumably this means that some DRM vendors will be sensible and some will make life difficult. In due course the latter will get their reward - a reputation for being a cess-pit of malware. Sadly, past experience shows that that won't do them as much harm as one might hope.
"It also happens at other seemingly random times, probably some sort of spam detection."
It happened to me back on the discussion of brickerbot. I eventually came to the conclusion that it was triggered by my mentioning some of the contents of the script. I could only post a very bowdlerised version of my original.
It wasn't helped by the fact that, having entered the captcha the comment was cleared and trying to repost just brought up a fresh captcha.
Cloudflare captchas are obnoxious.
It's one thing promising perfect performance on "business as usual" activities. The problem with that is, accidents aren't business as usual. They're edge cases and that's just what software has always had trouble in handling. And these are not just simple edge cases such as off-by-one that can be tested for. They're going to be "we never saw that coming" events. They're going to be events that require much more processing than normal to deal with an unexpected set of circumstances.
If a designer reckons there might be enough processing power to cope then maybe the "run down the lone pedestrian" option gets hard-coded as a would-be damage limitation short cut. And then that gets triggered by some freak set of circumstances when an accident wasn't threatened and the car goes out of its way to run one down.
Another issue is certification. That's going to be a difficult one to test. Will there be a temptation to code to the test? Remind me, who was it who wrote the code for the VW emission control?
"I wonder if DAFNI will use Virtually Enhanced Logistical Machine Analysis in the project?"
It'll use GIGO.
The water company seem to know more or less where their underground assets are round here. Gas and electricity have been rather puzzled.
Good luck with building a reliable database on that.
I'll see your cess-pits and raise you a pig-farm slurry pit.
There were a series of reports to the RUC that a couple had been killed and buried, the theme being that the bodies were dug up and moved. Nobody really believed it but it couldn't be entirely dismissed. (Have I ever mentioned the golf ball episode?)
Anyway, one of the variations was that the bodies had been dumped in a slurry pit in a pig farm. This had to be pumped out so that it could be examined. Even empty it would be done by the underwater team with dry suits and breathing apparatus.
The pit had been used for dumping carcasses of dead pigs and the pump was quite capable of drawing up and discharging bones. Somebody who was considered able to tell the difference between a pig bone and a human bone but cheaper than a regular pathologist had to spend a couple of days of an Irish winter standing at the outlet of the pump checking what came out. That was me. I suppose I should have been concerned about where the effluent was draining to. I wasn't
The subsequent examination was negative and, I heard, very brief. I didn't see that for myself. I'd already left.
"Back in the day when PC cases were made by Gillette."
I once had the good fortune to have a couple of PCs made by a firm who clearly hadn't got that message. The lids wrapped round to form the sides, were hinged at the back and had stays to hold them open. They were just held shut be a couple of catches - press to release and lift. All PCs should be made that way - at least those intended for IT folk and lab users.
"The bean counters wouldn't stump up for a replacement, so for the next year or so we had to make do with the backup unit which dripped continuously into a large refuse bin that had to be dragged out and emptied every few days."
Just have frequent precautionary shutdowns of any systems the beancounters rely on. After all, it's not good for the business to have no backup - which you don't if the intended backup has become the primary.
"That's the thing with patents, they're so easy to get"
Is it too much to hope that the US patent system collapses under its own weight? Perhaps someone could patent something the USPO depends on* and refuse to license it to them.
That would make it prior art, you say? That seems to have very little to do with it.
"I would shed a tear, but the sooner that bollocks Poettering stops being such a clown and takes his abomination systemd with him the better."
I wouldn't and if he actually did split from the Linux community I wouldn't care whether he continued to be a clown or not. But an upvote for the general sentiment.
"Red Hat. Red Hat controls enough of the commercial enterprise Linux market that nearly everyone's applications have to be compatible with them."
They also still support just about the only enterprise Linux without systemd, RHEL6. So if you want to escape the stranglehold of one of Red Hat's least favoured contributions to Linux you can do so by becoming a Red Hat customer. That's irony or something.
"Universal human rights are a product of Enlightenment"
Magna carta (1215) made such a good start at this that it took about 800 years before May managed to remove the concept of due process. The presumption of innocence didn't actually come from there but was introduced, I think from France, also in medieval times (maybe this is a further reason why May is in favour of Brexit - all these foreigners with inconvenient principles of law).
" People creating things as a hobby who just don't quite 'get' all those older principles us grey hairs used to live by and enterprises"
Poettering isn't doing this as a hobby. AFAIK he's employed by Red Hat and Red Hat is certainly big enough to be classed as an enterprise.
"We talk about, say, RHEL 5 or CentOS 7, but each of these versions has sub-versions and they do fall out of support over time.... Now, there's a difference between applying patches for, say, version 6.2 and updating from 6.2 to 6.3: in-version patches will generally not affect applications, but minor version upgrades have a higher risk. "
I don't know about RHEL and derivatives but for Debian regular patching brings it up to the current version number. e.g:
and yet it started out at 7.0.
Biting the hand that feeds IT © 1998–2019