Hi DKG and Jameson!

I tried out assword today, and since it's implemented in Python I was curious
to see the GTK GUI. I opened it for the first time, mashed on the keyboard a
bit, typed ↵. It said something about there being no context. I clicked
"Create". Then it died and turned it's legs up in the air. :'(

I didn't really look into why it died, nor try to get a log from it, but I
thought I'd let the two of you know that it gliched out and hopefully it's not
doing this for other people. If you need me to, I can pull a traceback out of
it.

Thanks for working on Debian!

Hi isis!

glad to hear you're experimenting with assword!

did it also give you a horrible pythonic backtrace, or did the gui just
go away?  If it gave you a backtrace, i'd like to see it.

the expected behavior, though, is that the window should disappear, and
then whatever had kbd input focus before should suddenly have a
high-entropy password typed or pasted into it.

assword gui is (deliberately) extremely minimal.  its job is to collect
a context from the user and then inject the associated password into the
X11 session it was pulled from.

Maybe we could include a «?» button in the gui that explains the
expected workflow a bit if it sees that there are no contexts available
-- would that help?  I don't want to clutter the gui if we can avoid it
though, i'm a big fan of the minimalism.

Daniel Kahn Gillmor transcribed 2.2K bytes:

Nope, there was no backtrace, as far as I recall. There were some lines
printed to the console, but I don't recall what they were.

And yes, it did print the passphrase to the terminal which I'd opened the GTK
app in. Twice, actually, once before my promt, once after. So it seems like
this isn't a bug at all, it's just not behaviour that I expected from a
GUI. (Though I don't normally use GUIs, so my user experience probably
shouldn't be taken as canonical.)

I'm not sure. Some explanation somewhere would have been nice, although I also
agree with you that minimalism is preferable.