why *not* remove gaskpass ? It's AFAICT completely outside the mission of gSTM and a perfectly good replacement exists for it (using ssh_askpass, as suggested elsewhere).
having a separate and relatively untested codebase that does something security-related (bugs in code that asks for passwords is totally a security concern, I'm sorry to disagree) just seems like asking for trouble, when there's a well-tested and widely-used equivalent available with a minor code change (that I've already submitted) on a different gstm bug (https://bugs.launchpad.net/ubuntu/+source/gstm/+bug/276534) as mentioned above. -- Pressing cancel on gaskpass dialog should return non-zero error. https://bugs.launchpad.net/bugs/276517 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs