-
|
Is there a way to bypass this? I'm running code-server over tor so its not possible to get an ssl certificate. edit: tor is encrypted by default by the way, so the connection is secure. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 4 replies
-
|
I'm not familiar with tor but would using i.e. |
Beta Was this translation helpful? Give feedback.
-
|
nope, I get the error info ping server: dial server: failed to WebSocket dial: expected handshake response status code 101 but got 403 probably because the code is ran through tor, some websites block tor by default. |
Beta Was this translation helpful? Give feedback.
-
|
Do things like service workers that normally only work in secure contexts work on .onion sites? If not then I think the error is accurate and we should keep it. If that functionality does work then of course the error is wrong and it seems like we will need to be more sophisticated in our detection. Currently we use |
Beta Was this translation helpful? Give feedback.
-
|
In the first case, at the very least maybe we should reword the error to make it clear the browser has disabled certain APIs that code-server uses rather than saying the domain is insecure, or something like that. |
Beta Was this translation helpful? Give feedback.
-
Well the thing is, tor is end to end encryped. Meaning You run an unsecure site on localhost which is not accessible to the outside. Then you configure a tor service, this will setup a service that will route from tor to the local website (even if its not accessible from the outside) the service uses encryption by default meaning no request ever leaves the local computer without being encryped on the local computer first The encrypted request is routed through tor nodes (when going through the servers, it will get encrypted another 3 times in layers, thats why its called onion routing) each node adds a layer In the end the last tor node sends the request to the tor browser, the tor browser will decrypt the received message, even if the url itsself is http and there is no ssl encryption used, tor by default encrypts the request, I think it uses RSA1024 if I'm not mistaken Situations where the connection is secure: domain ends in .onion Situarions where it is not secure: This means I could enable all the features by using a tor gateway that supports https, which irronically is way less secure since everything could be logged as its completely decrypted on the gateway, and then gets encrypted again with ssl or tls Edit: not sure if this matters but tor does not support udp, I think it routes udp requests over tcp |
Beta Was this translation helpful? Give feedback.
-
|
I think our error is misleading. It makes it sound like your connection is unsafe. What it really means is that secure context APIs like service workers and the clipboard API are not available. We should reword the error! How about something like this:
If Tor does not consider .onion sites a secure context then unfortunately there is nothing we can do. 😢 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, through the browser. Microsoft Edge: open edge://flags/ look for Insecure origins treated as secure. Other option is through code-server vscode settings. |
Beta Was this translation helpful? Give feedback.
-
|
@nexon33 you should use your vscode-server through https. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Version details: |
Beta Was this translation helpful? Give feedback.
-
|
I think so! |
Beta Was this translation helpful? Give feedback.
-
|
open chrome://flags/ search Insecure origins treated as secure turn it on and write down your code-server address restart your browser |
Beta Was this translation helpful? Give feedback.
@nexon33 you should use your vscode-server through https.
you need to go to ~/.config/code-server/config.yaml, and fix your file just like below:
bind-addr: ****
auth: password
password: ***88
cert: true(It's very very very important here,it needs your .key ,.crt or others to supprot the function) )
cert-host: ***