Gnome GCR won't unlock p12 certificate with password length > 31 characters

Bug #1400192 reported by Stephen Schrauger
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GCR
Confirmed
Medium
gcr (Ubuntu)
Triaged
Low
Unassigned

Bug Description

I am unable to import a p12 s/mime certificate using gcr if the certificate is encrypted with a password containing 32 or more characters. When trying to unlock the certificate, gcr responds as if the password entered was incorrect.

I imagine somewhere a 32-byte variable is being used for the password string, but that is just a guess.

Process to reproduce:
Export a certificate from Firefox/Thunderbird (or generate your own).
Encrypt it with the password '1234567890123456789012345678901' (31 characters).
Open with gcr and unlock successfully.
Export the same certificate.
Encrypt it with the password '12345678901234567890123456789012' (32 characters).
Open with gcr and unlock. Password is rejected.

1.
Description: Linux Mint 17 Qiana
Release: 17

2.
gcr:
  Installed: 3.10.1-1
  Candidate: 3.10.1-1
  Version table:
 *** 3.10.1-1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

3. I expected the 30, 31, 32, 33, 35, and 40 length passwords to be accepted and the certificate to be imported.

4. Only the certificates with password lengths of 31 characters or fewer were unlocked and imported . Certificates with 32 characters or more resulted in the error message "The password was incorrect" when trying to unlock, even though the password was, in fact, correct.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gcr (Ubuntu):
status: New → Confirmed
Revision history for this message
bl4ckb1rd (diego-amor) wrote :

I confirm the error, gcr-viewer version 3.10.1, i try to open a .p12 with a password with 51 chars.

From console and other apps works ok.

Changed in gcr:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in gcr (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
autostatic (autostatic) 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.