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!
We really loved the YT Live chat!
Interesting that Steve didn’t mention the Microsoft MSMQ CVE (2024-30080), which is far worse than the Wi-Fi bug - this is a true remote execution bug and Microsoft are advising everybody to patch against this as it will most likely be exploited within the next 30 days.
Also:
CVE-2023-50868 – MITRE: CVE-2023-50868 NSEC3 closest encloser proof can exhaust CPU
This is an advisory-only CVE, issued by MITRE and of concern to the industry at large, not only Microsoft. It covers a publicly disclosed issue with DNSSEC and how it proves the non-existence of a specified zone. (Unfamiliar with the details of DNSSEC, or perplexed as to how an NSEC record can prove a negative? The DNS Institute has a delightfully readable story that explains it.) The bug in question is an important-severity denial-of-service issue; it’s not thought to be under exploit in the wild, but it’s DNS and therefore worth your time.
What did you all think of the production quality?
I know we over-compressed the audio so that I sound like I have emphysema. We’re fixing that.
I dislike the sliding transitions. Right now Restream doesn’t have an alternative but we’re asking them for dissolve and cut which is what we use now.
I really liked the ability to include chat comments - it threw Steve at first but he learned to ignore them.
Lower thirds were pretty sparse but I think that’s probably more modern anyway and certainly sufficient for their purpose.
We’re leaning toward using Restream in all production once we close the studio. It’s easy for us to use and serves most of our needs. It does use WebRTC as the protocol and Alex Lindsay has severe reservations about that, but it seemed ok to me (except for a few hits here and there).
The Untitled Linux Show has been using it for a while now.
Thoughts?
3 Likes
I wasn’t paying close enough attention or realize you would like me to take notes of the quality, but given I cannot recall (pun not intended) anything that stands out. So quality was likely sufficient.
But that’s not the reason I am taking time to leave feedback. Am I the only one who sees the insurmountable problem with Recall? Even if it is stored on your computer and properly encrypted, your computer can be subject of a search warrant (and probably discovery in civil cases, but I am not a lawyers, so let’s stick to criminal searches)! Even if you are innocent of the alleged crime that lead to the search warrant, a search of Recall could dredge up evidence of some crime that could lead to your arrest and prosecution. While talking about politics is gravely frowned upon, even politicians in the United States are staying they would engage in vindictive prosecution if they are given the chance.
I will not willingly own a computer with Recall, let alone choose to let it run, because the legal liability vastly outweigh any minute benefit the feature claims to offer. With the state of local, federal, and global politics, this “feature” is not worth having and, while this is nothing more than speculation, there is reason to believe its being offered to incriminate end users on behalf of governments (and other prying bad actors, eg employers who want to track everything their workers do). Why shouldn’t people not believe that it wasn’t “big brother” who wanted what amounts to a complete and thorough key logger installed on every computer?
PS I do not know if that last sentence is grammatically correct, but the message should still come through.
PPS And I could even envision scenarios where someone would want to run malware on a target’s computer(s) to run malicious script to do something criminal so it appears the target engaged in unlawful activity. What happens if someone runs a script when it’s reasonable for them to suspect you are sleeping to make it look like you’re researching method and ways to commit crimes? That activity could get saved to your timeline and you may not even know it ever happen. However, the activity was logged by your computer, so by all accounts, it was you who did it.
I’m not an audio engineer, but it doesn’t just sound like over-compression, the EQ is also different. It sounds like early Skype audio, not even how Zoom sounds.
You can hear a clear difference between both episodes, even if you don’t know which one is which.
Restream doesn’t seem to be aimed at podcasters. Have you considered services that record audio and video locally such as Riverside, Squadcast or Zencastr?
2 Likes
In this episode I really noticed regular gaspy breath sounds from both hosts, like they were trying to talk too long before taking a breath. That’s what you meant by the reference to emphysema? It stressed me out enough that I stopped listening closely. I really would have difficulty listening to shows if they were like that all the time.
3 Likes
Are these bugs on all wintel OS, server too or just the clients? Steve sort of dismissed Windows as ‘for doing Excel’ when he was saying Windows is fundamentally insecure, but it’s used for an awful lot of very critical infrastructure globally - although air-gapped and not using the WiFi stack at all I hope.
1 Like
MSMQ isn’t installed as standard, but it can be installed on Windows 10/11, although it is generally more of a server side feature.
The “breathy” sound was immediately annoying to me too and I had difficulty following the content. As @Leo stated, this was very much likely due to overcompressing, possibly even with the stereo channels separated, because I also felt that the voices wandered a bit off the center at times.
Having listened to the latest episode, I did not get tripped again, so I consider it fixed now.
2 Likes
Besides the compression, I also noticed quite severe echo at times, especially when Steve was speaking, in the #979 “Angle of the Dangle” episode. It seems to be fixed in the latest show, though.
They seem to be using the studio with the Tricaster again for the latest episode, so no, the issue with restream wasn’t fixed.
1 Like
Oh no, but at least they seem to be aware how severe it is. I am only listening to the audio, never watch the video, so the sound is the only thing I am concerned with.
1 Like
It was a production error and not due to Restream. We’re working on our audio chain so that when we move out of the studio you’ll get the best possible audio - and no heavy breathing. I apologize!
3 Likes