-
Notifications
You must be signed in to change notification settings - Fork 71
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
examples/simpleclient: gives 513 Unrecognized command argument: Invalid key type #83
Comments
I don't devote enough time to this project to be able to debug this at this time. However, if you are able to debug the Tor control protocol and see what it may not like and/or if we're not prepared for some newer/older Tor version, we'd welcome any fixes. |
Any related quick little pointers you have would helpful, thanks. |
We may try building against a newer version of the Tor daemon 👍 . |
I now see in https://github.com/torproject/torspec/blob/main/control-spec.txt --
Looks like a control protocol issue indeed, yay; progress. |
Set |
@cretz Awesome, thank you! We'll try that. |
Here is what I get
|
I think when you create a v3 onion key, you have to use to use |
For me the issue seemed to be occuring while creating the onion service. Changing onion, err := t.Listen(listenCtx, &tor.ListenConf{RemotePorts: []int{80}}) to onion, err := t.Listen(listenCtx, &tor.ListenConf{RemotePorts: []int{80}, Version3: true}) seemed to resolve the issue. |
I am using the example given in the repo, and when I run it I get this error:
The text was updated successfully, but these errors were encountered: