Hi
On Sun, 14 Jan 2024 02:27:55 -0500 bruce wrote:
> ssh-keygen -t ed25519 -C 'y...@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
> debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g
The pathnames differ here. Adjust the .ssh/config file to point to:
~/.ssh/github/id_ed25519
Hi.
I'm trying to test using SSH key to clone a test repository from the cmdline..
I'm screwing up something in following the different sires/examples to
try to setup the SSH key to connect to "Github" for a user/repository.
It appears that the "ssh -vT g...@github.com" cmd seems to always
Tim:
>> Which I received base64 encoded, for reasons unfathomable.
Dave Close:
> I wonder what did that. It wasn't sent that way:
> Content-type: text/plain; charset="utf-8"
> Content-transfer-encoding: 8bit
These days, 8-bit mail ought to be able to traverse the internet
unscathed (not need
On 12/01/2024 18.34, Samuel Sieb wrote:
On 1/12/24 18:00, Sherman Grunewagen via users wrote:
On 12/01/2024 17.58, Sherman Grunewagen via users wrote:
Yes, the popup explicitly says that the 6.6.9 headers are needed (as I'm
running kernel-6.6.9).
Here's a screenshot of the popup:
Tim via users wrote:
>I wrote:
>> Speaking of email clients modifying received messages ...
>>
>> {This message was not written in HTML. If you are reading it as such,
>> the presentation is dishonest and not what the author intended.}
>Which I received base64 encoded, for reasons
On Sun, 2024-01-14 at 08:29 +1030, Tim via users wrote:
> On Fri, 2024-01-12 at 21:33 -0800, Dave Close wrote:
> > Speaking of email clients modifying received messages ...
> >
> > {This message was not written in HTML. If you are reading it as
> > such,
> > the presentation is dishonest and not
On Fri, 2024-01-12 at 21:33 -0800, Dave Close wrote:
> Speaking of email clients modifying received messages ...
>
> {This message was not written in HTML. If you are reading it as such,
> the presentation is dishonest and not what the author intended.}
Which I received base64 encoded, for
