Re: One word:
"I've seen backups that IT didn't know how to restore"
If it isn't tested it isn't a backup.
40432 publicly visible posts • joined 16 Jun 2014
"I have never worked with pipeline systems, but my guess would be that their is some need to extract billing and operating data from the product delivery system and probably some need to input some commands at times. So a completely separate system might be difficult/impractical/impossible"
That pipeline has been in operation for longer than an internet-based control system seems feasible. It has been proven to be operable without exposure to the net. It has now been proven to be inoperable with exposure to the net.
We can, then, eliminate impossible and impractical. Difficult, maybe. Probably an option you left out - inconvenient. But far better than what they've got now.
"probably kind of expensive and not all that reliable"
But not too bad compared with the current situation. Apart from anything else, where do you magic up all those road tankers when you need them? And if you succeed, where do you magic up the tankers to replace whatever it was they were doing before?
The one email address I have that receives frequent spam - which gets reported - is an old Hotmail address. Apart from SEO and the like service offerings* the phishing spam it receives is almost entirely pretending to be from one of the numerous Microsoft email brands. A check in the server spam folder shows that almost all other phishing spam such as advance payment scams is trapped and virtually none of the fake Microsoft mail is trapped. I'd have thought that there should be sufficient reports for NCSC to start having a quiet word with Microsoft to tighten up.
NCSC need to have words with their own marketing department. Earlier this year the responses to reports started including links to their own puffery making them look just like phishing emails. The link in TFA to the report is non-functional with JavaScript blocked. Given the point made in the report about JavaScript framework poisoning they really should know better than to (a) depend on JavaScript so heavily on their own site and (b) send out emails pointing to it.
* These generally get a response pretending to be a supplier questionnaire designed to suck them in before gently leading them to the conclusion that they've paid good money for a crap spam list.
"there's a good change the government is going to come and have a word with you."
As HMRC is one of the frequent sites spoofed I look forward to Namecheap, its management and board being subject to frequent and searching audits by them.
"it would make more sense for companies to just fix the bugs themselves and then commit them back to the project ... Often a company's employment contract will insist that it has complete ownership over all intellectual property that an employee creates."
There's absolutely nothing in the second part of that that stops the company committing back to the project. The company owns the IP and can do with it as it wishes.
There could, however, be a problem with companies who claim IP ownership of what employees do in their own time.
"If an open source maintainer gives up because it's not fun and not worth their time, there's little you can do other than fork it."
And the ability to do that is because it's open source. I remember looking at the description of some S/W, thought it might be useful to the business I worked for and then the company that wrote it got bought up by Microsoft and that was the last I ever heard of the product.
I'm reminded of the situation where we had some commercial source code but not enough to compile the full application. After having the second Friday lunchtime interrupted by a bug in a weekly program run I spent the afternoon working through the code to find the bug. Even after reporting it to them, including how to fix it, it took a few weeks before we got the revised binary. I wouldn't be surprised if the same dodgy coding practices were hidden in more of their programs.
"QCs make a lot of money"
A colleague bought a house previously occupied b a QC & said they kept getting debt chasing letters for him. However both he & I were in a position to observe QCs at work and we both knew who he was, I wouldn't have rated him as one of the more able ones.
The much maligned Imperial system of weights and measures had little islands of binary sanity. Apart from ha'pennies and farthings in currency there were pounds and ounces (binary ratios are particularly suitable for weighing) and stones, quarters and hundredweights. It was just the bridge between pounds and stones which was irrational.
"The legacy copper network has proven particularly expensive to maintain as the cables and telephone poles used are exposed to the elements, and thus susceptible to weather damage."
My telephone connection is entirely underground except for the green footway boxes connecting bits of underground cables together. My neighbours' connections are all strung from posts for the last few 10s of metres. If/when fibre connections replace them are made my guess is that all of them, including mine, will be overhead.
The question to ask is why do these bastards want a password? If it's to protect my interests then I'll use a random string of characters and let KeePass do the heavy lifting. If it's for some arcane purposes of their own (hello iPlayer BBC Sounds) it gets Passw0rd1 or something appropriate.
"Here's a suggestion to ISPs: supply non-configurable routers."
I'm not happy with that idea. My ISP in effect did that. They "upgraded" remotely and took away my ability to run admin level. They've frozen me out of being able to make changes to the DHCP settings I had in place. I suppose the best thing would be to replace it but then it's a matter of finding smething that's neither a load of cack nor over-priced. In my case overpriced would include paying for an included wireless access point as the location of the master socket isn't the best place to get a good signal out.