On Wed, 31 Dec 2025 18:48:50 +0000, "Barak A. Pearlmutter" writes: >Version 3.6.0.3-1 still has an issue with credentials being passed >through to gpg.
yes, and it doesn't work without any encryption at all either. >I generated a package 3.6.0.3-1.1 in thanks for your efforts. we clearly duplicated some of that in the last two days: i pushed out 3.6.0.3-2 yesterday, which... >includes post-3.6.0.3 development, in particular commit ac163d5e which >fixes the problem. ...also includes that commit but not unchanged. upstream doesn't seem to understand public key encryption and insists on passphrase-checking *public* keys without reason. while that commit fixes some/most gpg2 use with agent and gpgsm and other special cases, it absolutely breaks public-key-only/no-private-key-in-sight encryption. (in the orginal commit, line 150 in dup_main.py makes public key encryption strictly depend on check remote. with --no-check-remote you get no public key encryption at all and it falls through to symmetric.) >It also has a few other minor tweaks, like an >updated debian/watch file. i'll have a look at these when i prep the next release, but that won't be for a while: 3.0.6 broke much more than it fixed, and i want 3.0.7 to mature some before i spend time on it. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/ :q :q! :wq :w :w! :wq! :quit :quit! :help help helpquit quit quithelp :quitplease :quitnow :leave :shit ^X^C ^C ^D ^Z ^Q QUITDAMMIT ^]:wq
signature.asc
Description: Digital Signature
