This is a long-term goal that currently has no deadline, as there's no indication of the current "xplus" obfuscation being detected by censors. But there are definitely some new things I'd like to add on top of the current implementation:
Random padding
Replay prevention & detection
Random junk traffic generation (to break flow characteristics)
Before designing and implementing a new obfuscation we need to determine what has historically been used as characteristics for detection in general, how it should be addressed, and whether new attack vectors would be introduced.
This is a long-term goal that currently has no deadline, as there's no indication of the current "xplus" obfuscation being detected by censors. But there are definitely some new things I'd like to add on top of the current implementation:
Before designing and implementing a new obfuscation we need to determine what has historically been used as characteristics for detection in general, how it should be addressed, and whether new attack vectors would be introduced.