Package: monkeysign
Version: 1.1
Severity: wishlist
X-Debbugs-Cc: tails-dev@???
Hi,
unless we revert this change, Tails 0.23, scheduled for March 4, will
ship with monkeysign. Yay.
However, this raises one serious usability issue: there is no SMTP
server in Tails, and we include two MUA (namely: Mutt and Claws Mail).
So, users have to:
1. either use the --smtp* options (I've not looked at the kind of
SSL/TLS encryption that is supported, and I've seen no way of
pinning the remote server's certificate to a particular CA, nor to
provide its fingerprint; besides, the password either is set on the
command-line, or prompted interactively, one being unsafe, and the
other being a pain usability-wise, so I'll assume this is not good
enough for us)
2. or use the --no-mail option, and manually copy'n'paste the email
into their MUA (assuming it supports the MIME format output by
monkeysign, which I have not tried, and TBH I slightly doubt it
will work).
At this point, it should be clear that, in the current state of
things, monkeysign will be mostly unusable for our usecase (if I'm
wrong, I'd be delighted to be explained how one should do :)
It would be great to have a simple way to:
* either save the output email to a file (that one can manually feed
into Mutt later)
* or to pipe it to Mutt (which does not work yet, as monkeysign's
stdout is used by its interactive UI; perhaps printing it to a FD
greater than 2 would be doable?);
* or to do both internally, and to directly invoke the preferred MUA,
providing it with the email headers and body in the way it wants it.
I'm aware this is related to #720047, and likely solving the one will
solve the other usecase.
Thoughts? Any other way this usecase could be taken care of?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
