Chasing missing SIGINT signals down the SSH rabbit hole

Re:Chasing missing SIGINT signals down the SSH rabbit hole by russjones on Thursday May 24, 2018 @02:44PM (#17147019)

Author here, happy to answer any questions about the post.

[ Parent | on HN ]

Re:Chasing missing SIGINT signals down the SSH rabbit hole by yayana on Thursday May 24, 2018 @02:50PM (#17147083)

Is the double meaning of the headline intentional? I was expecting a timing or other attack to determine data has a particular origin..

[ Parent | on HN ]

Re:Chasing missing SIGINT signals down the SSH rabbit hole by wyldfire on Thursday May 24, 2018 @02:53PM (#17147106)

No it's [probably] not. SIGINT is unfortunately ambiguous, unlike SIGKILL, SIGTERM, SIGQUIT, SIGUSR1. :)

[ Parent | on HN ]

Re:Chasing missing SIGINT signals down the SSH rabbit hole by derefr on Thursday May 24, 2018 @03:28PM (#17147416)

I'd have suggested "missing Ctrl+C" instead (like the title of the bug report.)

[ Parent | on HN ]

Re:Chasing missing SIGINT signals down the SSH rabbit hole by c12 on Friday May 25, 2018 @05:15AM (#17151843)

As far as I know SIGINT is the name of the signal and Ctrl+C is simply a key combination that triggers it.

I read the title to mean SIGINT the signal and it wasn't until I came to HN comments did I see have another meaning.

[ Parent | on HN ]

Re:Chasing missing SIGINT signals down the SSH rabbit hole by russjones on Thursday May 24, 2018 @03:36PM (#17147507)

Ha, nope, didn't realize this until everyone started mentioning it in the comments.

[ Parent | on HN ]