| Release | Datum | Ondersteund/supported | valid database versions (fully patched/mainstream support) | runtime (fully patched) |
|---|---|---|---|---|
| 4.0.x-SNAPSHOT | ❌ (development) | Current PostgreSQL 13 - 17 + PostGIS 3.5, Oracle 19c/21c/23ai + Spatial, 21 XE, 23ai Free | Java 17, Java 21, Tomcat 9, Docker 27 | |
| 4.0.0 | 15-nov-2024 | ✔️ | PostgreSQL 13 - 17 + PostGIS 3.5, Oracle 19c/21c/23ai + Spatial, 21 XE, 23ai Free | Java 17, Java 21, Tomcat 9, Docker 27 |
| 3.0.2 | 7-feb-2024 | ✔️ (deprecated) | PostgreSQL 12 - 16 + PostGIS 3.4, Oracle 19c/21c + Spatial | Java 11, Tomcat 9, Docker 25 |
| 3.0.1 | 13-jul-2023 | ❌ (superceded) | PostgreSQL 11 - 15 + PostGIS 3.3, Oracle 19c/21c + Spatial | Java 11, Tomcat 9, Docker 24 |
| 3.0.0 | 6-feb-2023 | ❌ (superceded) | PostgreSQL 11 - 15 + PostGIS 3.3, Oracle 19c/21c + Spatial | Java 11, Tomcat 9, Docker 23 |
| 3.0.0-rc1 | 13-jan-2023 | ❌ (superceded) | PostgreSQL 11 - 15 + PostGIS 3.3, Oracle 19c/21c + Spatial | Java 11, Tomcat 9, Docker 23 |
| 2.3.3 | 29-nov-2022 | ❌ | PostgreSQL 11 - 15 + PostGIS 3.3, Oracle 19c/21c + Spatial | Java 11, Tomcat 8.5/9, Docker 20 |
| =< 2.3.2 | 29-sept-2022 | ❌ | PostgreSQL 10 - 14 + PostGIS 3.2, Oracle 19c/21c + Spatial | Java 11, Tomcat 8.5 |
zie ook/see also: https://github.com/B3Partners/brmo/wiki/Systeemeisen
Neem contact op met het team via [email protected] met alle details van het probleem. Indien u beschikt over een Github account geeft u die AUB ook door. Eventueel kunt u een PR maken met een fix van de kwetsbaarheid; gebruik https://github.com/B3Partners/brmo/security/advisories om een private branch te maken.
Wees verantwoordelijk in uw openbaarmaking en probeer te voorkomen dat het probleem wordt onthuld via Github-issues, pull-requests of commit-berichten.
Uw e-mail moet binnen 1 werkdag (maandag-vrijdag) worden bevestigd door het ondersteuningsteam en/of een ontwikkelaar.
Please contact the team by email through [email protected] with all details of the vulnerability, if you have a Github account, please provide that as well. Optionally you can make a PR to provide a fix of the vulnerability; use https://github.com/B3Partners/brmo/security/advisories to create a private branch.
Please be responsible in your disclosure and try to prevent disclosing the problem through Github issues, pull-requests or commit messages.
Your mail should be notified within 1 working day (monday-friday) by the support team and/or a developer.