View Issue Details

IDProjectCategoryView StatusLast Update
0004892Kali Linux[All Projects] Kali Package Bugpublic2019-02-20 11:38
ReporterboltAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionsuspended 
Product Version2018.2 
Target VersionFixed in Version 
Summary0004892: The alarm() function seems to make autossh exit when it's not supposed to
DescriptionPlease note: AUTOSSH_POLL is set to a very low number (10 seconds) for demonstration purposes, and yo@foo.coma is obviously an invalid target for SSH, but it's easier to replicate using this than to disconnect from the network, at which point any target will be unavailable.

The following invocation will run forever on a Debian Stretch install, as intended. When the network is brought up (or someone enters an actual valid target for SSH) it will connect.

AUTOSSH_DEBUG=1 AUTOSSH_GATETIME=0 AUTOSSH_POLL=10 AUTOSSH_PORT=0 autossh -n -N -T -g -o "ExitOnForwardFailure=yes" -o "ConnectTimeout=15" -o "ServerAliveInterval=10" -o "ServerAliveCountMax=3" -o "TCPKeepAlive=yes" yo@foo.coma

On Debian, it will periodically print lines saying "set alarm for N secs", and when N reaches 0, it will pop back up to 10.

On Kali, when the alarm time reaches 0, the program will end abruptly, with an exit status of 142, and print "Alarm clock" (found nowhere in the autossh source) to the console, as such:

[lots more of this above]
autossh[3410]: sleeping for grace time 3 secs
autossh[3410]: starting ssh (count 16)
autossh[3410]: ssh child pid is 3453
autossh[3410]: check on child 3453
autossh[3410]: set alarm for 1 secs
autossh[3453]: child of 3410 execing /usr/bin/ssh
ssh: Could not resolve hostname foo.coma: Name or service not known
autossh[3410]: check on child 3453
autossh[3410]: ssh exited with error status 255; restarting ssh
autossh[3410]: expired child, returning 1
autossh[3410]: checking for grace period, tries = 16
autossh[3410]: sleeping for grace time 4 secs
Alarm clock



2019-02-20 11:38

administrator   ~0010335

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2018.2), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux -

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read:

Issue History

Date Modified Username Field Change
2018-08-13 12:02 bolt New Issue
2018-08-18 19:35 elwood Status new => acknowledged
2019-02-20 11:38 g0tmi1k Status acknowledged => closed
2019-02-20 11:38 g0tmi1k Resolution open => suspended
2019-02-20 11:38 g0tmi1k Note Added: 0010335