Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Supporting ngrok's authtoken argument #67

Closed
Anon-Exploiter opened this issue Oct 23, 2020 · 2 comments
Closed

Supporting ngrok's authtoken argument #67

Anon-Exploiter opened this issue Oct 23, 2020 · 2 comments

Comments

@Anon-Exploiter
Copy link
Contributor

(ngrok only)Then the message that ask you to copy & paste tunnel authtoken of ngrok will appear. Login to ngrok, click Auth on left side menu, click Copy, return to Google Colaboratory, paste it to the text box under the message and push enter key.
ngrok token must be kept secret. I understand people hate copy & pasting ngrok token everytime they use remocolab, but I don't know how to skip it without risking a security. If you could specify ngrok token to remocolab.setupSSHD() or remocolab.setupVNC(), you can save ngrok token to a notebook. Then, you might forget that your notebook contains it and share the notebook.

Even though it's written in the documentation that by intention you haven't allowed any argument to hard code the authentication key. I'm not sure anyone would be sharing this but regardless of that maybe add a disclaimer or something in bold?

Really need the argument, right now have added my key as a comment and copy-paste from there, I'd normally fork your repo and use that version but would like to stay up-to-date.

Would appreciate if you could add such an argument.

@Anon-Exploiter
Copy link
Contributor Author

Looking at #10, guess it won't be implemented.

@demotomohiro
Copy link
Owner

If you use Argo Tunnel instead of ngrok, you don't need to copy-paste authtoken.
I wrote how to use remocolab with it on README.md.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants