One workaround is to open a regular CMD shell on the machine itself (not over ssh).  Do 'fossil remo' or whatever there, then the password etc gets saved and it will subsequently work over ssh.

Not the best solution, but it does work.


On 19/06/2018 21:27, Ron Aaron wrote:

Just today I decided I need to set up a windows build machine, and I put "msys2" on it, with ssh and build tools .  It's great, in general.

However, after having to specify "user:pwd" in the clone URL to get a clone working, I now always have to do that as well on the command-line. Never get prompted for a password, and the password never gets saved.

To clarify: this is on Windows 7 64-bit, running the "msys2" Unixy tools over ssh. 

I note this issue was discussed (exactly the same problem) in 2014 by Michael Weise "Password not saved? Missing or incorrect password..."



Ron Aaron | CTO Aaron High-Tech, Ltd | +1 516.373.0794 / +972 52.652.5543 | GnuPG Key: 91F92EB8


_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Ron Aaron | CTO Aaron High-Tech, Ltd | +1 516.373.0794 / +972 52.652.5543 | GnuPG Key: 91F92EB8

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to