There's a contradiction according to the "Heartbleed" fixes between the information in this FAQ and the newest 12.0.1.4104 EBF readme:
From Jason's statement in the FAQ answer:
Affected Versions - note that all platforms are impacted by this issue.
SQL Anywhere 12.0.1 ebf 3994-4085
SQL Anywhere 16.0 ebf 1690-1823
In contrast, the 12.0.1.4104 EBF readme (and the according CR) does name different affected versions:
================(Build #4086 - Engineering Case #761751)================
The OpenSSL vulnerability known as Heartbleed impacted some components of
SQL Anywhere software as follows:
....
Affected Versions (note that all platforms were impacted by the vulnerability):
- SQL Anywhere 12.0.1 builds 3994-4098
- SQL Anywhere 16.0 builds 1690-1880
Question:
Am I right that the EBF information is wrong? - I hope so as there are no 16.0 EBFs available with build numbers beyond 1880...
asked
19 May '14, 03:38
Volker Barth
40.2k●361●550●822
accept rate:
34%
Presumably the 16.0.0.1824 EBF for Windows has the Heartbleed fix. Alas, the associated read-me file does not contain any mention of it (no mention of Engineering Case #761751, no references AT ALL to ANY changes made in build 1824).
I suspect the Evil Prince Haste is to blame :)