-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Historic IP addresses included in invites are rendered invalid by omitting the last digit of the port #136
Comments
I cannot reproduce it. Can it be that you are missing the = at the end? |
@csoler Thank you for looking into this. By the way, thank you for your hard work on this excellent project. Please find below two invites generated with 0.6.7 on Ubuntu 22.04, first in the "new" format (showing the bug), then in the "old" format (correct port numbers). I also attached screenshots of the IP addresses of the exporting node, then after importing the invite (generated with the the new format) into another node (also 0.6.7 on Ubuntu 22.04). I hope that helps to reproduce the issue. Best regards New FormatABCL3ecZDHNZ0z7r1v1tvu18AxTCKsSx8Phq8u67TYXmB9qk1D/l3gEJQ2hyaXNjaGFuAhhpcHY0Oi8vMTkyLjE2OC4xNDQuMTo0 Old FormatCQEGAcGaxsBNBFXda74BCACwg6yWrFGX2YYFM3Ozf8OKN4c5z9A09YM1fD6HM+Xx |
Fixed in PR 138 |
Using the new certificate format, IP addresses included in an invite are rendered invalid by omitting the last digit of the port.
Reproduce
Create an invite that includes the complete IP address history. Add this friend in another instance or use a Base64 decoder to look into the invite. Observe that the last digit of the port is missing, i.e. 3ipv6://[2103:c7:9720:d377:165d:efb4:d504:d25e]:420 when port "4200" was used.
Workaround
Use the "old certificate format". In this case, ports are properly included
The text was updated successfully, but these errors were encountered: