Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
2014-01-28 James Turner: Thanks for the clarification guys. I'm thinking it's probably safe then to use 1.28 with our 3.8.0.2 version of SQLite. I'll get our in-tree version of SQLite upgraded to the latest after the unlock. Thanks for your feedback. It is highly appreciated! Regards, Jan Nijtmans ___ 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 ui/serv
On Tue, Jan 28, 2014 at 12:46 AM, James Turner ja...@calminferno.netwrote: I dunno either. Everything is fine on my main development machine. I'll chalk it up to a messed up virtual machine I guess. Sorry for the noise. I have seen something similar in the past, could it be a permissions issue on the repo or the containing directory? Mark ___ 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 ui/serv
2014-01-28 Mark Janssen mpc.jans...@gmail.com: I have seen something similar in the past, could it be a permissions issue on the repo or the containing directory? If it's a security issue, this commit could be the coolpit: http://www.fossil-scm.org/index.html/info/b4d538f8c6 I cannot explain how, maybe the check in db.c line 844 should use R_OK in stead of W_OK. It would mean that the configuration db cannot be written, but for a fossil server/ui I wouldn't expect this file to be written anyway. Feedback appreciated! Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil clone / sync / update with Basic Authentication
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
On Tue, Jan 28, 2014 at 10:46 PM, Tal Yardeni tal.yard...@gmail.com 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
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 sgb...@googlemail.com wrote: On Tue, Jan 28, 2014 at 10:46 PM, Tal Yardeni tal.yard...@gmail.comwrote: 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
On Tue, Jan 28, 2014 at 11:28 PM, Tal Yardeni tal.yard...@gmail.com 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
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
[fossil-users] Command line option for HTTP Auth?
Hello, I've just started a branch for exploring a different way to enable the use of HTTP Authorization headers in requests: http://www.fossil-scm.org/index.html/info/e747041a72 Of course, removing the special character as a flag to enable HTTP Auth could potentially break some users who rely on it at the expense of allowing users who might have # as a legitimate first character in their password. Also, I believe this ticket can be closed: http://www.fossil-scm.org/index.html/tktview?name=c46b0f7bb7 Do we envision more than what Fossil currently does? Perhaps Fossil should just automatically detect a 401 and resend the request? I actually looked at doing that and it was obviously simpler to add a command line option. Now I can clone doing something like: $ fossil clone http://amb@www/~andy/fossil/fossil.cgi/new new.fossil password for amb: remember password (Y/n)? y server says: 401 Authorization Required Clone finished with 246 bytes sent, 622 bytes received server returned an error - clone aborted Oops, looks like I need Authorization: $ fossil clone --httpauth http://amb@www/~andy/fossil/fossil.cgi/new new.fossil password for amb: remember password (Y/n)? y Round-trips: 2 Artifacts sent: 0 received: 15 Clone finished with 642 bytes sent, 2720 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 018a5f218fdfcaa7400b355e2dc9b8c7c9959588 admin-user: amb (password is f61fa3) Thoughts? Thanks, Andy -- TAI64 timestamp: 400052e8a6dc ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
