Thus said Warren Young on Thu, 21 Jan 2016 14:29:53 -0700: > Is there a way to allow public HTTP access to a Fossil repo for > unprivileged users only (anonymous, nobody) but make Fossil refuse to > do anything sensitive over HTTP, to force all such traffic over SSH or > local DB connections?
There are a few ways I can envision accomplishing this. One method would be to not have any user accounts on the public facing HTTP repository. Then setup your SSH access repository location. Finally, configure a cronjob that does ``fossil pull'' into the public facing HTTP repository from the location where SSH access is given. > That is, could I allow anonymous to clone over HTTP, but if you're in > the developer group or have the superuser or admin permissions, you're > forced to use SSH? One thing to remember is that unless you're using SSH keys, there is no way to conveniently box SSH users into ``reader,'' ``developer,'' and other Fossil Privileges and Capabilities. They are all fully privileged. > Yes, I know about putting Fossil behind TLS proxies, but SSH is > basically a zero-effort way to achieve the same end, as long as you > can be sure all privileged users must use it. It's not zero-effort if you want Fossil Privileges and Capabilities enforced on the server. Only if you don't mind that all SSH users have the same privileges is it zero-effort (aside from making sure correct file permissions are configured on the repositories). Andy -- TAI64 timestamp: 4000000056a1a474 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
