It is recommended to keep your copy of CloudLink up-to-date for improved security, performance, and stability.
| Version number | Supported? | Note |
|---|---|---|
| 0.1.0 | 🟢 Yes | Latest version. |
| S4.1 | 🟡 Partial | Legacy support. |
| S4.0 | 🟡 Partial | Legacy support. |
| B3.0 | 🔴 No | End of life. |
| S2.2 | 🔴 No | End of life. |
| S2.1 | 🔴 No | End of life. |
| S2.0 | 🔴 No | End of life. |
| S1.1 | 🔴 No | End of life. |
| S1.0 | 🔴 No | End of life. |
Special exceptions are given to Meower-specific builds of CloudLink. They will be maintained as long as Meower supports APIv0 or the CloudLink protocol.
You are to keep your instance of Cloudlink as up-to-date as possible. You are to assume that support can be discontinued at any time, with or without reason.
| Version number | Supported? | Note |
|---|---|---|
| 0.2.0 | 🟢 Yes | Latest version. |
| 0.1.9.x | 🔴 No | CL4 Optimized. EOL. |
| 0.1.8.x | 🔴 No | Pre-CL4 optimized. EOL. |
| 0.1.7.x and older | 🔴 No | CL3/CL Legacy - EOL. |
Public server hosts should maintain the latest version. If a public server host has been found to be running on a Deprecated release, or a version that has not been upgraded in over 30 days, your public host will be removed from the public server list and you will be notified to update your server.
In the event that a vulnerability has been found, please use the following format to report said vulnerability:
- A title of the vulnerability - Should be less than 20 words
- A description of the vulnerability - Describe the vulnerability in as much detail as possible. Should be no larger than two paragraphs.
- Steps to reproduce the vulnerability - Brevity is desired.
- Scope of the vulnerability - Does the vulnerability allow a hacker to gain access to a remote machine? Does the vulnerability compromise users in any way, shape, or form?
- Initial severity assessment - Range from Low, Medium, High or Critical
- Any other comments/concerns