Failure to get passphrase right causes "CHECKSUM FILE(S) DISAGREE WITH DIRECTORY LISTING"

Bug #173 reported by Andrew Bennetts on 2005-02-18
2
Affects Status Importance Assigned to Milestone
bazaar (Ubuntu)
Medium
Unassigned

Bug Description

I don't use a gpg agent, so I get prompted twice every commit. This time, with latest cotm baz, I got my passphrase right for the first prompt, but typoed it three times in a row for the second signing, so gpg gave up, causing baz to put my archive in a state where I can't commit to that branch. Full transcript:

----
andrew@trogdor ~/warthogs/code/supermirrorsftp $ baz commit -s "Add comment"
These files would be source but lack inventory ids (`baz add' perhaps?):

keys
samplekey.sql
supermirrorsftp/test

* auto-adding <email address hidden>/supermirrorsftp--devel--0--patch-14 to greedy revision library /home/andrew/arch/revlib
* found immediate ancestor revision in library (<email address hidden>/supermirrorsftp--devel--0--patch-13)
gpg: Good signature from "Andrew Bennetts <email address hidden>"
gpg: Good signature from "Andrew Bennetts <email address hidden>"
* patching for this revision (<email address hidden>/supermirrorsftp--devel--0--patch-14)
M supermirrorsftp/sftponly.py

You need a passphrase to unlock the secret key for
user: "Andrew Bennetts <email address hidden>"
1024-bit DSA key, ID F1A573C9, created 2004-06-22

gpg: Good signature from "Andrew Bennetts <email address hidden>"

You need a passphrase to unlock the secret key for
user: "Andrew Bennetts <email address hidden>"
1024-bit DSA key, ID F1A573C9, created 2004-06-22

gpg: Invalid passphrase; please try again ...

You need a passphrase to unlock the secret key for
user: "Andrew Bennetts <email address hidden>"
1024-bit DSA key, ID F1A573C9, created 2004-06-22

gpg: Invalid passphrase; please try again ...

You need a passphrase to unlock the secret key for
user: "Andrew Bennetts <email address hidden>"
1024-bit DSA key, ID F1A573C9, created 2004-06-22

gpg: no default secret key: bad passphrase
gpg: [stdin]: clearsign failed: bad passphrase
signature command exited with non-0 status (2)

command: gpg --clearsign --default-key <email address hidden>

(You may also have to use tla lock-revision -b before
 retrying this transaction. See tla lock-revision -H)

unable to complete transaction due to signature failure
andrew@trogdor ~/warthogs/code/supermirrorsftp $ baz commit -s "Add comment"
These files would be source but lack inventory ids (`baz add' perhaps?):

keys
samplekey.sql
supermirrorsftp/test

gpg: Good signature from "Andrew Bennetts <email address hidden>"

***********************************

  CHECKSUM FILE(S) DISAGREE WITH
  DIRECTORY LISTING ABOUT WHAT
  FILES SHOULD BE PRESENT IN
  REVISION DIR OF ARCHIVE

  archive: <email address hidden>
  revision: supermirrorsftp--devel--0--patch-15

***********************************

andrew@trogdor ~/warthogs/code/supermirrorsftp $ baz lock-revision -b <email address hidden>/supermirrorsftp--devel--0--patch-15
gpg: Good signature from "Andrew Bennetts <email address hidden>"

***********************************

  CHECKSUM FILE(S) DISAGREE WITH
  DIRECTORY LISTING ABOUT WHAT
  FILES SHOULD BE PRESENT IN
  REVISION DIR OF ARCHIVE

  archive: <email address hidden>
  revision: supermirrorsftp--devel--0--patch-15

***********************************

andrew@trogdor ~/warthogs/code/supermirrorsftp $
----

This happened just after making a commit without any trouble, so I'm pretty certain the mistyped passphrase was the cause.

Christian Reis (kiko) on 2005-07-04
Changed in bazaar:
assignee: sabdfl → nobody
Changed in bazaar:
assignee: nobody → bazaar-developers
Changed in bazaar:
assignee: bazaar-developers → nobody
status: New → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers