I'm seeing some kind of authentication failure when trying to sync local
with remote over SSH.

Given a user account "foo":

    $ fossil clone http://[email protected]:4444/test test.fsl
    password for foo: 
    remember password (Y/n)? n
    Round-trips: 1   Artifacts sent: 0  received: 0
    *** time skew *** server is fast by 20.4 seconds
    Round-trips: 2   Artifacts sent: 0  received: 1
    *** time skew *** server is fast by 20.3 seconds
    Round-trips: 2   Artifacts sent: 0  received: 3
    Clone finished with 540 bytes sent, 1162 bytes received
    Rebuilding repository meta-data...
      100.0% complete...
    project-id: 4f2339b57d865b43d48c3c6dccd0f989f0544860
    admin-user: foo (password is "eba680")
    foo@glaze:/usr/home/foo/tmp/shared $ cd ../src/test/
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil open ../../shared/test.fsl 
    foo@glaze:/usr/home/foo/tmp/src/test $ echo '# DO NOT READ ME' > README
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil add README 
    ADDED  README
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil commit -m 'added README'
    Autosync:  http://[email protected]:4444/test
    Round-trips: 1   Artifacts sent: 0  received: 0
    missing or incorrect password for user "foo"
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil setting autosync off
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil commit -m 'added README'
    New_Version: 2360769f27be6e03e22dcec699200ca10383adb5
    foo@glaze:/usr/home/foo/tmp/src/test $ fossil push
    password for foo: 
    remember password (Y/n)? n
    Push to http://[email protected]:4444/test
    Round-trips: 1   Artifacts sent: 2  received: 0
    Error: not authorized to write
    Round-trips: 1   Artifacts sent: 2  received: 0
    Push finished with 548 bytes sent, 277 bytes received

So . . . I'm guessing the autosync fail is due to it assuming the local
Fossil admin user's password being randomly set at the time the
repository is cloned, easily solved by turning off autosync (which I
don't want on for this anyway -- it would really screw with workflow).

It still fails after that, though, with an authorization error:

    Error: not authorized to write

Is there some way to give the account write authorization from the
command line on the server?  I don't see anything in the output of
"fossil user help", and what I've found about this error in web searches
doesn't seem to apply to my case (involving mismatched Fossil versions,
for instance).

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to