Fossil SCM
fossil update reporting 'login failed' despite local repo having a password for the account used
8b46db87f1bfa94…
· opened 15 years, 4 months ago
- Type
- Incident
- Priority
- —
- Severity
- Important
- Resolution
- Open
- Subsystem
- —
- Created
- Nov. 12, 2010 9:42 p.m.
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://[email protected]/fossil typed the password, and of I went. OK
-
Later I ran fossil update and got back: Autosync: http://[email protected]/fossil Bytes Cards Artifacts Deltas Sent: 193 3 0 0 Error: login failed fossil: BAD
-
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 fossil 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 then the above again, this had no effect on the problem.
aku added on 2010-11-12 23:03:20: Thanks Richard. Tried this using the binary built from [328fc92ceb318278b] and the problem with update is gone.
I came to wonder why pull and sync (maybe push) ask for the password tough, given that it is known. The modified 'update' shows that fossil can find the information somewhere for an automatic pull/push cycle.