[fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Tal Yardeni
I saw some threads on this topic from 2011, but wanted to see if there was
any change or decision since then.

I have fossil repos hosted on an Apache server with REMOTE_USER enabled. If
I attempt to clone via the following commands:

fossil clone https://usern...@fossil.example.tld/repo/test.fossil
test.fossil

The result is:

password for username:
fossil: server says: 401 Authorization Required

Clone finished with 252 bytes sent, 699 bytes received
fossil: server returned an error - clone aborted


I get a 401 error from the web server. I would like to authenticate either
via Basic Authentication or a KRB5 TGT if possible. Any suggestions? I am
not in a position to enable fossil authentication - I need to use the web
authentication due to boundary conditions.

Any help would be appreciated.

Thank you,
Tal Yardeni
Recent Fossil Convert
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Stephan Beal
On Tue, Jan 28, 2014 at 10:46 PM, Tal Yardeni  wrote:

> fossil clone https://usern...@fossil.example.tld/repo/test.fossil
> test.fossil
>

FWIW, all my repos are hosted/cloned this way, but over http, not https,
without problem. i unfortunately can't say anything helpful about the ssl
support, though.


-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Tal Yardeni
Stephan, that is great - I don't think the https/SSL piece is the issue
since the browser is returning the 401 status code as part of the
authentication handshake.

In case it matters (and I should have included this info in the initial
post) we were using the following fossil version:

fossil version 1.25 [d2e07756d9] 2013-02-16 00:04:35 UTC

I recompiled fossil 1.28 with SSL support and still getting same error:

password for username:
remember password (Y/n)? n
server says: 401 Authorization Required
Clone finished with 252 bytes sent, 699 bytes received
server returned an error - clone aborted

Are your repos using the Apache server's authentication or the internal
fossil authentication?

We have no issue authenticating on the web interface, just from the CLI to
the web server.

Thanks,
Tal



On Tue, Jan 28, 2014 at 3:12 PM, Stephan Beal  wrote:

> On Tue, Jan 28, 2014 at 10:46 PM, Tal Yardeni wrote:
>
>> fossil clone https://usern...@fossil.example.tld/repo/test.fossil
>> test.fossil
>>
>
> FWIW, all my repos are hosted/cloned this way, but over http, not https,
> without problem. i unfortunately can't say anything helpful about the ssl
> support, though.
>
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Stephan Beal
On Tue, Jan 28, 2014 at 11:28 PM, Tal Yardeni  wrote:

> Are your repos using the Apache server's authentication or the internal
> fossil authentication?
>

Ah, of course. i'm using Fossil's authentication, which (IIRC) uses
REMOTE_USER via http://name:password@...


> We have no issue authenticating on the web interface, just from the CLI to
> the web server.
>

When run in CLI mode there is _no_ authentication going on. All auth checks
effectively resolve to all permissions in CLI mode.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Andy Bradford
Thus said Tal Yardeni on Tue, 28 Jan 2014 14:46:29 -0700:

> password for username:
> fossil: server says: 401 Authorization Required

It seems that Basic HTTP Authorization  is somewhat of a hidden feature.
When  it prompts  you  for your  password,  you must  prepend  # to  the
password to signal that the connection requires an Authorization header.

Try putting # in front of your password when cloning.

Andy
-- 
TAI64 timestamp: 400052e88b91


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-28 Thread Kees Nuyt
[Default] On Tue, 28 Jan 2014 14:46:29 -0700, Tal Yardeni
 wrote:

>I saw some threads on this topic from 2011, but wanted to see if there was
>any change or decision since then.
>
>I have fossil repos hosted on an Apache server with REMOTE_USER enabled. If
>I attempt to clone via the following commands:
>
> fossil clone \ 
> https://usern...@fossil.example.tld/repo/test.fossil \
> test.fossil
>
>The result is:
>
>password for username:
>fossil: server says: 401 Authorization Required
>
>Clone finished with 252 bytes sent, 699 bytes received
>fossil: server returned an error - clone aborted

Try passing the password in the URL:

fossil clone \ 
http://username:passw...@fossil.example.tld/repo/test.fossil \
test.fossil

, where username and password are fossil username and password.

It works for me with http with fossil behind Apache cgi, I
currently don't have https set up on my Apache installation.

-- 
Groet, Cordialement, Pozdrawiam, Regards,

Kees Nuyt

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil clone / sync / update with Basic Authentication

2014-01-29 Thread Tal Yardeni
Prepending # solved my issue. Tested succsssfully with v1.28 and v1.25

Thanks,
Tal


On Tue, Jan 28, 2014 at 10:02 PM, Andy Bradford <
amb-sendok-1393563762.gjleeofhibmajfjpg...@bradfords.org> wrote:

> Thus said Tal Yardeni on Tue, 28 Jan 2014 14:46:29 -0700:
>
> > password for username:
> > fossil: server says: 401 Authorization Required
>
> It seems that Basic HTTP Authorization  is somewhat of a hidden feature.
> When  it prompts  you  for your  password,  you must  prepend  # to  the
> password to signal that the connection requires an Authorization header.
>
> Try putting # in front of your password when cloning.
>
> Andy
> --
> TAI64 timestamp: 400052e88b91
>
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users