|
2010-11-17
| ||
| 01:39 | • Closed ticket [8b46db87f1]: fossil update reporting 'login failed' despite local repo having a password for the account used plus 1 other change artifact: 6eb76d542f user: aku | |
|
2010-11-12
| ||
| 23:03 | • Open ticket [8b46db87f1]. artifact: a9a8646618 user: aku | |
| 22:54 | • Ticket [8b46db87f1]: 2 changes artifact: 6bd13f8c8a user: aku | |
| 22:12 | • Fixed ticket [8b46db87f1]. artifact: 0b103eec23 user: drh | |
| 22:12 | Wait to record the sync password until after the user has actually entered the sync password. Ticket [8b46db87f1bfa942b] check-in: 328fc92ceb user: drh tags: trunk | |
| 21:42 | • New ticket [8b46db87f1] fossil update reporting 'login failed' despite local repo having a password for the account used. artifact: 4146298e77 user: aku | |
| Ticket Hash: | 8b46db87f1bfa942b48169ef7a8e8d69df8bd2d5 | ||
| Title: | fossil update reporting 'login failed' despite local repo having a password for the account used | ||
| Status: | Closed | Type: | Incident |
| Severity: | Important | Priority: | |
| Subsystem: | Resolution: | Open | |
| Last Modified: |
2010-11-17 01:39:15 15.37 years ago |
Created: |
2010-11-12 21:42:07 15.39 years ago |
| Version Found In: | d0753799e4 | ||
| Description: | ||||
|
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 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: 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. | ||||