No encryption method for xchacha20-ietf-poly1305 #336
-
|
There is no support for |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
|
@hamzamalikdevgalixo may I ask what server you are using with Outline client? As far as Outline server supports all client side (app) encryptions. Please let me know if you have any suggestions on code snippets that show how this can be added to the SDK. |
Beta Was this translation helpful? Give feedback.
-
|
@hamzamalikdevgalixo are you using xray or singbox on the server side? |
Beta Was this translation helpful? Give feedback.
-
|
We are using |
Beta Was this translation helpful? Give feedback.
-
|
@hamzamalikdevgalixo Looking at the spec, seems like these three crypto are part of the spec: 
https://shadowsocks.org/doc/aead.html May I ask why not use one of the supported encryption methods? Is there any obvious advantage in using |
Beta Was this translation helpful? Give feedback.
-
|
Yes it has support for those but I'm looking for maximum compatibility. I don't want to change the infrastructure setup that's done and its working well in our other platform as well. |
Beta Was this translation helpful? Give feedback.
-
|
@hamzamalikdevgalixo it seems like other shadowsocks implementations are deprecating shadowsocks/shadowsocks-android#2697 Maybe others can chime in and see if it is a good idea to add it to SDK or there is a good reason not to. |
Beta Was this translation helpful? Give feedback.
-
|
xchacha20-ietf-poly1305 seems to be an abandoned IETF proposal: https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha-03 We would like to stick to the standard crypto. Support for alternative ciphers may open up the code to vulnerabilities. I strongly recommend moving away from that cipher in favor for the IETF ones. |
Beta Was this translation helpful? Give feedback.
-
|
ss://Y2hhY2hhMjAtaWV0Zi1wb2x5MTMwNTpzeGdlaXNEcVBYdkhUYWxWbzJ1RW9U@159.89.196.236:33151/?outline=1 |
Beta Was this translation helpful? Give feedback.
-
|
ss://Y2hhY2hhMjAtaWV0Zi1wb2x5MTMwNTpzeGdlaXNEcVBYdkhUYWxWbzJ1RW9U@159.89.196.236:33151/?outline=1 |
Beta Was this translation helpful? Give feedback.
xchacha20-ietf-poly1305 seems to be an abandoned IETF proposal: https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha-03
We would like to stick to the standard crypto. Support for alternative ciphers may open up the code to vulnerabilities. I strongly recommend moving away from that cipher in favor for the IETF ones.