Closed jojoo- closed 11 years ago
i suppose we should put this into a gpg.conf in $GNUPGHOME. We should think about what other options we want to give here: GPG Configuration Options
ups, forgot to write: putting the lock-never option in data/gpg worked. do we only need this for mac or do we use this globally?
setting this in data/gpg/gpg.conf will set it globally for all platforms because we need to share the keys. we could specify this with the starter as we do it for the gpg path, but i'd prefer not write into all cfgs before starting the app.
and windows & linux will have to delete this item. sucks :/
maybe there is another way?
y shouldn't we use lock-never on all platforms?
i think i misundersood you. i think using lock-nerver should be safe in our usecase, and we can use it on all platforms
This should be fixed with d07d6a224ce4661cf6281012c984ab38011aebd1 and 4012a03eb4e1a26c8c930bcdef7f7a2800fdd3a7 but needs some testing to confirm that using lock-never actually works stable under all operating systems and really fixes this problem. mbe i'll be able to test this in the next couple of days, but @jojoo- if you could please also take a look at this.
GPG for Mac does not work:
The problem seems to be, that it can't lock because of fat not supporting links. As suggested in http://lists.gnupg.org/pipermail/gnupg-devel/2009-January/024747.html i added --lock-never to the list of gpg options and it worked BUT we need to do that automatically.