From nobody Thu Jan 26 23:30:44 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P2xlp6F3Wz3b6Wv for ; Thu, 26 Jan 2023 23:30:46 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P2xlp4LPMz4N2X for ; Thu, 26 Jan 2023 23:30:46 +0000 (UTC) (envelope-from dalescott@shaw.ca) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id L7xZpSya2c9C4LBhdpwbzY; Thu, 26 Jan 2023 23:30:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shaw.ca; s=s20180605; t=1674775845; bh=5sqnhlkst96vmh3gszBAvdcTmnqrKyG4YzEJrJd4/2A=; h=Date:From:To:Cc:In-Reply-To:References:Subject; b=FRIXaSbOVw/W0DJrrDQGrIDz0BVhhdemetVnHQFgMmE7un5Y/EDkUOkZ7AxA2TpGq JOAFRs9l7vMsRXe7ggstIvE2gj+pxXADZ8K88okfiV4G3xp+hJl7eWbeuPSP+syRZO tD39shZGiGr8jxKgzDfs12tJVbtW5c1/Ak6A//OuXr6T91LOJnbc8InCNplpMawejE 9bOk0eURJOnEmcaQ/9thVCWw8pTLevIKkTLVleLdBqHXp0T1273GvKKrW76decgOEK dtXqvgw/XnEQ7TzUpbF8rcQa6D5B+fTlTztkQSOjZlJI6MYdl93twf+//Q8E59TRic UFd6q+g5sCMFg== Received: from cds220.dcs.int.inet ([64.59.134.6]) by cmsmtp with ESMTP id LBhcp8iLIHFsOLBhcphQkE; Thu, 26 Jan 2023 23:30:44 +0000 X-Authority-Analysis: v=2.4 cv=XZqaca15 c=1 sm=1 tr=0 ts=63d30d24 a=9zdlX7M534QhL7mOrorEvQ==:117 a=CU-ez75lMe6tua3-:21 a=FKkrIqjQGGEA:10 a=on0NmgUIp3IA:10 a=IkcTkHD0fZMA:10 a=sfOm8-O8AAAA:8 a=_Dj-zB-qAAAA:8 a=GUfD1UccAAAA:8 a=6I5d2MoRAAAA:8 a=NEAV23lmAAAA:8 a=f8ffklrFPp6UhgNMqt4A:9 a=QEXdDO2ut3YA:10 a=834IS-D2GE8uhZXcNXcv:22 a=TvTJqdcANYtsRzA46cdi:22 a=-EiQn41SfbDD0E51JUit:22 a=IjZwj45LgO3ly-622nXo:22 Date: Thu, 26 Jan 2023 16:30:44 -0700 (MST) From: Dale Scott To: 0x1eef <0x1eef@protonmail.com> Cc: Tomek CEDRO , freebsd-questions Message-ID: <1043094158.25106249.1674775844296.JavaMail.zimbra@shaw.ca> In-Reply-To: References: <2088347522.21487875.1674704156310.JavaMail.zimbra@shaw.ca> <1461614347.22885986.1674746677113.JavaMail.zimbra@shaw.ca> Subject: Re: push to github repo hangs - why? (how to push to Github from FreeBSD) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [162.223.103.50, 162.223.103.50] X-Mailer: Zimbra 8.8.15_GA_4464 (ZimbraWebClient - GC109 (Win)/8.8.15_GA_4468) Thread-Topic: push to github repo hangs - why? (how to push to Github from FreeBSD) Thread-Index: si1ileqjyjJvBhwdImH3xB4VdLDhKA== X-CMAE-Envelope: MS4xfHLntG2Hdku4dqpFaKnsL6hZiWIX0iwOX4GPQL/KJyOTEc8a878MpNNSdd7UMNRDNGp5nnwZ/k53a3NeN54fmCOfnYtwS2y/vzcd6p8HCA2aprzZdWq/ 47ZwyISr9ivSAmx/2Dn7UO0PNppmcLA7vQXd6xwTHROXheVyiZB4qc4f4/muLXjJdJDTjfQyW8kumncMPy5mNB6KBRyB5JDIb18aJ92OZi3zL8CLourlJ3mh ljtEWnxW71+2ced5q+XU480xvhSWWUqQCunoYwafgWE= X-Rspamd-Queue-Id: 4P2xlp4LPMz4N2X X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N ----- Original Message ----- > From: "0x1eef" <0x1eef@protonmail.com> > To: "Dale Scott (dalescott@shaw)" > Cc: "Tomek CEDRO" , "freebsd-questions" > Sent: Thursday, January 26, 2023 11:16:09 AM > Subject: Re: push to github repo hangs - why? (how to push to Github from FreeBSD) > > It is common to authenticate with GitHub for clone, pull, and > push operations using an SSH key. It is recommended (but not required) for the > key to be protected by a passphrase. > > I recommend GitHub's documentation to learn more: > > https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent > > After you have generated an SSH key, you should add the public > key to your GitHub account through their website. You might > also find the "ssh-keygen", "ssh-agent" and "ssh_config" man > pages helpful. Thanks for your suggestion. I was mistakedly thinking ssh wasn't available, but I was confusing using git over ssh with GitHub (which iiuc is no longer supported), with using ssh authentication for git over https. I will add my public ssh key to my github account and expect success this time (I'm already using my private key to ssh login to other servers, so I expect that part should already work).