-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
add support to new version vmess link #516
Conversation
some information can be found at: v2ray/discussion#720
V2rayNG/app/src/main/kotlin/com/v2ray/ang/util/AngConfigManager.kt
Outdated
Show resolved
Hide resolved
} | ||
"quic" -> { | ||
vmess.network = "quic" | ||
vmess.security = queryParam["security"] ?: "none" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently quic security should be put as vmess.requestHost.
This brings a question.. how does the new format carry vmess.securiity?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
现阶段,vmess的security取消,默认auto
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the new format finalised? If not I'd suggest we should add security.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Until now, looks there is no plan for it. And I don't think we should add this feature. Because it can auto negotiation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no matter which encryption has been choosed, client can always connect to server, so I don't think security option is necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That only happens when using the old standard. It's your parser's fault not to work correctly.
The new standard obsoletes this setting, so they are irrelevant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new version scheme has removed the paramter. I think it's viable to user, because of we don't use base64. So that user will understand what's happeded.
some information can be found at: v2ray/discussion#720