[Pkg-gnupg-maint] Bug#701566: gnupg: wrong length of month used for key expiration date

[Michael Below]

Package: gnupg
Version: 1.4.12-7
Severity: minor

Dear Maintainer,

today I generated a new key (0xfaaad43b), and I set the expiration
date to 24 months. I had expected this to be the same as two
years, as it is defined in the calendar. In fact, it is ten days
less.

It looks like gpg assumes that one month = 30 days, so a timespan
of one month from today, according to gpg, ends not on March 24th,
but on March 26th. This is obviously wrong. 

GnuPG should use the measure month as defined in the calendar.
Alternatively, it could define its own measure, but then it should
be named differently.

Thanks for your efforts!

Michael Below


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnupg depends on:
ii  dpkg          1.16.9
ii  gpgv          1.4.12-7
ii  install-info  4.13a.dfsg.1-10
ii  libbz2-1.0    1.0.6-4
ii  libc6         2.13-38
ii  libreadline6  6.2+dfsg-0.1
ii  libusb-0.1-4  2:0.1.12-20+nmu1
ii  zlib1g        1:1.2.7.dfsg-13

Versions of packages gnupg recommends:
ii  gnupg-curl     1.4.12-7
ii  libldap-2.4-2  2.4.31-1

Versions of packages gnupg suggests:
ii  eog                                              3.4.2-1+build1
pn  gnupg-doc                                        <none>
ii  graphicsmagick-imagemagick-compat [imagemagick]  1.3.16-1.1
ii  libpcsclite1                                     1.8.4-1
ii  xloadimage                                       4.1-19

-- no debconf information