SSH on Gitlab

Bryan Richter bryan at haskell.foundation
Tue Jun 27 12:03:50 UTC 2023


Ah - my bet is that the hospital's IT department were simply blocking ssh
as a "better safe than sorry" infosec policy.

On Tue, 27 Jun 2023 at 12:37, Simon Peyton Jones <
simon.peytonjones at gmail.com> wrote:

> Thanks for following up.
>
> I came home from hospital, and it was fine at home.  Maybe there was
> something strange in their Wifi.   If I was there for longer I'd have had
> to investigate more (somehow) but it was a thankfully brief stay.
>
> Simon
>
> On Tue, 27 Jun 2023 at 07:29, Bryan Richter <bryan at haskell.foundation>
> wrote:
>
>> Hi Simon,
>>
>> Did this, in fact, work itself out?
>>
>> On Thu, 22 Jun 2023 at 18:43, Ben Gamari <ben at smart-cactus.org> wrote:
>>
>>> Simon Peyton Jones <simon.peytonjones at gmail.com> writes:
>>>
>>> > Is SSH working on gitlab.haskell.org?  I'm getting this
>>> >
>>> > simonpj at CDW-8FABODHF0V5:~$ ssh -v git at gitlab.haskell.org
>>> > OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
>>> > debug1: Reading configuration data /home/simonpj/.ssh/config
>>> > debug1: Reading configuration data /etc/ssh/ssh_config
>>> > debug1: /etc/ssh/ssh_config line 19: include
>>> /etc/ssh/ssh_config.d/*.conf
>>> > matched no files
>>> > debug1: /etc/ssh/ssh_config line 21: Applying options for *
>>> > debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
>>> > debug1: Connection established.
>>> > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
>>> > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
>>> > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_xmss type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
>>> > debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
>>> >
>>> > At this point it hangs.  Stackoverflow suggests
>>> > <
>>> https://superuser.com/questions/1374076/what-does-it-mean-if-ssh-hangs-after-connection-established
>>> >a
>>> > server fault.  But I'm on a new WLAN so I suppose there could be some
>>> > bizarre filtering?
>>> >
>>> I suspect this may be a filtering issue. Like Tom, I am able to connect
>>> without issue. A Wireshark trace [1] may help shed light on the
>>> situation. Happy to have a call to debug if this would be helpful.
>>>
>>> Cheers,
>>>
>>> - Ben
>>>
>>>
>>> [1] https://www.wireshark.org/
>>> _______________________________________________
>>> ghc-devs mailing list
>>> ghc-devs at haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20230627/5e3ef919/attachment-0001.html>


More information about the ghc-devs mailing list