From nobody Thu Jan 26 18:16:09 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 4P2pn0169fz3bJJ1 for ; Thu, 26 Jan 2023 18:16:20 +0000 (UTC) (envelope-from 0x1eef@protonmail.com) Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P2pmz5qGgz400x for ; Thu, 26 Jan 2023 18:16:19 +0000 (UTC) (envelope-from 0x1eef@protonmail.com) Authentication-Results: mx1.freebsd.org; none Date: Thu, 26 Jan 2023 18:16:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1674756977; x=1675016177; bh=935HJCvXHFtyxuW7tUznLuGhHDF2Ub3F+S2X5ga84XY=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=C5Imm/pqozwcqWp4svnTfd1AIFELk53bXlj7IQC0rBsFqWc0VkfN2worFw3LZJxsB HzORhntZ9or+mIi/kvVnIY1hpkBKdWYBRZKi7k7naFEMEOWfV6Z+ZfPcyJ9okimxpz j4DYhR75bThSuJy9bGTguCgtpeNs9jJZPO06Dy6/XZ4HmRDUZYPHe4Yizz9rf6IZ85 sElQG2g2Ers2acH1DzcBTqcxRl/9HK00AnNvE6UXUiRey0eLUVK39+B4XnTXmvpaBU FRcxEWMFquE2iNH+CW7YC08Jatvq/SBm8K5FqYYLuxraFeJtWaIfD1AonxJkI5PM9p EPjtnMYyO5+hQ== To: Dale Scott From: 0x1eef <0x1eef@protonmail.com> Cc: Tomek CEDRO , freebsd-questions Subject: Re: push to github repo hangs - why? (how to push to Github from FreeBSD) Message-ID: In-Reply-To: <1461614347.22885986.1674746677113.JavaMail.zimbra@shaw.ca> References: <2088347522.21487875.1674704156310.JavaMail.zimbra@shaw.ca> <1461614347.22885986.1674746677113.JavaMail.zimbra@shaw.ca> Feedback-ID: 39071764:user:proton 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: quoted-printable X-Rspamd-Queue-Id: 4P2pmz5qGgz400x X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > Can you explain your workflow in more detail? It looks like I've got some= reseach to do.... Hi Dale, It is common to authenticate with GitHub for clone, pull, and=20 push operations using an SSH key. It is recommended (but not required) for = the key to be protected by a passphrase.=20 I recommend GitHub's documentation to learn more: https://docs.github.com/en/authentication/connecting-to-github-with-ssh/gen= erating-a-new-ssh-key-and-adding-it-to-the-ssh-agent After you have generated an SSH key, you should add the public=20 key to your GitHub account through their website. You might=20 also find the "ssh-keygen", "ssh-agent" and "ssh_config" man=20 pages helpful.