| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
... which displays a prefix of the msg contents.
This feature was missing in the docs.
|
|\
| |
| | |
Clean up doc source generators
|
| | |
|
|\ \
| | |
| | | |
command/envelope: Prompt before sending an encrypted message with Bcc
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently alot cannot encrypt to Bcc recipients, and it isn't obvious
how to implement encrypted BCC without a metadata leak (the key ids of
the Bcc recpients would be visible to the to and cc recipients as well
as the other bcc recipients). As such it hasn't been implemented yet
(although #949) is opened for such encryption.
In the mean time alot doesn't encrypt to bcc recipients at all, making
the message all but useless (it might be useful to send it to yourself
as a blind recipient, or to two email addresses of the same person).
Since most people don't know that alot has this limitation, we should
really warn them. This adds a prompt before constructing the message
for that case.
|
|\ \
| |/
|/| |
Submit/update docs
|
| |
| |
| |
| | |
Since the original patch that added the support didn't.
|
| | |
|
|\ \
| |/
|/| |
commands/envelope: Fall back to account for signing key
|
| |
| |
| |
| |
| |
| | |
This new return_default flag (which is an optional and default to
False) will try to return the default account if it cannot find an
account matching the address hint.
|
| |
| |
| |
| |
| |
| |
| | |
If there isn't a key provided as an argument to sign or togglesign, fall
back to using the account of the sending address to determine the key,
otherwise the message will be marked as "to sign", but won't actually be
signed. This is the same type of logic used for sign_by_default.
|
|\ \
| | |
| | | |
db/utils: Support unicode in signatures
|
| | |
| | |
| | |
| | |
| | | |
Nested ternaries are awful to read, especially in this case. Putting it
into an if statement is actually more terse, and is much easier to read.
|
| | |
| | |
| | |
| | |
| | |
| | | |
1) dont use len() to test that a list is non-empty
2) only go down the else clause if it's possible to have a valid
signature.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Currently if a signature name has a non-ascii unicode character in it,
the thread will fail to load because a UnicodeEncodeError. This patch
fixes that by converting the str into unicode.
|
| | |
| | |
| | |
| | | |
One of these tests is known to fail, and marked as xfail.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| | |
These are pretty basic, but they do cover most of the conditions, even
if they rely heavily on mocking.
|
|\ \
| |/
|/| |
settings: Allow loading themes from system locations
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds additional system locations to search for theme files, which
are either defined as the environment variable XDG_DATA_DIRS, or the
generic fallback (per the xdg base directories spec) as
/usr/local/share and /usr/share. We then add alot/themees to those paths
to search for themes in. This allows a package manager to install the
theme files system wide along with alot, and for alot to load them from
the system wide directories.
The Archlinux alot-git package is already installing the packages like
this.
|
|\ \
| | |
| | | |
helper: Do not add a newline to the end of a signed section
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The spec is very clear here:
(2) An appropriate Content-Transfer-Encoding is then applied; see
section 3. In particular, line endings in the encoded data
MUST use the canonical <CR><LF> sequence where appropriate
(note that the canonical line ending may or may not be present
on the last line of encoded data and MUST NOT be included in
the signature if absent).
That very last MUST NOT is what's important here, we shouldn't be adding
newlines if they weren't there to begin with. Because we do it causes
signed blobs that have newlines to be invalid since we've changed the
substance of the signed code.
|
|\ \
| | |
| | | |
Some misc tests
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
One is an abstract method anyways and the other one is trivial. It just
calls two other functions that are already covered by tests.
This results in 100% test coverage for alot/addressbook/*.
|
| | | |
|
| |/ |
|
|\ \
| |/
|/| |
Fix solarized light colorscheme name
|
| | |
|
|/ |
|
|\
| |
| | |
Add crypto module tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are currently several problems with this docstring:
1) it says the return type is list, but it's actually an iterator
2) it says the first parameter is keyid, but it's hint
3) no types are specified.
This patch corrects that.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a just a small refactor that makes things a little more
readable, and provides slightly more verbose messages in for signing and
encrypting failures.
Mainly this uses str.format instead of inline concatenation, but it also
rewraps and removes '+' operators from a string already wrapped in
parens
|
|/
|
|
|
|
| |
This covers mosts of the functions in the crypto module, but doesn't
bother with the hash_key function, which is slated for deletion in the
port to python-gpg. It also doesn't cover re-raising errors.
|
|\
| |
| | |
crypto: Fix handling of signed messages
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To verify the signature correctly we need to ensure that the body of the
message is decoded the same way as it was when it was signed,
specifically using helper.email_as_string to insert \r\n instead of
.as_string, which only inserts \n.
Fixes #1079
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gpgme.Context.verify doesn't raise an exception, instead it attaches the
error as an attribute of the return value. This means that we've been
returning that a signature is valid even when it isn't.
This patch checks the attribute instead of try/excepting. Because there
is a second bug (fixed in the next patch) signature verification will
always fail with this patch.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a couple of basic tests for the signing and verification of
signatures code in the crypto module. This relies on the utilities
module introduced in the last patch.
One of the tests in here is expected to fail
|
|/
|
|
|
| |
This module currently only contains a class that adds a class level
addCleanup function (called addClassCleanup).
|
|\
| |
| | |
Implement :tag commands in envelope buffer
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
The test file is also renamed.
|
| | |
|