Hi Dirk, sorry I didn't respond earlier, but I did try these things.  They
just didn't work.  Questioning whether I didn't run into a firewall rule.
Even though they allow us to add an SSH Key in GitHub, that doesn't mean
they've opened port 22 on the server.  When I try to ssh g...@github.com, it
ends up "Connection timed out".  I would kind of expect a refusal if the
firewall were slapping it down, but not sure.  I've also turned
strictHostKeyChecking off and that also produced failure from the cloning.
This is a gov repository so I'm guessing that it is, indeed, a firewall
rule.  Thanks for all the help!  Guess I should be thankful that 443 is
open to me...

On Wed, Mar 31, 2021 at 12:10 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Montag, den 29.03.2021, 12:26 -0700 schrieb eric....@gmail.com:
>
> The only thing I can guess is that ssh is getting a question when he
> attempts to connect wanting to be added to the known_hosts file.  Wondering
> if maybe there's a way to establish this if this is indeed the issue?
>
>
> Yes, of course it does, and yes, there is (see my other two replies from
> yesterday). SSH verifies that it indeed connects to the correct *remote*
> host (github.com in this case), by comparing the *HOST* key of the remote
> host it has stored in the *local* user's (or machine's) *known_hosts*
> file. On the first connection, it asks the user to confirm the remote host
> key (unless the user has certain options set in her *~/.ssh/config* to
> either skip the verification completely or accept new keys w/o asking). And
> this is what's happening here.
>
> So, to get out of this, you need to login to your Jenkins machine once (as
> the user running Jenkins), run "ssh g...@github.com" and confirm the host
> key. Or add "StrictHostKeyChecking no" or, if your SSH is recent enough,
> "StrictHostKeyChecking accept-new" to that user's ~/.ssh/config (or
> machine's /etc/ssh/ssh_config).
>
> HTH...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/Ob42FqU-0UY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d8bd7d209c38e258fa083e78f484d2529a9b4cab.camel%40opentext.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d8bd7d209c38e258fa083e78f484d2529a9b4cab.camel%40opentext.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAByBicZijnZo%2BsKteoUCzoTwJ_%3DxFv0Yt7mppbEbkFCa9BR_zQ%40mail.gmail.com.

Reply via email to