6 ms·
There have been cases in LedgerSMB where we have had to do something like that. The SQL injection fixes in 1.2.0 were too numerous to backport without extensiv
by einhverfr 13y ago
There have been cases in LedgerSMB where we have had to do something like that. The SQL injection fixes in 1.2.0 were too numerous to backport without extensive beta testing, and the new permissions management system in 1.3.0 could not be backported for similar reasons. In both cases, the same workarounds were suggested.
However, those really should be rare cases.
It is worth noting that while we could not backport our anti-CRSF measures to 1.2, we did provide separate fixes to the most severe CRSF vectors (like those which could lead to account takeover).