| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
we check whether a key is
- revoked
- expired
- invalid
- unable to encrypt
- unable to sign
|
| |
|
|
|
|
| |
This reads nicer then a hash string. The format is: name (comment) <email>
|
| |
|
| |
|
|
|
|
| |
We need that for auto-completion
|
| |
|
|
|
|
|
| |
sometimes if gpgme doesn't find a key it gives INVALID_VAL sometimes EOF, we now
handle both
|
|
|
|
|
| |
If all the encryption keys are deleted from the encryption list set the encrypt
flag in the enveleope to false
|
|
|
|
|
| |
if the user doesn't supply encrypt with a list of encryption keys, the email
addresses of the email recipients are used
|
|
|
|
|
| |
We use an own has function for that, since pygpgme doesn't implement __cmp__()
or similar
|
|
|
|
|
|
|
|
| |
Multiple recipient-keys can be specified. They are shown in the envelope buffer.
A new command is introduced: 'rmencrypt' do remove a key from the encryption
lsit. Unfortunately pygpgme doesn't implement __cmp__() so we have to either
write something similar on our own or use this solution (index of the key in
encryption list)
|
|
|
|
|
| |
We add a GPG encrypt line with the key to encrypt as description in the envelope
buffer
|
|
|
|
|
| |
It is more useful if we check wether the key is available directly when the user
ask for encryption, rather than doing it before sending it
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We now can define the key, we want to encrypt with as parameter of the encrypt
command
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the envelope has the encrypt flag set we encrypt the (signed if available)
mail and create a PGP/MIME compliant mail
TODOs:
a) create a 'This is a PGP/MIME encrypted mail...' warning on top of all
multipart parts
b) find the correct key for encryption
c) find a way to handle multiple recipients
|
|
|
|
|
| |
The encrypt command sets the encrypt flag of an envelope, which we will use to
later encrypt a message
|
|
|
|
|
| |
This function takes a plaintext string and encryptes it with a given gpg key and
returns the encrypted text
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
... after external processes terminate.
fixes #566
|
|
|
|
| |
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
|
|
|
|
|
|
| |
This will help us identify problems in libnotmuch and reduces visual
artifacts (unfortunately libnotmuch writes messages to stderr that
used to clobber the curses interface).
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
|
|
|
|
|
|
|
| |
This also prevents a zombie from hanging around until the next worker
is spawned by multiprocessing.
Fixes 411.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|\ |
|
| |
| |
| |
| |
| | |
.. the current value cannot be prefix of any bound
keysequence. fixes #547
|
| | |
|
| |
| |
| |
| |
| | |
only sort messages with not-None date header,
append the rest
|
|/
|
|
|
|
|
|
|
|
| |
If the child process is killed using SIGTERM by the parent, send(2)
can fail with EINTR. Install a signal handler for SIGTERM and ignore
EINTR in this particular case.
Fixes #325.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
| |
|
|
|
|
|
|
| |
by keeping a "was locked" flag in the UI.
Once changes are successfully flushed, we use a single "all clear"
notification.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This causes SettingsManager not to read the default configs upon init
when no config paths are passed on.
It is safe because alot.init.main
triggers reading the config files anyway.
This fixes a problem with building the docs on rfd.org due to them not havin configobj available at
build time.
|
|
|
|
|
|
| |
helper.shorten_authors_string was not able to deal with nonempty whitespaces only as author's
realnames.
cf issue #530.
|
| |
|
|
|
|
| |
cf issue #536
|
|\
| |
| |
| |
| | |
Conflicts:
alot/commands/thread.py
|
| |
| |
| |
| | |
... which has been accidentally removed before
|
| |
| |
| |
| |
| | |
before, it did not re-read the thread info from the index.
This showed when updating the tags for individual threads.
|
| | |
|
| |
| |
| |
| |
| |
| | |
these now support an `--all` parameter that allows to tag
all messages in the (search) result set instead of just
all in the selected thread.
|
| | |
|
| |
| |
| |
| |
| | |
- tries to omit code dupication,
- refresh issue
|
| |
| |
| |
| |
| | |
The user can only ever set the target string via a command parameter,
which is sanitizd by argparse as we use choices..
|
| | |
|