Hi, 04/11/2010 14:09, Richard Hipp wrote: > On Thu, Nov 4, 2010 at 3:52 AM, Hakki Dogusan<dogus...@tr.net> wrote: > >> Hi, >> >> 03/11/2010 23:51, Benjamin Peterson wrote: >>> Richard Hipp<d...@...> writes: >>>> Try setting: >>>> >>>> fossil setting autosync off >>>> >>>> before you do the >>>> >>>> fossil update >>> >>> I actually get this from "fossil clone http://sqlite.org/src";, too. >>> >> >> >> I don't know it is same problem as this but I'm getting something like >> "couldn't login" error too. >> >> In my case >> Server (Ubuntu) with: fossil-linux-x86-20101101142335.zip >> Client (WinXP) with : fossil-w32-20101101142335.zip >> >> If I use >> fossil server reponame.fossil >> instead of >> fossil ui reponame.fossil >> then client successfully sync. >> > > In newer versions of Fossil, the "fossil ui" command binds to the loopback > IP only (127.0.0.1) meaning that it will only see TCP/IP traffic coming from > the local machine. This is a security feature. The "fossil server" command > continues to bind to all IP addresses as it always has. >
(Possibly a stupid question/suggestion, but) Could "fossil ui" be relaxed to allow local addresses? -- Regards, Hakki Dogusan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
