[fossil-users] strange 'login failed' error on initial repository clone.

[Jeremy Anderson]

Hey everyone. Need a little help...

Problem:
Attempting to clone a recently-created repository gives this error:

D:\f\repo>fossil clone http://user:p...@ec2-xxx.compute.amazonaws.com:6969/hekate d:\f\repo\hekate.fossil

                Bytes      Cards  Artifacts     Deltas
Sent:              53          1          0          0
Received:         341          5          1          0
Sent:              58          2          0          0
Error: login failedxe:
Received:          52          1          0          0
Total network traffic: 667 bytes sent, 819 bytes received
C:\Windows\fossil.exe: server returned an error - clone aborted

(no, user is not the actual username, pwd is not the password, and xxx is not the real machine name)

What I did to set it up:

1. I'm using Fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 to set up a new Fossil server on Win2k8 R2 64-bit (hosted by Amazon's EC2 cloud service).
2. Used this to command create the service instance:         fossil winsrv create -S auto -P 6969 -R c:\repo
1. (c:\repo holds our fossil repository file, hekate.fossil. The repository is currently empty (apart from the initial/default checkin).
3. I've created an admin+setup user for myself (user) and given him a password (pwd) i'm very familiar with.
4. Opened port 6969 for the machine in Amazon's EC2 configuration for this machine
5. Opened the Windows firewall for port 6969.
   

What I know works:

• The repository is visible via the web at the same url as above.
  
• The same credentials (user:pwd) work just fine to log into the repository website.

What i've done to troubleshoot:

• Checked and re-checked the user/pwd combo
• (Successfully) Logged in to the repository from the same machine (via the web) with the same credentials
  

Any thoughts on why I can't clone the repository?

Thanks!

-jer

[Leo Razoumov]

On Tue, Mar 20, 2012 at 02:12, Jeremy Anderson <jer...@gmail.com> wrote:
> Hey everyone. Need a little help...
>
> Problem:
> Attempting to clone a recently-created repository gives this error:
>
> D:\f\repo>fossil clone
> http://user:p...@ec2-xxx.compute.amazonaws.com:6969/hekate
> d:\f\repo\hekate.fossil
>

Could you, please try URL without password like this:

D:\f\repo>fossil clone

http://us...@ec2-xxx.compute.amazonaws.com:6969/hekate
d:\f\repo\hekate.fossil

Now when fossil prompts you for a password type # followed by your password.
'#' prefix tells fossil to use the password (with # removed, of
course) both for your server Basic Authorization and for your fossil
repo.

Please, let the list know whether it helps.

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

[Richard Hipp]

On Tue, Mar 20, 2012 at 2:12 AM, Jeremy Anderson <jer...@gmail.com> wrote:

Hey everyone. Need a little help...

I don't have any good ideas of why this isn't working....

But just for grins, try entering just the username in the URL and let Fossil prompt you for the password.  Maybe there is some bug in the MBCS-to-UTF conversion for passwords typed into URLs or something....
 

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

--
D. Richard Hipp
d...@sqlite.org

[Jeremy Anderson]

I should have mentioned that as well. I get the same error either way. :)

I started with that method and migrated to the http://user:pwd@... approach when I needed to double-check my password for correctness.

[Jeremy Anderson]

Thanks, Leo. You just solved my problem!

The password I was using began with a hash symbol ('#')... adding an additional # (##[password]) got it to work.

Is it just me, or is putting special tokens like that in the password a bad idea? :)

[Leo Razoumov]

On Tue, Mar 20, 2012 at 10:11, Jeremy Anderson <jer...@gmail.com> wrote:
> Thanks, Leo. You just solved my problem!
>
> The password I was using began with a hash symbol ('#')... adding an
> additional # (##[password]) got it to work.
>
> Is it just me, or is putting special tokens like that in the password a bad
> idea? :)
>

Jeremy,
I am glad that this little undocumented trick solved your problem. In
Fossil's login process leading # has a special meaning. If one runs
fossil as a CGI script and the web server requires its own basic
authorization (authentication) prepend an extra # to your password.

In general I would recommend to stay away from special chars like
*^&#* in your password. If you are concerned with your password
security make your password longer. 64^8 is greater than 70^7.

--Leo--