This package has a long security history, and a currently left-open CVE because the upload of 3.100 did not include closing the active CVE.
If there's a go-ahead from the Security Team (I'm not looking for a code review, just an acknowledgement that they are aware of the requirement for this package, and are fine with its current general state); then I see no issues with this MIR.
This package has a long security history, and a currently left-open CVE because the upload of 3.100 did not include closing the active CVE.
If there's a go-ahead from the Security Team (I'm not looking for a code review, just an acknowledgement that they are aware of the requirement for this package, and are fine with its current general state); then I see no issues with this MIR.