Thus said Matt Welland on Sat, 01 Feb 2014 08:52:56 -0700: > In my opinion fossil should prompt the user for username/password as > appropriate on receipt of a 401. If the channel is not ssl then a > warning/are you sure would be a good idea.
Please try the latest from the http-auth branch: http://www.fossil-scm.org/index.html/info/d581ef0057 It now prompts instead for the Basic Authorization which means it can also be different: $ fossil clone http://u...@host.dom/project project.fossil password for user: remember password (Y/n)? y host.dom requires Basic Authorization over unencrypted HTTP. Use Fossil username and password (y/N)? n Basic Authorization user: httpuser HTTP password for httpuser: Retype new password: Remember Basic Authorization credentials (Y/n)? y Round-trips: 2 Artifacts sent: 0 received: 38 Clone finished with 898 bytes sent, 6778 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 018a5f218fdfcaa7400b355e2dc9b8c7c9959588 admin-user: user (password is "f33ecd") I believe this is better than making assumptions in response to 401. Andy -- TAI64 timestamp: 4000000052f04962 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
