Beep boop - this is a robot. A new show has been posted to TWiT…
What are your thoughts about today’s show? We’d love to hear from you!
Beep boop - this is a robot. A new show has been posted to TWiT…
What are your thoughts about today’s show? We’d love to hear from you!
Leo and Paul were surprised that the Halo Infinite Xbox was going to ship prior to the game release, but that’s pretty common for special edition consoles now.
A few years ago I bought the Super Smash Bros branded Nintendo Switch and the console was delivered about a month before the game release. Nintendo included a download code to get the game once it had been released.
We use Windows Server for terminal services as well. It is much better, when the user interface on the server is the same as the PC they are using as a client.
I just wanted to mention that there is an RTX Remake/Update of Quake 2 already. I think it’s free on Steam as well.
With regard to the PowerBuilder leaked data, it wasn’t a wrongly configured server on Microsoft’s part.
It was the wrong default on new PB apps being published. The Microsoft provided template defaults “open”, AFAIK, meaning anyone can access it, the PB app builder then needs to lock it down to who needs access.
What all of these cloud solutions need to do is default closed, so that nobody has access, then the admin or developer has to explicitly open up access to those that need it.
We see this all the time, with ElastiSearch, Hadoop and dozens of other cloud based databases. They default open, because it is easy and the admin/dev can see straight away, that it works. They think everything is fine, because they don’t know/care about security and the support of the cloud provider gets an easy life, because nobody complains that they can’t access their data.
What they need to do is default closed and force the damned dev or admin to actually work out what the hell they are trying to accomplish! For anything on the web, other than a public web page, its security should always default to as locked down as possible.
The other problem is, these “no code” solutions also mean “developers” with “no idea” of what they are actually doing or what havoc they can cause. Also, given that the whole idea behind PowerBuilder is to circumvent the IT department, there is nobody in the release chain who can sanity check that what the user is doing actually makes sense or that they have taken things like security into account.
Certainly in Europe, if a user used PowerBuilder to produce an app without consulting the Data Protection Officer* at their company, they would be automatically in breach of GDPR and would face, at the least, disciplinary action and could leave the company facing a hefty fine.
(*) The DPO can’t be part of management and shouldn’t be in IT either, it is a separate and serious role, they do not report to the management or board of directors. They can, in fact, actually tell management and the board exactly what they have to do, in order for the company to be compliant with GDPR. They also have to report all incidents they find within 72 hours of discovery to the authorities. This is also why, at least in Germany, they have employment protection - the company can’t fire them whilst they are fulfilling the role; which is usually set to a period of time, commonly 4 years.
In other news, Microsoft did make a huge mistake with their Cosmos DB configuration…
I don’t know how much this sweetens the pot for O365 customers but Microsoft is going to add basic Visio capabilities soon. I’ve looked at Visio many times over the years but could never quite justify the expense, so I am excited to try this out:
MC280285 - In Preview: Microsoft 365 now includes the core functionalities of Visio - The Unofficial M365 Changelog (m365log.com)
Microsoft is threatening to withhold Windows 11 updates if your CPU is old - The Verge
A notable clarification for those that have not seen the news yet. They really don’t like to explain things all at once. It’s always days / weeks / months of piecemeal tidbits.