Ticket Change Details
Not logged in
Overview

Artifact ID: 4146298e779c0709effa52a0f86a03af303e2763
Ticket: 8b46db87f1bfa942b48169ef7a8e8d69df8bd2d5
fossil update reporting 'login failed' despite local repo having a password for the account used
User & Date: aku 2010-11-12 21:42:07
Changes

  1. comment changed to:
    I made my first commit to fossil in a long time, and started from a fresh clone.
    1. So, to be able to push I did:
         fossil push http://aku@www.fossil-scm.org/fossil
         typed the password, and of I went.
       OK
    
    2. Later I ran
         fossil update
       and got back:
        Autosync:  http://aku@www.fossil-scm.org/fossil
                        Bytes      Cards  Artifacts     Deltas
        Sent:             193          3          0          0
        Error: login failed    fossil: 
       BAD
    
    3. I should note, when I do a
         fossil pull
       I get asked for the password again, and then the pull works.
    
    I suspect that something is wrong with the local password storage, or how it is used by the transfer code. ... Looking into the user table gossil has stored a HASH of my password ... The last-sync-url contains my user name ... Oh, it is some mismatch between client and server about password vs hash usage.
    
    While this can have a severe impact on usability I decided to set the priority of this ticket only to important because of 3.
    
    Last note: I ran a 'fossil rebuild' and the the above again, this had no effect on the problem.
    
  2. foundin changed to: "d0753799e4"
  3. private_contact changed to: "194c9ef8edbd9a57ef36f4f18fde1d57ce26e1e5"
  4. severity changed to: "Important"
  5. status changed to: "Open"
  6. title changed to:
    fossil update reporting 'login failed' despite local repo having a password for the account used
    
  7. type changed to: "Incident"