Hi,

I've only seen this bug now, sorry about that...

Do you still have this problem? 
It was most probably generated because the configured 'Keyfile location'
in the pidgin-encryption's options was changed at some point, since it
uses the default libpurple dir for storage, unless configured otherwise.

So this bug probably isn't really a bug, but if you think my assumption
is wrong for some reason, please let me know so I can investigate it
further.

Cheers and thanks for the information
Leo

On Mon, 2007-05-21 at 17:59 +0200, Jean-Luc Coulon (f5ibh) wrote:
> Package: pidgin-encryption
> Version: 3.0-1
> Severity: normal
> 
> Hi,
> 
> pidgin doesnt look for id.priv in .purple but in .gaim directory. So it
> complains it cannot change the permissions (.gaim doent exist on my system)
> 
> If I create the .gaim directory then copy id.priv from .purple in it, I've a
> popup saying:
> Bad permissions on key file: id.priv
> Pidgin-encryption will not save keys to a world it group-accessible file.
> 
> (the same apply to the id file)
> 
> id and id.priv was rw-r--r- with my userid/geoup as the owner. I've not set 
> them up myself.
> 
> Regards
> 
> Jean-Luc
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers unstable
>   APT policy: (900, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.22-rc2-k8-1 (PREEMPT)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages pidgin-encryption depends on:
> ii  libc6                     2.5-8          GNU C Library: Shared libraries
> ii  libnspr4-0d               4.6.6-3        NetScape Portable Runtime Library
> ii  libnss3-0d                3.11.5-3+b1    Network Security Service 
> libraries
> ii  pidgin                    2.0.0+dfsg.1-4 multi-protocol instant messaging 
> c
> 
> pidgin-encryption recommends no packages.
> 
> -- no debconf information
> 

-- 
Leo Antunes <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to