i checked twisted sourcecode in factory and SP4, neither support
chacha20-poly1305 or etm.

however they implement SSH v2 protocol, so might need the fix in some form but less urgently.

Upstream issue can be found here: https://github.com/twisted/twisted/issues/12057

The relevant part of the upstream ticket is this, I believe (https://github.com/twisted/twisted/issues/12057#issuecomment-1866239542):

> Just a quick comment from my part as one of the authors of the Terrapin paper. We also examined twisted.conch.ssh while compiling our list of implementations for responsible disclosure. While it seems true that you currently don't support the affected cipher modes, it may still be advisable to implement "strict kex" to improve the rigidity of the SSH handshake to avoid possible attacks of a similar kind in the future. The protocol weaknesses are buried deep within the SSH specification but only become exploitable when using newer ciphers. Handling it as a feature request seems fine because it does not affect security.

If I understand this correctly, then it means that we actually do not carry CVE-worthy bug in our packages. If anything, then this could be downgraded to normal RFE, but unless we want to make this change upstream, we should probably leave this to the upstream.

Suggesting WONTFIX.

currently marking as wontfix