Results 257 comments of dkg

i agree with the removal of monkeysign here. Probably better to replace it with a link to [GNOME Keysign](https://wiki.gnome.org/Apps/Keysign) though, which does a lot of what the gui version of...

fwiw, doing autocrypt at the MTA (the "message store", as it's framed here) is similar to the [proxy pattern described in draft-ietf-lamps-e2e-mail-guidance](https://www.ietf.org/archive/id/draft-ietf-lamps-e2e-mail-guidance-16.html#name-message-transport-protocol-) as a "dangerous choice".

I think you're looking at the wrong place for the `gpg` module in python. This is maintained by the GnuPG upstream as part of [gpgme](https://dev.gnupg.org/source/gpgme/browse/master/lang/python/), and has had four releases...

just wanted to note that due to the upcoming release of the crypto-refresh draft, this (and the milestone) should probably be update to refer to v6, not v5.

Thanks for working on this! Note that v6 key, signature, and OPS support should be possible independently of the new pubkey algorithm types. Would it make sense to have a...

ping here on the status v6 key, signature, and OPS support, independently of the new pubkey algorithms.

what's the status on this pull request? it'd be nice to get it included so that openpgp.js doesn't use a fork :)

@kesara can you give an example of a document where it's important to bubble up this failure as a critical failure?

Hi @cabo. [the draft in question](https://gitlab.com/dkg/lamps-samples) uses a Makefile to assemble the draft programmatically, so the `{:include` was used to that effect. That draft is about to go through last...

To try to more clearly state the problem: is it possible to have some text included in a markdown source file *without* having it appear entirely on its own line...