[Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

[Paride Legovini]

Hello Bert and thanks for this bug report. I could easily reproduce the
issue you described, but I think it would best be fixed upstream rather
than with an Ubuntu specific patch. I filed an upstream bug report [1]
and linked it to this one.

Given that triggering this bug requires a very odd setting I'm marking
this report with Importance: Low. Should there be an actual use case for
such a high timeout please explain it in a comment and we'll re-evaluate
the bug importance. Thanks!

[1] https://bugzilla.mindrot.org/show_bug.cgi?id=3229

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

** Changed in: openssh (Ubuntu)
       Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1903516

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+subscriptions