NewPKI Client can't load a PKCS#12 certificate to connect to the PKI.

Bug #475249 reported by Pirouette Cacahuète
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
newpki-client (Debian)
Fix Released
Unknown
newpki-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: newpki-client

The NewPKI Client can't connect using a PKCS#12 file. Once the users has selected the certificate, and entered the (good or bad) passphrase, it issues an error :

« system library #21 is a directory [bss_file.c:198] »

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Attached is a patch that corrects the issue. It should be inserted in the debian/pacthes/wx2.6 patch.

Changed in newpki-client (Debian):
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Actually, there's a small typo in the previous patch. One should replace « char * » with « char* ».

Anyway, I'm adding a patch for the wx2.6 package patch :=)

Changed in newpki-client (Debian):
status: Unknown → New
Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

After playing a bit with my new working newpki-client, I noticed that
the « remember my PKCS#12 file » feature was also broken.

That is, once you load you certificate and connect to the PKI, a file
~/.newpki/client_pki is written with the informations you used to login
(server, port, entity, and certificate).

Currently, the same bug happens when writting this file than what
prevented us to open the certificate.

I join a full patch for the debian package's wx2.6 compatibility patch,
that also corrects this behavior. This patch includes the first one.

Have fun.

Changed in newpki-client (Debian):
status: New → Fix Released
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.