Hey there,

Le lundi 05 juin 2023 à 17:31 +0200, Drew DeVault a écrit :
> Could it be that you have more than one account? Each SSH key must be
> globally unique, you can't have the same key on two accounts.

Hut cli is a terrific tool. I now have new keys and completely deleted
the old ones. Thank you for that!

Of course now comes the *actual issue* to configure my local git repo
with the distant one. That's tricky, but that's also meant for another
thread.

All the best,

Hello Conrad,


On Mon, Jun 5, 2023, at 22:00, Conrad Hoffmann wrote:
> On 6/5/23 17:20, Conrad Hoffmann wrote:
>> On 6/5/23 16:59, Charles-H. Schulz wrote:
>> 3. Your original problem seems to be a display issue. I can confirm that 
>> when I use the FF dev tools to change the fingerprint to be really long 
>> the delete button gets pushed out of the visible area with no way to 
>> scroll to it.
>> 
>> I'll look into fixing that. In the meantime, you can either use FF dev 
>> tool to shorten your fingerprint, or you could look into using the API 
>> to delete the key (e.g. with hut[1]).

Hey Drew,

Drew DeVault @ 2023-06-05 17:31 +02:

> Could it be that you have more than one account? Each SSH key must be
> globally unique, you can't have the same key on two accounts.

I do not have two accounts, but the reason I got into this issue is that I
changed laptop and the reinitialization of my git repos ended up in something
I screwed up, since I'm now trying to manage new ssh keys...

Best,

--

Conrad Hoffmann @ 2023-06-05 16:45 +02:

> On 6/5/23 16:34, Charles-H. Schulz wrote:
>> Conrad Hoffmann @ 2023-06-05 16:18 +02:
>> 
>>> On 6/5/23 15:48, Charles-H. Schulz wrote:
>>>> Conrad Hoffmann @ 2023-06-05 15:14 +02:
>>>>
>>>>> On 6/5/23 15:00, Charles-H. Schulz wrote:
>>>>>> It might be a very silly question - is there anyway to delete existing ssh
>>>>>> keys from one's sr.ht profile?
>>>>>
>>>>> You can delete them on the keys page:

Conrad Hoffmann @ 2023-06-05 16:18 +02:

> On 6/5/23 15:48, Charles-H. Schulz wrote:
>> Conrad Hoffmann @ 2023-06-05 15:14 +02:
>> 
>>> On 6/5/23 15:00, Charles-H. Schulz wrote:
>>>> It might be a very silly question - is there anyway to delete existing ssh
>>>> keys from one's sr.ht profile?
>>>
>>> You can delete them on the keys page:
>>>
>>> https://meta.sr.ht/keys
>> That was my thinking too. Going there there's a button to add ssh

Conrad Hoffmann @ 2023-06-05 15:14 +02:

> On 6/5/23 15:00, Charles-H. Schulz wrote:
>> It might be a very silly question - is there anyway to delete existing ssh
>> keys from one's sr.ht profile?
>
> You can delete them on the keys page:
>
> https://meta.sr.ht/keys

That was my thinking too. Going there there's a button to add ssh keys, but
not to delete them. There's a button to add gpg keys, and another one to
delete them.

Hello there,

It might be a very silly question - is there anyway to delete existing ssh
keys from one's sr.ht profile?

Thank you,
-- 
Charles-H. Schulz
Moved by Freedom - Powered by Standards 
http://www.standardsandfreedom.net

Hey there,


On Fri, May 26, 2023, at 10:35, Charles-H. Schulz wrote:

>> >You should try logging in to git@git.sr.ht
>> > 
>> > It gave me the same outpy than with git@git.sr.ht:~chs :
>> > 
>> > > ssh: Could not resolve hostname git.sr.ht:~chs/: Name or service
>> > > not
>> > > known
>> > > Process /usr/bin/ssh exited abnormally with code 255
>> 

Le jeudi 25 mai 2023 à 23:40 +0200, Moritz Poldrack a écrit :
> On Thu May 25, 2023 at 11:26 PM CEST, Charles-H. Schulz wrote:
> > Le jeudi 25 mai 2023 à 22:14 +0200, Moritz Poldrack a écrit :
> > > This is assuming : to be part of the hostname. SCP notation
> > > doesn't
> > > work
> > > here. You should try logging in to git@git.sr.ht
> > 
> > It gave me the same outpy than with git@git.sr.ht:~chs :
> > 
> > > ssh: Could not resolve hostname git.sr.ht:~chs/: Name or service
> > > not
> > > known
> > > Process /usr/bin/ssh exited abnormally with code 255

Le jeudi 25 mai 2023 à 22:14 +0200, Moritz Poldrack a écrit :
> On Thu May 25, 2023 at 9:49 PM CEST, Charles-H. Schulz wrote:
> > Hello,
> > 
> > Running:
> > > git remote -v
> > gives me something which *I* interprete as being normal:
> > > origin  git@git.sr.ht:~chs/ (fetch)
> > > origin  git@git.sr.ht:~chs/ (push)
> 
> These should be followed by the repo:
>         $ git remote -v
>         origin  git@git.sr.ht:~rjarry/aerc (fetch)
>         origin  git@git.sr.ht:~rjarry/aerc (push)