will disable the check altogether for the upcoming version 1.7.0. there are 
simply too many ways to give a key id
http://www.gnupg.org/documentation/manuals/gnupg-devel/Specify-a-User-ID.html

..ede/duply.net


On 08.03.2014 20:59, Joachim Wiedorn wrote:
> Hello Edgar,
> 
> I got a bugreport about duply because of long gpg keyIDS:
> 
> 
> ---- original message ----
> From: Erwan David <[email protected]>
> Date: Wed, 29 Jan 2014 14:08:46 +0100
> To: Debian Bug Tracking System <[email protected]>
> 
> Subject: Bug#737024: duply : no support for long gpg keyIDs
> 
> 
> Package: duply
> Version: 1.5.10-1
> Severity: normal
> 
> When I configure duply using a long gpg keyID I get the error :
> 
> duply general bkp --preview
> Start duply v1.5.10, time is 2014-01-29 14:06:49.
> Using profile '/etc/duply/general'.
> Using installed duplicity version 0.6.22, python 2.7.6, 
>   gpg 1.4.16 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1', 
>   bash '4.2.45(1)-release (x86_64-pc-linux-gnu)'.
> 
> Sorry. A fatal ERROR occured:
> 
> GPG key '0XB5A4F21D6CB95BE4' set in 'GPG_KEYS_ENC' is not 
> a valid 8 character hex digit string e.g. '012345AB'.
> 
> 
> However gpg knows this key :
> 
> gpg --list-key 0xB5A4F21D6CB95BE4
> pub   4096R/E40FFD0F 2013-09-23
> uid                  Erwan David <[email protected]>
> sub   4096R/6CB95BE4 2013-09-23
> 
> 
> short keyIDs have a risk of collision, thus it would be better 
> if duply allowed this use.
> 
> 
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing-proposed-updates
>   APT policy: (900, 'testing-proposed-updates'), (900, 'testing'),
>     (800, 'stable'), (500, 'proposed-updates'), (400, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages duply depends on:
> ii  duplicity  0.6.22-2
> ii  gnupg      1.4.16-1
> 
> duply recommends no packages.
> 
> Versions of packages duply suggests:
> ii  openssh-client  1:6.4p1-2
> 
> -- no debconf information
> 
> 
> ---
> Have a nice day.
> 
> Joachim (Germany)
> 


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to