Thus said Richard Hipp on Mon, 05 Aug 2013 19:42:12 -0400:
That's the way it used to work. I think Andy's changes fix it so
that it doesn't work that way any more. I'm disappointed too, and
would like to find a solution that works both ways.
Ok, I've reimplemented the original
Hello,
Last week I sent out an email regarding the new SSH changes, which I
believe are ready to go:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg12579.html
I have been using it and it feels stable. There has only been one change
since then (cleans up output during
On Mon, Aug 5, 2013 at 1:47 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
Hello,
Last week I sent out an email regarding the new SSH changes, which I
believe are ready to go:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg12579.html
I have been using it and it
Thus said Richard Hipp on Mon, 05 Aug 2013 16:21:05 -0400:
I just tried it, and it is different, isn't it. :-|. Let me mess
around some and see if I can live with the change. Apparently, I'll
need to get real familiar with --ssh-fossil-user
Yes, it's a bit different becuase now
Thus said Andy Bradford on 05 Aug 2013 14:40:08 -0600:
Addtionally, it is now possible to use SSH keys and Force Commands to
restrict the SSH account to doing Fossil only activities.
s/possible/easier/
It was always possible to write a wrapper script, but it's much easier
if fossil is the
On Mon, Aug 5, 2013 at 4:40 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
Thus said Richard Hipp on Mon, 05 Aug 2013 16:21:05 -0400:
I just tried it, and it is different, isn't it. :-|. Let me mess
around some and see if I can live with the change. Apparently, I'll
need to get
Unfortunately even though I'm very interested I haven't had time to look
closely at this new ssh approach. Is the following use case possible to
implemen with your code? I ask because I hear some emphasis on the
many-to-one mapping and I'm interested in one-to-one mapping.
Each person given
Thus said Richard Hipp on Mon, 05 Aug 2013 19:42:12 -0400:
Once I have my ssh key entered I should be able to do all operations
(clone, sync, commit etc.) without entering my password but the
remote fossil knows who I am.
That's the way it used to work. I think Andy's changes fix
Thus said Andy Bradford on 05 Aug 2013 22:42:44 -0600:
It would be better if I didn't have to rely on a script for this,
which is why I thought a new fossil subcommand would be useful. This
would mean all I have to put into my command= is something like:
Ok, scratch that. I've already
9 matches
Mail list logo
