How to Contribute to Airship, Even If You're Not a Security Expert
If you believe in our mission to make online publishing safer for everyone, you may have considered contributing to CMS Airship already. Whether you share our desire to see data breaches become less frequent or you seek some open source work to put on your resume to improve your employment prospects, there are a myriad of ways to get involved. We greatly welcome anything you feel you can contribute.
What follows are some things we'd specifically ask for if given a choice.
CMS Airship Version 1.3.0 Released
CMS Airship Version 1.2.0 Released
CMS Airship < 1.1.2 - Stored XSS Post-Mortem
Earlier today, a stored XSS vulnerability was reported by Lucas Reschke and fixed in version 1.1.2. Unfortunately, this news arrived at the same time as I discovered the auto-updater was refusing to run. If you've set up your own Airship already, you'll need to manually update to the latest version (
CMS Airship Version 1.1.0 is out! Get it while it's hot. If you've enabled
minor updates in your Bridge, this update should be applied automatically.
When we released version 1.0 earlier this week, we weren't counting on receiving as much great feedback from the community, and we certainly didn't expect anyone to contribute significantly enough to tag 1.1 so soon. I'm delighted to say, our expectations weren't high enough.
Let's dive into what's changed in version 1.1.0: