pan creates PEM certificates in my home directory with garbage filenames

Bug #1012985 reported by ais523
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pan (Ubuntu)
New
Undecided
Unassigned

Bug Description

In my home directory, several PEM certificates were created, mostly with the same content (I've only observed two different versions). Both of the versions I've seen, when un-base64-ed, appear to be certificates for my news server; I haven't been accessing it (over any protocol) via any application but pan, so it must be to blame. (I haven't caught the files in the act of being created, though.) The names strongly look like uninitialised data. (I moved the certificates out of my home directory to avoid clutter, but kept the files around for further testing):

$ ls -b1 ~/garbage_pem_files/
\ \ \ \
-
\002
\004
\025
\2404\226
ml
operation_block_and_unref:\ 0x972bec0:\ done
process.binary
@\327\020\266\220Q\021\266\025
\274r\002
ral
top_general
ب

I run Pan from the launcher, meaning that its working directory is my home directory, so it's possible it's creating them in the working directory instead. It doesn't seem to create the files on every run, either; the bug's intermittent. (It has been crashing unexpectedly from time to time too, which might or might not be relevant; next time it crashes, I'll check to see if a PEM file was created.)

Possibly relevant options: "Use Secure SSL Connections" and "Always trust this server's certificate" on the only news server it's configured to use.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: pan 0.136-1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic i686
ApportVersion: 2.0.1-0ubuntu9
Architecture: i386
Date: Thu Jun 14 06:36:33 2012
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pan
UpgradeStatus: Upgraded to precise on 2012-04-26 (48 days ago)

Revision history for this message
ais523 (ais523) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.