Phillip Susi writes:
> It was pinentry-curses. I tried switching to pinentry-tty and it rapes > the tty even worse than the curses one. At least some keystrokes > occasionally had some effect with the curses one. With This one nothing > I hit would do anything. Couldn't get it to eventually think I entered > a wrong password and give up, couldn't C-c, C-g, or C-z; I just had to > use ~. to force ssh to hang up. Why and how is this program so abusive > of the terminal? Weird... I ran strace on the program from another terminal and could see that it was reading each keystroke, but continued to read after seeing the \r. I hit C-j ( \n ) and it finally recognized the end of input. I'm thinking that it requires that tty mode that appends a \n to a \r to be enabled, but it doesn't bother enabling it when it takes over the tty. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
