[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#280175: kmail refuses to decrypt OpenPGP/MIME without gpg-agent



> Reading the thread in the KDE bugtracker, it appears the upstream 
> maintainers wish to force us to use the 1.9 branch of OpenPGP, which is 
> tagged by the OpenPGP upstream as development/beta code. 

  gpg2 is beta code. I think gnupg-agent and gpgsm is considered stable.

> Furthermore, that code isn't currently included in Debian. 

  See below.

> This presents a serious problem for this package.

  To some extent, yes.

> Furthermore, the S/MIME howto no longer works properly -- the codebases 
> in that howto require a version of libassuan not currently in debian 
> (even unstable) requiring a manual build of (now) 3 packages 
> (libassuan, libksba, and gnupg-1.9.x) to make this work.  This makes 
> Kmail crypto in Debian increasingly unworkable.

  Uhm, I haven't read the howto lately, but I believe that the single
  packages not in Debian and which are needed are:

    gpgsm
    gnupg-agent

  Last time I checked, all other libraries and auxiliary programs (e.g.,
  pinentry), were in the archive.

> I've not seen any ITPs for gnupg-1.9.x (or at least the gpg-agent part 
> of the package) recently, which would push towards resolving this 
> issue. 

  http://developer.skolelinux.no/~pere/debian-NEW.html. That is the list
  of NEW packages waiting for ftpmaster approval. gnupg2, which provides
  the two mentioned above, is ready since 2004-09-29.

> Whether or not packaging "beta code" would be a Good Idea is something
> that might want to be addressed.

  See the first sentence of this mail.

> Managing this issue for people who can't or don't want to use gpg-agent 
> as part of their crypto setup should probably be strong addressed with 
> the (Kmail upstream),

  Indeed. There is nothing Debian can do about that.

> as well as their wish to force downstream users to use
> beta/non-production code from a utility that they require.

  See the first sentence of this mail.

> Personally, for me as a user, this kind of a bug would be a show-stopper 
> in a heavy production environment.  Having to rebuild 3 packages to get 
> properly functioning crypto in my MUA is absolutely unacceptable.  

  All you need from outside Debian (but see the NEW list above) should be:

    http://smurf.noris.de/code/debian/experimental/i386/gpgsm_1.9.11+cvs20040924-5_i386.deb
    http://smurf.noris.de/code/debian/experimental/i386/gnupg-agent_1.9.11+cvs20040924-5_i386.deb

  And perhaps you can even get rid of gnupg-agent (see comment #17 in
  the upstream bug report).

  Note that such binary packages are provided by a well known DD.

  Cheers,

-- 
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
The easy way is the wrong way, and the hard way is the stupid way. Pick one.




Reply to: