7 | | Given that, the way you use to find the cipher names (translation and all that) might also be more elaborate than needed - on the initial reply, we stuff the NCP cipher in {{{o->ciphername}}}. If that value is kept across TLS reconnects (which I cannot answer) we could reduce the patch to "log a comment, and just send the already-set value once again". Loke this - fully untested, just to explain the idea: |
| 7 | Given that, the way you use to find the cipher names (translation and all that) might also be more elaborate than needed - on the initial reply, we stuff the NCP cipher in {{{o->ciphername}}}. If that value is kept across TLS reconnects (which I cannot answer) we could reduce the patch to "log a comment, and just send the already-set value once again". |
| 8 | |
| 9 | Like this - fully untested, just to explain the idea: |