-
Notifications
You must be signed in to change notification settings - Fork 599
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
ERROR: Unknown hidden service type #162
Comments
This happen because you are using a V3 .onion address that is 56 char long instead of 16... Change this line --> matched, _ := regexp.MatchString( basically just add ",56" near the 16 so it will match all the length from 16 to 56... rebuild the project eg $ go install github.com/s-rah/onionscan and try again.. now it should work.. Notice that this is a quick fix only, since it match ANY the address FROM 16 To 56 chars length. A better fix should match ONLY 16 or 56 length.. |
The suggested fix doesn't work. I even tried replacing the entire validation function so that it would always return true |
That is strange.. Are you sure you are recompiling the code? Try to add a print statement inside the validation function and see if the new line get printed when you execute the application.. |
I tried to add a message and compile with |
What does not work? Do you see your new line printed? If you still get the message error message but you are not seeing validation print statement, try to add a new print statement in the beginning of the code, and see if that gets printed. |
For me, making the suggested edit solves the issue. I have tested by running the source directly and by (re)compiling. It seems like this should be supported. Has someone already make a PR? ... Last commit was 3 years ago. Is this still being maintained? |
There are already several PR trying to fix this issue. In some of them i even suggest a better way to handle it like in this: But I do not think this project is maintained anymore. |
Thank you this worked for me |
This solution doesnt work ERROR: Change this line --> matched, _ := regexp.MatchString((^|.)[a-z2-7]{16}.onion$, identifier) |
ERROR: Unknown hidden service type: some suggestion |
Tried the solution and my own code. Neither seems to work. I also compiled it with go build and tried it as well not just go run. Didn't make a difference. v2 Adresses work. Strangely enough, even when changing both returns to true not matter what, it is STILL unknown service.... weird
|
So i figured it out. I solved it by doing
Then in
Now it uses my code instead of the "old" version. Cheers |
Other than what he said, I had to replace the old import dependencies in main.go file, in few word I replaced:
with the edited ones, for istance:
|
Can't get this to work. Somewhere in the orig code it only wants to build from the /s-rah/ repository and completely ignores changes I push to my forked repository. Everything is there in my fork, local/remote syncd, but the "go build" just always recompiles /s-rah/ code... Where is the secret switch to enable editing and recompiling? Sorry, I'm a complete "go" newb, and a low-level githubber too. Can anyone help? |
Anyone looking for an onionscan version that works with v3 addresses (or trying to add support) feel free to checkout my repo. I've also added ci for automated releases. Basically, Use grep and sed to replace all s-rah/onionscan module imports to your Github repo. Run this in a bash shell (git bash for windows works too) grep -Rrl 'cypherpunksamurai\/onionscan' ./ | xargs sed -Ei 's/cypherpunksamurai\/onionscan/CypherpunkSamurai\/onionscan/g' |
This was very helpful - but I needed to change all references to match my local module |
If I do sudo $GOPATH/bin/onionscan facebookcorewwwi.onion the program runs ok, as it does with other existing onion sites. But when I run my own onion site that i can view ok from the Tor browser(from a different device and network) and I run onionscan on it i get ERROR: Unknown hidden service type. Would this be because I haven't published my onion site anywhere? Any advice would be appreciated.
The text was updated successfully, but these errors were encountered: