5

我在我拥有的共享主机帐户上建立了一个化石存储库。我创建了一个 perl 脚本fossil.pl,它指向我放在网络空间上的一个克隆存储库。我设置了所有正确的权限(755)。当我去fossil.pl时,我得到了网络用户界面。一切都很酷。但是,我在推送方面遇到问题,希望有人能指出我的解决方案。

当我克隆一个存储库时,它会在新克隆的存储库中为我(Toby)设置一个新密码。如果我在不更改密码的情况下在线推送到此存储库,它可以正常工作,我可以将更改从本地计算机推送到在线存储库。但是,一旦我更改了 Toby 的密码(更改为我更容易记住的密码),我就会收到以下错误。

 Bytes      Cards  Artifacts     Deltas Send:           
 1810          9          0          2
 1Server Error: not authorized to write
 fossil: server says: not authorized to
 write

有谁知道为什么会这样?谁知道怎么修它?

4

2 回答 2

6

Fossil recently changed the details of how it saves passwords, which impacted the way authentication is done during clone, push, pull and sync.

One result of that change is that the initial password for the first user account created for you by the clone stores the password the old way, but changing any password updates it to the new way. To force all password records in a repository to use the new method use "fossil test-hash-passwords".

I would verify that both copies of fossil are after that revision, upgrading both ends as needed.

Note that if upgrading to the most recent versions available, you must do "fossil rebuild" on the server (and locally too for any clones) due to changes in the database schema. Since that is always safe to do, it is wise to do it after any upgrade.

于 2010-03-17T00:39:43.363 回答
1

直到最近,用户和密码从未被克隆过。通常,当您克隆时,确保本地密码和远程密码相同,并通过同步进行测试,这通常是一个好主意。

于 2010-02-03T16:32:06.390 回答