ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Does it take a while before a public key becomes available o

From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
Date: Tue, 13 Jun 2017 06:13:59 -0700
On Tue, Jun 13, 2017 at 6:01 AM, Graham Bloice
<graham.bloice@xxxxxxxxxxxxx> wrote:
>
>
> On 13 June 2017 at 13:37, Richard Sharpe <realrichardsharpe@xxxxxxxxx>
> wrote:
>>
>> On Tue, Jun 13, 2017 at 12:08 AM, Roland Knall <rknall@xxxxxxxxx> wrote:
>> > Usually adding the key should take immediately. Try on a console window
>> > together with your user-name and don't forget the port 29418.
>> >
>> > Usually the following command should print you the version on a console:
>> >
>> >    ssh -p 29418 <your_username>@code.wireshark.org gerrit version
>>
>> Thanks, I will give it a try when I have finished debugging this other
>> problem I have at work.
>>
>> I guess I was confused by this instruction:
>>
>>          git clone ssh://USERNAME@xxxxxxxxxxxxxxxxxx:29418/wireshark
>>
>> because Phabricator used a weird single username. Since you have put
>> angle brackets around your_username it is clear that I should replace
>> that token with my username.
>
> The commands are different because they're intended for two different
> purposes.
>
> The ssh command attempts to open a remote shell connection to the gerrit
> server, the git clone command uses ssh to clone the wireshark repository.

So you are saying that it literally should be
USERNAME@xxxxxxxxxxxxxxxxxx:... there?

Let me check it again to see if it is working now.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)