On Feb 10, 2016, at 10:13 PM, jungle Boogie wrote:
>
> On 10 February 2016 at 08:57, Warren Young wrote:
>>
>> Someone kept trying to tell me that SSH keys somehow solved this problem,
>> but it wasn’t clear to me why
>
> Can you give an example of this? Perhaps this can be added to the
> Fos
Thus said Warren Young on Wed, 10 Feb 2016 08:50:29 -0700:
> Also, since the OP talked about permissions, isn't HTTP pretty much
> required?
Yes, and the OP is forcing Fossil to use http over SSH, which means
permissions are enforced.
> As came up in a different recent thread, the ssh
Hi Warren, David,
On 10 February 2016 at 08:57, Warren Young wrote:
> On Feb 10, 2016, at 9:23 AM, David Mason wrote:
>>
>> if you use REMOTE_USER in the .ssh/authorized_keys file, you get full
>> enforcement of permissions.
>
> Oh, that finally clears something up for me. Someone kept trying t
On Feb 10, 2016, at 9:23 AM, David Mason wrote:
>
> if you use REMOTE_USER in the .ssh/authorized_keys file, you get full
> enforcement of permissions.
Oh, that finally clears something up for me. Someone kept trying to tell me
that SSH keys somehow solved this problem, but it wasn’t clear to
On 9 February 2016 at 15:56, Andy Bradford wrote:
> Are you allowing REMOTE_USER to work in your Fossils/dmason.fossil?
>
> $ echo "SELECT * FROM config WHERE name = 'remote_user_ok';" | fossil sql
> -R Fossils/dmason.fossil
>
Bingo! I had actually added this to my script last year
fossil s
On Feb 9, 2016, at 1:53 PM, Richard Hipp wrote:
>
> Would it be easier if you configured your server to allow your 160+
> students to clone/push/pull using HTTP? The HTTP protocol is built
> into Fossil and is thus much less sensitive to the idiosyncrasies of
> individual SSH implementations.
A
Thus said David Mason on Tue, 09 Feb 2016 15:34:26 -0500:
> There is a user dmason with capabilities s in the fossil.
Are you allowing REMOTE_USER to work in your Fossils/dmason.fossil?
$ echo "SELECT * FROM config WHERE name = 'remote_user_ok';" | fossil sql -R
Fossils/dmason.fossil
Thanks,
On 2/9/16, David Mason wrote:
> On 9 February 2016 at 15:48, Richard Hipp wrote:
>
>> A Fossil repository is an SQLite database, and you shouldn't create
>> links (symbolic or hard) to SQLite databases.
>>
>
> Understood, but this is a very low-contention server. I'm really just
> using symlinks
On 9 February 2016 at 15:48, Richard Hipp wrote:
> A Fossil repository is an SQLite database, and you shouldn't create
> links (symbolic or hard) to SQLite databases.
>
Understood, but this is a very low-contention server. I'm really just
using symlinks here to demonstrate the problem.
I'll tr
On 2/9/16, David Mason wrote:
> As you may remember, I use fossil to have students submit assignments for
> my courses. Last year it worked well (eventually) with some problems with
> Windows.
>
> I have 160+ students. All of their fossils are made by the same script
> that creates a user with t
On 2/9/16, David Mason wrote:
>
> So I cloned a sample fossil each of the 2 ways
>
> fs clone ssh://cps...@cps506.sarg.ryerson.ca xxx.fossil
> fs clone ssh://cps506.sarg.ryerson.ca/cps506-fossils/xxx.fossil xxx2.fossil
>
> These both reference sym-links to the same fossil file on the server.
>
A
As you may remember, I use fossil to have students submit assignments for
my courses. Last year it worked well (eventually) with some problems with
Windows.
I have 160+ students. All of their fossils are made by the same script
that creates a user with their ID and capabilities:v and a developer
12 matches
Mail list logo
