Came here to say exactly that.
"Physician, heal thyself".
No other provider I login to has such an annoying captcha system. And, like so many providers, you don't get SAML support without paying for the Enterprise product.
469 posts • joined 17 Apr 2007
SOTAP is the answer to your question
"When it is launched, you will be able to use SOTAP to provide broadband and internet protocol (IP) phone services, because it connects to your exchange infrastructure.
We’re developing SOTAP to help us withdraw Wholesale Line Rental (WLR). We’re planning to launch it UK-wide by August 2022.
It will only be for areas where there aren’t any fibre products available. And it won’t include a managed phone service, or any associated calling and network features."
Indeed. Looks out of my window at the pole-mounted single-phase 11KV-230V transformer feeding half a dozen properties.
Nope, no telemetry there. Now, if I had a SMETS2 smart meter, perhaps they could use that. Oh, hang on, no network here yet. And it would be passing data to my electricity supplier, not the DNO.
Agreed, SIP is a technology with remote intercept capability and other inherent vulns. Especially since SIP over TLS and S/RTP are so very hard (once you've found a provider who can offer it - and I've been there)
But is it.worse than POTS? Pitch up to a street cab or DP with appropriate bits including yellow hi-viz and you'll have hours, if not days, to find the pair you want and listen in.
VM used to make it really easy, having street cabs with the doors flapping in the breeze everywhere, but I hear they've upped their game lately.
PS the existing phone sockets in the UK aren't RJ11, but a unique design chosen solely to prevent unapproved phones being connected. All in the name of preventing bell tinkle when using pulse dialling and electromagnetic bells. Back then even trivial stiff like that was important, let.alome important stuff like the phone working during a power cut. Once this is implemented, I'll have to walk 200m to get mobile coverage to report a power outage to the DNO. (Not really, I have a UPS. But I'm a techy)
If they had their budgeting right, they'd be _speeding up_ the replacement programme.
This is why local authorities have been replacing even comparatively new sodium street lights with LED. The payback period is mind-bogglingly short.
Even led to Kent aborting their "turn street lights of at midnight" programme, to the relief of anyone (but especially females) out after midnight.
Clearly, the specific vulnerability in the article wasn't caused, directly, by the instruction architecture.
But I was following up to a more generic issue over what you do with your system.
And I'd suggest that the vulns of this type (including Spectre,etc.) we're seeing today are, at least in part, thanks to the prevalence of a CISC architecture and the huge system complexity we now find ourselves with as we play whack-a-mole with each performance bottleneck that pops up.
Or whack-an-elephant back in the days of trying to sort out SMP.....
Don't let random people mess with stuff they don't understand.
Chip designers in particular :-) , since this problem has been made much worse by speculative execution and all the other shenanigans to improve performance.
I often wonder where we'd be if VLIW had delivered on its promise of beating both CISC and RISC
A Cabinet Office official told Bloomberg that beta is a standard labelling practice for a digital service that is fully operational. Experienced IT professionals may contest this definition.
What a liar. Alpha is a standard labelling practice in the world of Government service for a digital service that is fully operational. For at least six years.
For that's how long the Dartford Crossing Payments page has been labelled "alpha"
I had a spat on here with an ex-GDS geezer who said "Nothing to do wiv us guv, it's someone else". Even though, of course, it's clearly labelled as a gov service. Apparently the branding isn't the point.
Devs should not care about where their code gets deployed
And this is how we got code that assumes >100Mbps network speed.
And this is how we got code that assumes <5mS RTTs.
And this is how we got code that assumes >32GB of memory available.
And this is how we got code that assumes >32 CPUs available.
It's a great theory, but it doesn't work in practice.
You absolutely DO need to know, at the very least, the constraints that will apply where your code gets deployed. Or it won't work. You can't abstract out of reality (unless you call it Brexit, of course)
Windows XP, how modern :-)
I sorted out a CNC machine tool controlled by a W98 machine a few years back. Might even have been 95, memory fades. Managed to track down a spare mobo and disk drive that were compatible for spares before they became (even more) like hen's teeth.
It also had one of those multi-serial-port cards so beloved of green screens connected to *nix back in those days, used to talk to the various components.
Since Cummings' job advert for arse-lickers, sorry, fellow SPADs, in his blog back in January demonstrated his technical understanding so well, via his description of SQL as an "analytical language", I am quite sure he has the skill to pick the next big tech success.
Or maybe not.
When it _is_ Cloudflare, though, they are exemplary at:
a) putting their hands up
b) Giving a detailed explanation of what went wrong
c) Giving a fully detailed exposition of what they're doing/have done to prevent a recurrence.
No corporate ass-convering by PR droids from them. Like I said, exemplary.
People do their best work when they're supported by those above them in a hierarchy
Indeed. But the problem there is the hierarchical structure. In an effective collaborative environment, one person can have a good old rant about what someone else has done, and as there's good peer relationships, the problem gets resolved and everyone moves on to the next challenge.
It's a (long) while since I even looked at the kernel dev process, but despite an initial appearance from the outside of it being a pyramid with Linus at the top, that wasn't how it worked.
Though quite how systemd got its claws in remains.a mystery to me. Unless RedHat have gone to the dark side......
Beer (OK, Watneys Red) was around 2s 6d a pint when I started drinking in pubs in 1970 (age 15, of course). 12.5p to you.
45 years ago was 1975. Inflation hit 25% in that year alone, 20% the year before.
Some google research indicates 25p a pint in pubs was about right in London in 1978 (which suggests beer price rises were below inflation back then). So, I don't think he was (particularly) being ripped off.
Of course, SU bars were much cheaper back then.
Here, thanks to pubs being closed, our local brewery is putting a barrel outside 2 or 3 times a week, self-serve for £1 a pint in an honesty box (villagers only!!!). Happy days.
You've fallen into the classic misunderstanding of the word "free" in F/OSS, and consequently setup a strawman.
Repeat after me:
"Free as in speech, not free as in beer"
Notwithstanding this being a strawman, I will offer a counter-argument, I can show you numerous cases of a supplier's promises not having due diligence applied to them, and the time and effort (along with at least some of the purchase/licensing costs) being wasted.
I'd also posit that applying full due diligence and fit-for-purpose tests to commercial software is not that different from the costs of considering F/OSS.
Came here to say that. OPNSense doesn't seem to be so well known, am spreading the word to everyone who says they use pfSense, and the general response is "hadn't heard of that ".
The last person was well impressed with the improved GUI.
Because unless you have a professional engineering qualification and undertake CPD, validated by a recognised professional association, you shouldn't have the label "engineer".
Germany is (or at least, was) very, very, very hot on this.
Our lives are as much in engineers' hands as doctors', and woe betide anyone who calls themselves a doctor of medicine when they're not. Should be the same for engineers.
Presumably amongst the divergence that our wonderful UK Government wants from EU regulations, the current Eur Ing recognition will be one we have inflicted on us.
Gosh, if that was an OS you were describing there, you'd be describing SCO Unix.
All its compatibility problems with modern hardware are now addressed by it being only sold to run in a VM.
A VM running in FreeBSD, if you get the whole shebang from XinuOS. Now headquartered in that hotbed of technical advancement, US Virgin Islands.
Agreed with you up to here:
It's like complaining that a file created in unix has the creators username and time attached - where is the privacy!! It even logs atime and mtime!!!
It's nothing like that. The metadata you describe is stored in the inode - the file's low-level directory entry on the filesystem. It's not stored as part of the file, so if it is copied to another system - by email, f'rinstance - that metadata is lost. Well, at least that's true for classic Unix and ext.
That is a world away from metadata embedded in the file, in terms of privacy. And auditability.
God, the VT52, non-ANSI predecessor to the VT100.....
Then there was Newbury Data, who made VDUs affordable. Had a pile of them in the HENP group at Imperial, hooked up to the DecSystem 10 via a DC-10 (not the aeroplane), whose RS232 interface had been created by kludging the current loop TTY interface. Badly.
You brought back memories there.
Ah yes. That option. Was talking to the local Parish Council about my company's plans for FTTH into the village, and the possibility of our providing some public WiFi. One member commented that the lack of mobile coverage, WiFi and (even) decent wired Internet was what attracted some people to the place.
Quick as a flash, I pointed out that there was always the "off" button. Sage nods of agreement all round the room.
Rarely do we see evidence that real UI designers - people with actual understanding of UI theory, doing actual UI research - were involved.
Certainly no such evidence when it comes to the Windows UI. I still want to know what the guys who dreamt up the Ribbon for Office, whilst keeping the rest of the Windows UI as the "traditional" one were smoking.
Coz I ain't going near it.
Biting the hand that feeds IT © 1998–2021