Uh oh!
There was an error while loading. Please reload this page.
Document how to use GH in the ring with 2FA. - #115
Conversation
0b4b297 to
50e09beCompare
mrakitin
left a comment
There was a problem hiding this comment.
I suggested some improvements of the text to avoid a possible leak of the token in a plain text form.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Revisions from @mrakitin Co-Authored-By: Maksim Rakitin <mrakitin@users.noreply.github.com>
mrakitin
left a comment
There was a problem hiding this comment.
Here is a couple of corrections. Otherwise looks good.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| $ git remote set-url <NAME> <NEW_URL> | ||
| For use inside the ring, connecting via SSH does not work. (Consult ITC to ask |
There was a problem hiding this comment.
Not sure if this is intended?
| For use inside the ring, connecting via SSH does not work. (Consult ITC to ask | |
| For users inside the ring, connecting via SSH does not work. (Consult ITC to ask |
There was a problem hiding this comment.
Fair question. I meant "use". Maybe it could be phrase more clearly?
There was a problem hiding this comment.
No, don't put users inside the ring, it's not safe there 🤣.
Maybe we can better say "For use in the controls network ..."?
Uh oh!
There was an error while loading. Please reload this page.
cowanml
commented
Jul 5, 2019
via email
In source/components/github.rst: ...
- For use inside the ring, connecting via SSH does not work. (Consult ITC to ask
- why.) Your best option is to use a personal access token, which you can do at
+ For use inside the ring:
+ * put the following in ~/.ssh/config:
+ Host github.com
+ ProxyCommand ssh -W %h:%p ssh01
+ User [your-github-username] (this line is an optional convenience)
+ * or set the GIT_SSH env var to ``'ssh -o "ProxyCommand ssh -W %h:%p ssh01"'`` in
+ your shell setup (eg. for bash, ``export GIT_SSH='ssh -o "ProxyCommand ssh -W %h:%p ssh01"'`` in your .bashrc)
+ * or just ``GIT_SSH='ssh -o "ProxyCommand ssh -W %h:%p ssh01"' git [whatever]``
+ * or you could use a personal access token, which you can do at …-matt |
tacaswell
commented
Jul 6, 2019
Won't this push all ssh traffic, including to other machines on the floor through the proxy? |
cowanml
commented
Jul 6, 2019
via email
doh! yup, scrub that one. …On Sat, 6 Jul 2019, Thomas A Caswell wrote:
export GIT_SSH='ssh -o "ProxyCommand ssh -W %h:%p ssh01
Won't this push all ssh traffic, including to other machines on the floor through the proxy?
?
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute thethread.[ABJZ7Y6FOUIEPFG4YNJJMFLP572J7A5CNFSM4H6NNUFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVX
HJKTDN5WW2ZLOORPWSZGODZKQKFI.gif]
|
Co-Authored-By: Maksim Rakitin <mrakitin@users.noreply.github.com>
No description provided.