Thus said David Mason on Thu, 25 Jul 2013 18:16:08 -0400:
command=/home/fossilcm/bin/fossil gate otheruser ssh-rsa ...
where the name after gate defines the fossil user that this
represents, and the ... are the public keys from the particular users.
Should this instead
Thus said Alan Barrett on Mon, 29 Jul 2013 08:29:37 +0200:
Regardless of whether this is a good idea or not, please do not call it
fossil gate. Please give it a name that alerts the user to the fact
that it's very closely tied to ssh.
Understood. At this point, it is really just a concept
It appears that gitolite works much like mercurial-server.
What I would expect (I haven't set up fossil yet, because I need this
functionality) is that the authorized_keys file for the fossilcm user
would have:
command=/home/fossilcm/bin/fossil gate admin ssh-rsa ...
Thus said Rene on Sun, 21 Jul 2013 00:00:01 +0200:
A forced command is in place and it can only be fossil http.This will
check if it is started via ssh and then look in the environment to see
if the request was fossil gate myotherdb.
For now, I think I will abandon the idea that this type of
On Sat, Jul 20, 2013 at 3:23 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
[snip]
I'm trying to accomplish what I believe Matt Welland was suggesting it
do, which I did like. Basically, if I have an SSH account named
``fossil'' on my server, I can use it to server out as many
Thus said Matt Welland on Sun, 21 Jul 2013 22:16:42 -0700:
The ssh key is being used to give access only to the fossil file and
yes, the access list would map ssh keys (thus users) to fossils.
Just for clarification... access list would map an SSH key user
to fossils, but not
On Sun, Jul 21, 2013 at 10:09 PM, Andy Bradford
amb-sendok-1377061791.goefgfndahogdhegp...@bradfords.org wrote:
Notice that I'm able to access multiple fossil files with my SSH key and
Fossil account. And, I can install as many SSH keys into the ``guest''
account as I like.
This is a
Hello,
I've been working on a simple fossil command that will integrate with
SSH accounts where SSH keys are in use and wonder if there is a formal
process for coming up with new subcommand names? Here is what I have at
the moment:
$ fossil help gate
Usage: fossil gate ?FILENAME?
On 2013-07-20 23:06, Andy Bradford wrote:
Hello,
I've been working on a simple fossil command that will integrate
with
SSH accounts where SSH keys are in use and wonder if there is a
formal
process for coming up with new subcommand names? Here is what I have
at
the moment:
$ fossil
Thus said Rene on Sun, 21 Jul 2013 00:00:01 +0200:
A forced command is in place and it can only be fossil http.This will
check if it is started via ssh and then look in the environment to see
if the request was fossil gate myotherdb.
what are you trying to archive?
I'm trying to
10 matches
Mail list logo
