Update Supported Platforms article for Fall of 2023 #2925
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some additional notes on the testing to provide context for what went into the article updates:
The loaner Brim MacBook that I've traditionally used for testing that Zui still runs on super old macOS releases won't even install Big Sur (macOS 11) anymore. I have every reason to assume Zui still runs on there, but I don't feel confident claiming it does unless I can repro issues on it in a pinch. Based on my web searches, Apple's support for Big Sur may be wrapping up right about now anyway, so I figure it's no big loss.
I definitely saw Zui work on Windows 8.1 in the past, but for whatever reason this time went I went to repeat the smoke test I couldn't get Wireshark to work. That's when I noticed that Microsoft has officially announced EOS on Windows 8.1 overall, so I was happy to drop mention of it entirely.
For all the old Linux releases I'm not claiming to support anymore, the root cause is the same: A GLIBC that the Suricata artifact wants that isn't there. No doubt someone could surgically add the correct one by hand but I don't wanna be officially supporting surgeries, so I'm happy to have our oldest supported versions be ones that lack that problem out-of-the-box.
In addition to binary searching to confirm the oldest releases that still passed smoke testing, I also did smoke tests with the most recently available versions just to be sure. I don't care to include all this detail in the article, but in case I ever need to refer back to it, here's a list of which ones I tested and which worked ok. (Now that I'm writing this I realize I didn't hit Windows 11. I happened to spin up a Windows 11 VM on Azure a few days ago when repro'ing a user issue and of course the app worked fine for general operations. I unfortunately didn't happen to test with pcaps at the time, but Windows 11 has been around long enough that if it was busted I expect we'd have heard about it by now.)
Closes #2906