On Wed, Jul 10, 2013 at 10:32:26PM +0200, Rene wrote: > On 2013-07-10 21:31, Martin Gagnon wrote: > >On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: > >>Folks, > >> > >>As I mentioned before, I've been attempting some modifications > >>to the > >>fossil SSH URL handling. I'm at a point where I could use some > >>feedback > >>regarding the previous method for handling SSH. > >> > > [snip] > > > > > >I like the idea to have new ssh implementation that don't depend on > >shell and to have capability to use ssh protocol without using > >accounts > >with shell access. But I think there's still have some work and test > >that need to be done on this implementation. > > > >I tried your patch, I don't know if I'm missing something but it > >doesn't work for me... I made a simple test in the same way I was > >using > >ssh:// protocol before, without using SSH keys restrictions and I got > >following results: > > > > 1- Some new line are missing when asking for password, so I'm > > typing password over the first line of sync status output. > > > > (I guess this is not a problem when using ssh keys > > but output should still be correct when using > > password) > > > > 2- Clone return with no warning or error right away with 0 > > artifact sent and 0 artifact received and I end up with a > > empty fossil file and a fossil-journal file.. > > > > (On OpenBSD 5.3 amd64) > > > >Exact same command with non-patched fossil work. > On linux (arch) it works. Now if i lower my credentials i'm not > allowed to write! > > I had no problem typing the password. even if i botch my first one! > fossil clone > ssh://renez@arch:22/src/fossil/myclone.fossil?fossil=bin/fssh > new2.fsl > ssh -e none -T renez@arch > renez@arch's password: > Permission denied, please try again. > renez@arch's password: > Round-trips: 6 Artifacts sent: 0 received: 21510 > Clone finished with 1592 bytes sent, 28967314 bytes received > Killed by signal 2. > Rebuilding repository meta-data... > 100.0% complete... > project-id: CE59BB9F186226D80E49D1FA2DB29F935CCA0333 > admin-user: renez (password is "4b8994") >
Cloning the repo work with orignal fossil using http:// protocol, so nobody can clone it.. Here some experiments: - try 1: normal fossil, clone throught http: ----------------------------------------- me@myserver(~/test) $ fossil clone http://10.0.0.1/repo/common common1.fossil Round-trips: 12 Artifacts sent: 0 received: 3120 Clone finished with 2888 bytes sent, 75949538 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: fae69cd7d6c31a88295fa9c9d984b9483faac0ac admin-user: me (password is "6e3c63") - try 2: normal fossil, clone throught ssh: ----------------------------------------- me@myserver(~/test) $ fossil clone ssh://me@10.0.0.1//fossil/common.fossil common2.fossil ssh -e none -T me@10.0.0.1 me@10.0.0.1's password: Round-trips: 12 Artifacts sent: 0 received: 3157 Clone finished with 2994 bytes sent, 75953950 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: fae69cd7d6c31a88295fa9c9d984b9483faac0ac admin-user: me (password is "4ff602") - try 3: patched fossil, clone throught ssh: ----------------------------------------- (Notice on output that it ask password on same line as sync status output, but we can see that artifact received and sent are 0) $ fossil2 clone ssh://me@10.0.0.1//fossil/common.fossil common3.fossil ssh -e none -T me@10.0.0.1 fossil http /fossil/common.fossil me@10.0.0.1's password: nt: 0 received: 0 Now, if I list my 3 cloned repos: (common3.fossil have the journal file and is a lot smaller that it should be..) me@myserver(~/test) $ ls -ltrh total 336800 -rw-r--r-- 1 me me 79.7M Jul 10 17:11 common.fossil -rw-r--r-- 1 me me 79.7M Jul 10 17:13 common2.fossil -rw-r--r-- 1 me me 14.5K Jul 10 17:13 common3.fossil-journal -rw-r--r-- 1 me me 4.7M Jul 10 17:13 common3.fossil -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users