View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004892 | Kali Linux | Kali Package Bug | public | 2018-08-13 12:02 | 2019-02-20 11:38 |
Reporter | bolt | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | suspended | ||
Product Version | 2018.2 | ||||
Summary | 0004892: The alarm() function seems to make autossh exit when it's not supposed to | ||||
Description | Please note: AUTOSSH_POLL is set to a very low number (10 seconds) for demonstration purposes, and [email protected] 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" [email protected] 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] | ||||
Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2018.2), these legacy versions are no longer supported. Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)? 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? |
|