On Tue, 18 Apr 2006 00:42:39 +0200, Jukka Salmi <j+nbsd@2006.salmi.ch>
wrote:

> Christos Zoulas --> current-users (2006-04-17 16:30:50 +0000):
> > In article <1145284933l.559l.0l@origin.amelgem.be>,
> > dieter roelants  <dieter.NetBSD@pandora.be> wrote:
> > >On 04/17/06 09:16:00, Jukka Salmi wrote:
> > >
> > >> When using /bin/sh this problem doesn't exist. However, using an old
> > >> (2004-01-01) ksh didn't fix the problem...
> > >> 
> > >> Is anybody else seeing this?
> > >
> > >Yes. I also think I know what changed that causes this. Since
> > >http://cvsweb.be.netbsd.org/cgi-bin/cvsweb.cgi/src/usr.bin/login/login_pam.c.diff?r2=1.16&r1=1.15&f=H
> > >
> > >pam_login restores SIGINT to its previous value. However, the previous  
> > >value as saved on line 534 is SIG_IGN, because it was set so already on  
> > >line 157. My guess is /bin/sh explicitly sets SIGINT to the default.
> > >
> > >(As a workaround you can put 'trap - 2' in your .profile )
> > >
> > >Kind regards
> > >dieter
> > 
> > Yup, this was a mess. I think I fixed it now.
> 
> usr.bin/login/login_pam.c:1.17 indeed fixes the problem. Thanks a lot!
> 
I'm still seeing it, with tonight's source.  I am using ksh.

Oddly enough, typing 'trap' doesn't show anything, but using the above
workaround "solves" it.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb