From owner-freebsd-current Sun Dec 10 10:34:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27969 for current-outgoing; Sun, 10 Dec 1995 10:34:06 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27911 for ; Sun, 10 Dec 1995 10:33:59 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA28588 for ; Sun, 10 Dec 1995 19:33:57 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id TAA13590 for freebsd-current@FreeBSD.org; Sun, 10 Dec 1995 19:33:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id TAA08377 for freebsd-current@FreeBSD.org; Sun, 10 Dec 1995 19:32:39 +0100 From: J Wunsch Message-Id: <199512101832.TAA08377@uriah.heep.sax.de> Subject: getpass() and SIGINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 10 Dec 1995 19:32:38 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk Hi all Somebody from the Linux camp was pointing me to this (mis)feature of getpass(3): /* * note - blocking signals isn't necessarily the * right thing, but we leave it for now. */ omask = sigblock(sigmask(SIGINT)|sigmask(SIGTSTP)); While i think that blocking SIGTSTP might not be the worst idea at all, blocking SIGINT contradicts the principle of least surprise, in that you can't interrupt a program that's requesting a password until you finally entered a newline. Unless somebody objects, i'm going to remove SIGINT from the above line. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)