TLSv1.3 makes TLS Miscreant-in-the-Middle (MITM) efforts harder, and that difficulty will likely only increase. The reported cert validity is way too long, too. That should be a year, at most. Best either code your app to mirror its own traffic, or maybe migrate your HTTPS traffic over to Mitmproxy and use that. Based on what is reported here, I'd suspect that the MITM might also be downgrading some TLS connections.

Load new vendor drivers (latest from HP are from October 2021), try switching to and using the AirPrint path (which eliminates add-on drivers, accessing drivers embedded within the printer itself), and failing that remove and reset the printing subsystem and re-add the printer, same as usual sequence for troubleshooting printing problems. And yes, ASC is a better spot for this. These developer forums would be where printer driver developers would seek help with their drivers or with developing other apps, for instance.

This isn't the best spot for Private Relay discussions—this forum is for app developers to discuss technical issues within their apps with the Apple app development support folks, or how to implement apps for specific purposes. If you're not working on an app and its source code or such, the Apple Support Community forums are a better place for the questions. Here's an intro to Private Relay: https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay iCloud+ Private Relay suppresses website access to the originating IP address. Some websites try to use that originating IP for user tracking, or for other purposes including fraud prevention and DDoS protection and for managing geo-restricted content, among others. Those websites can potentially get tangled and block access. Private Relay targets the shuffling of IP addresses of HTTPS-related protocols, and does not effect DNS translations. I would not expect a "DNS blockage" here, either. (Whatever that is.) DNS either gets translations, or it doesn't. If it doesn't, the user usually gets 30-second pauses inserted, and no connectivity. But then I've also met some very dumb and very buggy routers, too. While you're accessing your router, access its firmware and update that firmware from the vendor if newer is available, as generic advice.

Apple states not: "...if your app provides a network extension to add VPN or app-proxying capabilities, your extension won't use Private Relay and neither will app traffic that uses your extension."

The C compiler standard library being selected on your Mac is a locally-installed gcc 11.2.0 version, and the installed version is not compatible with the macOS version you're using. Based on what's posted, upgrade macOS to 11.3, or re-link that locally-installed library (likely homebrew) for 11.0, or maybe switch to the clang tools and libraries.

Apple may or may not see enhancement suggestions here. Best to log your feedback with Apple.

Per Apple: How to get old versions of macOS. This covers versions from the last ~seven years. As for testing the older installers, you'll have to test them without newer software around, and/or test them using a bootable drive and createinstallmedia. The Mac involved can need to support the macOS or OS X version you are testing with, too. The usual workaround for a busted certificate in an old installer is to manually set the system time back to when the version just was released, launch the installer and stop at the first prompt, switch back to system preferences and re-set the time to current.

Boot into Safe Mode, and try again. Failing that, contact Adobe Support.

macOS has never had a downgrade feature. Your ugly options: Restore your backup from prior to macOS 12.0.1 and revert your system and its contents to prior to the 12.0.1 update, or maybe you can wipe and reload a new macOS 12.0.0 copy of and migrate from 12.0.1, or wipe and reinstall and manually copy over files and data. Check whether the printer supports AirPrint and switch to that. Failing that, look for the driver directly from HP. Failing that, I'd then replace the printer before ever trying a downgrade. And if I replaced the printer, I'd look for printers with some specific features (including AirPrint) to avoid needing drivers. This question is also best asked over in the ASC Monterey forum. The developer forums are intended for the third-party app developers that are working on third-party apps. Apps such as printer drivers.

Proving a negative is... difficult. There are myriad ways to go wrong with data encryption. One common mistake is using encryption for certain data, where a cryptographic hash would be more appropriate. Claiming data security can involve open-sourcing at least some of the storage-related details if not the related code (and also allowing reverse-engineering for the related area), or can involve the performance of an outside audit. Even then, it's still exceedingly difficult to prove that no backdoors exist, and that critical members of technical staff are not themselves compromised. It's also seldom a vulnerability in the encryption itself that's targeted—AES and TLS and Argon2 are decently secure—it's usually something around the encryption or key management that's targeted. Or the people. Upgrading to newer encryption or newer hashes tends to be an interesting discussion for developers too, and one that some apps are ill-prepared for. With third-party password managers, arguably the biggest problems folks have had have involved apps that vaporized.

Here's some general reading: https://developer.apple.com/documentation/network/building_a_custom_peer-to-peer_protocol Here's the Apple analog to Wi-Fi direct, if you want to try that: https://developer.apple.com/documentation/multipeerconnectivity Swift streams, which is a step up from BSD sockets: https://developer.apple.com/forums/thread/35636

Check for any available update, then contact Microsoft Mojang Minecraft support.

Maybe you want: https://developer.apple.com/documentation/security/keychain_services

Remove it. I'd request a refund from the vendor. I'd also use the built-in anti-malware. Some related reading: Effective defenses against malware and other threats Most of the messes folks get into with macOS are not going to be prevented by add-on anti-malware; problems around poor and reused passwords, failure to use two-factor authentication, phishing, installing the adware or the questionable apps, etc. And yes, it's best to ask these app-support questions of the app vendor (Norton), or over in ASC, as these developer forums would be where (for instance) the Norton 360 app developers might seek assistance with the problems seemingly present in this app, or for other developers with their respective apps.

You will want to check for and apply any available YouTube app update from Google. If any available update does not resolve this issue, you will want to log a bug report with Google, as they may or may not see bug reports in their app posted here.