Version 2.26: Pull before Sync after writing commit

(1) By Alex Canales (nales0) on 2025-05-20 06:54:16 [link] [source]

Before version 2.26 every time I did a commit I had to insert two times my password.

Once before writing the commit for a "Pull".
Once after writing the commit for a "Sync".

Since version 2.26 every time I do a commit I have to insert three times my password.

Once before writing the commit for a "Pull".
Once after writing the commit for another "Pull".
Once after writing the commit for a "Sync".

Is this new "Pull" just before the "Sync" an expected behaviour in this new version?

(2.2) By Andy Bradford (andybradford) on 2025-05-21 17:29:53 edited from 2.1 in reply to 1 [link] [source]

> Is this  new "Pull" just  before the  "Sync" an expected  behaviour in
> this new version?

That's  hard to  say. What  version were  you on  previously? What  sync
method are you using? SSH or HTTP?

When the check-in  locking functionality was implemented,  this added an
additional sync  which would prompt for  a password if you  aren't using
SSH  keys or  don't allow  Fossil to  store your  credentials for  HTTP.
Specifically it may be this commit:

https://fossil-scm.org/home/info/18d588015bd508c5

Andy

(3) By Alex Canales (nales0) on 2025-05-21 16:53:08 in reply to 2.1 [link] [source]

I am using HTTPS and I do not allow Fossil to store my credentials. I set autosync to "true". I think the behaviour changed when moving from 2.25 to 2.26. I have just tried to commit with my Fossil client on 2.25 and my Fossil server on 2.26, and the new behaviour is still there. I did not rollback the Fossil server version to 2.25 for a test.

Thank you for pointing the commit. If this is not a bug, I think I will just live with that or turn-off autosync.

(4) By Richard Hipp (drh) on 2025-05-21 17:04:15 in reply to 3 [link] [source]

Ubuntu has some kind of daemon process that remembers your SSH credentials after typing them in the first time for each login session. So, in other words, the first time you invoke "ssh", you do get asked for a password to unlock your private key. But just that one time. It thereafter remembers your private key password (in memory) until you log out, or maybe for a fixed interval.

Seems like something like that would work well for you.

(6) By Warren Young (wyoung) on 2025-05-21 21:55:24 in reply to 4 [link] [source]

some kind of daemon process that remembers your SSH credentials

I expect that's ssh-agent, a stock part of OpenSSH. (That, or a GNOME wrapper around same.)

For those who don't like that option, the SSH agent interface is a de facto standard now implemented by several others, notably the major password managers,¹² which allows you to have your SSH keys unlocked by the same mechanism that protects the rest of your digital credentials.

^{^} https://bitwarden.com/help/ssh-agent/
^{^} https://developer.1password.com/docs/ssh/agent/

(5.2) By Andy Bradford (andybradford) on 2025-05-21 17:26:14 edited from 5.1 in reply to 3 [link] [source]

> If this is  not a bug, I think I will just  live with that or turn-off
> autosync.

You  could set  autosync  to  "pullonly". At  least  then  you would  be
prompted only  once when autosync  pulls in  changes to keep  your local
copy updated. You would then have  to use "fossil push" or "fossil sync"
when you're ready to be prompted more than once.

Andy

(7) By Alex Canales (nales0) on 2025-05-23 16:24:05 in reply to 5.2 [source]

Thank you Andy, Richard and Warren for your help on this issue. I will check out those solutions.