Hi Kevin,
On Sunday, 2019-08-11 13:44:53 -0700, Kevin J. McCarthy wrote:
> On Sun, Aug 11, 2019 at 10:24:42PM +0200, Eike Rathke wrote:
> > The minimal public key of multiple UIDs written as autocrypt keydata in
> > my case is 15kB, quite large as mail overhead. I guess there's no way
> > to red
On Mon, Aug 12, 2019 at 11:57:14AM +0200, Eike Rathke wrote:
Tried (then it needs to be done with --export-secret-keys not --export,
of course..) with 6 of 12 uids but that didn't change anything. I think
the size is merely due to the rsa4096 used on that key.
How many lines is the Autocrypt he
It looks like building a static binary doesn't work with the sqlite3
option, due to a couple extra dependencies needed in that case.
One common, and increasingly prevalent, solution is to use pkg-config
and the related autoconf macros (e.g. PKG_CHECK_MODULES). However, this
isn't without issu
On Mon, Aug 12, 2019 at 09:15:57AM -0700, Kevin J. McCarthy wrote:
> One common, and increasingly prevalent, solution is to use pkg-config
> and the related autoconf macros (e.g. PKG_CHECK_MODULES).
> However, this isn't without issues, for example dealing with libraries
> installed in non-standa
On Mon, Aug 12, 2019 at 07:11:20PM +0200, Oswald Buddenhagen wrote:
On Mon, Aug 12, 2019 at 09:15:57AM -0700, Kevin J. McCarthy wrote:
One common, and increasingly prevalent, solution is to use pkg-config
and the related autoconf macros (e.g. PKG_CHECK_MODULES).
However, this isn't without is
Hi Kevin,
On Monday, 2019-08-12 09:07:49 -0700, Kevin J. McCarthy wrote:
> On Mon, Aug 12, 2019 at 11:57:14AM +0200, Eike Rathke wrote:
> > Tried (then it needs to be done with --export-secret-keys not --export,
> > of course..) with 6 of 12 uids but that didn't change anything. I think
> > the s
On Tue, Aug 13, 2019 at 12:56:37AM +0200, Eike Rathke wrote:
and then gpg --homedir testdir -k lists the 12 (!) addresses of the
original key. It seems that the Autocrypt header content for an existing
key is pulled from the original keyring and not the ~/.mutt/autocrypt
keyring.
The base64
On Mon, Aug 12, 2019 at 04:13:16PM -0700, Kevin J. McCarthy wrote:
The base64 keydata is stored in the sqlite3 database once the account
is created. Updating the key in gpg subsequent to that won't have an
effect on the keydata.
Make sure to remove the account (via ) and
recreate it if you m
Hi Kevin,
On Monday, 2019-08-12 10:51:56 -0700, Kevin J. McCarthy wrote:
> > why would supplying a non-standard search path to pkg-config files be
> > any more problematic than a non-standard path to the library itself?
>
> By all means, please enlighten me. My understanding from starting to
>
Hi Kevin,
On Monday, 2019-08-12 16:13:16 -0700, Kevin J. McCarthy wrote:
> On Tue, Aug 13, 2019 at 12:56:37AM +0200, Eike Rathke wrote:
> > and then gpg --homedir testdir -k lists the 12 (!) addresses of the
> > original key. It seems that the Autocrypt header content for an existing
> > key i
Hi Kevin,
On Monday, 2019-08-12 17:38:16 -0700, Kevin J. McCarthy wrote:
> On the plus side, it actually gives you some flexibility if you wanted to
> take advantage of it. You could create a different base64 export of the
> same keyid, each with a single uid, and store it right in the database
On Tue, Aug 13, 2019 at 02:39:35AM +0200, Eike Rathke wrote:
Yes. Or rather, if "no" then do not check for it, and break if
--enable-autocrypt was specified as well.
PKG_CHECK_MODULES generates code to output a message if the .pc file
wasn't found and to adjust PKG_CONFIG_PATH or how things can
On Mon, Aug 12, 2019 at 07:05:19PM -0700, Kevin J. McCarthy wrote:
> There's no new issue here with sqlite3. :-/
>
Actually I can see an issue with the sole fact that sqlite3 is a new
dependency.
Before introducing autocrypt to mutt, there was no need for it. I can see
that mutt can already use
13 matches
Mail list logo
