Re: [Tails-dev] Please review'n'merge feature/monkeysign
On Wed, Dec 18, 2013 at 12:26:32AM +0100, intrigeri wrote: berta...@ptitcanardnoir.org wrote (17 Dec 2013 22:29:20 GMT) : I've just reported this problem upstream. Being the one that raised the issue. I could have done that myself after our discussion. Credits, etc... I felt it was my responsibility to follow-up on the problems that go with a branch I've submitted. I'm sorry. Ah, my bad, didn't think about it that way, and it makes sense. Nevermind then. This confirms that we really need to get you a spare laptop for testing :p Hmm, well, make it two then, as my computer actually don't have a camera. :) I'll think about it, and if I don't find a way to test it, I'll ask for someone else to take over. bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
sajol...@pimienta.org wrote (17 Dec 2013 10:06:53 GMT) : I push a minor documentation fix with commit f0762cd. Shall I merge it myself? Reviewed, looks good, merged. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
On Tue, Dec 17, 2013 at 10:06:53AM +, sajol...@pimienta.org wrote: intrigeri: Merged I push a minor documentation fix with commit f0762cd. Shall I merge it myself? That seems minor and relevant, I guess you can. :) even if this might need a bit of documentationi though, as monkeysign errors out with a backtrace if one don't use the --no-mail option, as there is no /usr/sbin/sendmail in Tails. But the signature is added to the key still. When using the --no-mail option, it outputs quite a lengthy mail, with mime headers and all, but that isn't really possible to use it in claws-mail, as you can't edit the email source. Best is probably to just paste the pgp public key bloc part of it into a new mail. Doesn't piping it to Mutt work? monkeysign currently being command-line only, I was thinking more of Mutt users than Claws Mail's ones when I thought we wanted this in Tails. Hopefully this will change at some point. I've tried that, but couldn't find a way to have it working. That was a short session though, I might have missed something. Note that monkeysign also includes and graphical tool for fingerprint scanning: monkeyscan; with QR codes and all :) Which doesn't work in Tails, as we don't ship the recommends of monkeysign (python-qrencode, python-gtk2, python-zbar, python-zbarpygtk). Not sure if it is that usefull in Tails' usecase though (like, not running on a mobile platform). Regarding the need for documentation, well, I don't think this would be a good use of our time. I expect that the kind of public that's addressed by a command-line only piece of software will know what to do with its output and manpage. Writing monkeysign documentation for newbies seems very hard a task to me, and I doubt more than a handful of people would benefit from it. If someone wants to make monkeysign better suited for other kinds of users, IMHO they should instead write a GUI for it, or (even better) integrate it into Seahorse, or something. Agreed. I admit it is sometimes a bit blurry but our position was to only document on our website things that were specific to Tails (see the Pidgin and OTR documentation for example). So writing a tutorial on using monkeysign is out of scope. I admin that some pieces of software are documented beyond this requirement already (for example KeepassX) but it is also much more advertised and a key feature than monkeysign ever will be. I tried to improve a bit on this by improving the visibility of the list of included software from the documentation index. That's commit e8a33f6 in master. Agreed. That sounds relevant regarding our actual documentation. Having given it a bit of tries, I believe monkeysign at the moment is only for power users, they should be able to get it by themselves. If we want it to be usable for everyone, I think we'd have to work a bit with upstream so that it integrates a bit better. bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
Hi, berta...@ptitcanardnoir.org wrote (17 Dec 2013 11:44:11 GMT) : Doesn't piping it to Mutt work? monkeysign currently being command-line only, I was thinking more of Mutt users than Claws Mail's ones when I thought we wanted this in Tails. Hopefully this will change at some point. I've tried that, but couldn't find a way to have it working. That was a short session though, I might have missed something. Ah crap, so I've really had you merge something that is *far* from being usable out-of-the-box. Still, I think it makes sense to ship it, at least for a while, for the reasons I've given previously. I've just reported this problem upstream. Note that monkeysign also includes and graphical tool for fingerprint scanning: monkeyscan; with QR codes and all :) Which doesn't work in Tails, as we don't ship the recommends of monkeysign (python-qrencode, python-gtk2, python-zbar, python-zbarpygtk). My intent was to ship these packages in Tails, and it was a mistake from my part to act as if we installed Recommends by default: before I uploaded these packages to Debian backport, I've verified that each of these packages as available in Squeeze. I'll submit a branch that installs all that stuff, as it was part of what convinced me it was worth shipping monkeysign at all. Not sure if it is that usefull in Tails' usecase though (like, not running on a mobile platform). Most laptops have a camera these days. Making fingerprint verification easier is (part of) what makes monkeysign potentially more relevant than caff. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
On Tue, Dec 17, 2013 at 08:27:57PM +0100, intrigeri wrote: Hi, berta...@ptitcanardnoir.org wrote (17 Dec 2013 11:44:11 GMT) : Doesn't piping it to Mutt work? monkeysign currently being command-line only, I was thinking more of Mutt users than Claws Mail's ones when I thought we wanted this in Tails. Hopefully this will change at some point. I've tried that, but couldn't find a way to have it working. That was a short session though, I might have missed something. Ah crap, so I've really had you merge something that is *far* from being usable out-of-the-box. Still, I think it makes sense to ship it, at least for a while, for the reasons I've given previously. Yep, that's why I merged it. I've just reported this problem upstream. Being the one that raised the issue. I could have done that myself after our discussion. Credits, etc... Note that monkeysign also includes and graphical tool for fingerprint scanning: monkeyscan; with QR codes and all :) Which doesn't work in Tails, as we don't ship the recommends of monkeysign (python-qrencode, python-gtk2, python-zbar, python-zbarpygtk). My intent was to ship these packages in Tails, and it was a mistake from my part to act as if we installed Recommends by default: before I uploaded these packages to Debian backport, I've verified that each of these packages as available in Squeeze. I'll submit a branch that installs all that stuff, as it was part of what convinced me it was worth shipping monkeysign at all. Ok, I'll stay tuned, but might not be able to test this fancy feature *that* extensively (meaning I'll probably just check that the UI starts). Not sure if it is that usefull in Tails' usecase though (like, not running on a mobile platform). Most laptops have a camera these days. Making fingerprint verification easier is (part of) what makes monkeysign potentially more relevant than caff. Yeah, sorry I have hard time thinking about people showing themselves their laptop that way, but why not. bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
Hi, Merged Thank you. even if this might need a bit of documentationi though, as monkeysign errors out with a backtrace if one don't use the --no-mail option, as there is no /usr/sbin/sendmail in Tails. But the signature is added to the key still. When using the --no-mail option, it outputs quite a lengthy mail, with mime headers and all, but that isn't really possible to use it in claws-mail, as you can't edit the email source. Best is probably to just paste the pgp public key bloc part of it into a new mail. Doesn't piping it to Mutt work? monkeysign currently being command-line only, I was thinking more of Mutt users than Claws Mail's ones when I thought we wanted this in Tails. Hopefully this will change at some point. Regarding the need for documentation, well, I don't think this would be a good use of our time. I expect that the kind of public that's addressed by a command-line only piece of software will know what to do with its output and manpage. Writing monkeysign documentation for newbies seems very hard a task to me, and I doubt more than a handful of people would benefit from it. If someone wants to make monkeysign better suited for other kinds of users, IMHO they should instead write a GUI for it, or (even better) integrate it into Seahorse, or something. It's an enhancement, as it automates the key retrieval and signing process, but might need some more to be really usable by monkeys. Fully agreed. I've wondered about this too while I was testing it within Tails, hesitated, but I've eventually decided to request a merge for it anyway. IMHO, it's mainly a long-term move: installing it by default in Tails may be enough for us to start using it, to discover its drawbacks in the context of Tails, and it could be a motivating factor for $SOMEONE to adapt the software to the Tails context. It may also make monkeysign better known, which also increases the chances it gets better. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/monkeysign
On Fri, Dec 06, 2013 at 08:39:58PM +0100, intrigeri wrote: Hi, please review'n'merge feature/monkeysign into devel (candidate for 0.23). Ticket: #6338 Merged even if this might need a bit of documentationi though, as monkeysign errors out with a backtrace if one don't use the --no-mail option, as there is no /usr/sbin/sendmail in Tails. But the signature is added to the key still. When using the --no-mail option, it outputs quite a lengthy mail, with mime headers and all, but that isn't really possible to use it in claws-mail, as you can't edit the email source. Best is probably to just paste the pgp public key bloc part of it into a new mail. It's an enhancement, as it automates the key retrieval and signing process, but might need some more to be really usable by monkeys. Bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] Please review'n'merge feature/monkeysign
Hi, please review'n'merge feature/monkeysign into devel (candidate for 0.23). Ticket: #6338 Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
