"David C. Rankin" <drankinatty@xxxxxxxxx> wrote: > I too am stuck. It's a damned if you do, damned if you don't Hobson's choice > of git repo ownership on the server. All worked fine serving both https and > ssh prior to the change, now it is either one or the other but not both. So > either your read-only pulls and clones are hosed, or your read/write are. Thanks for the reply. I guess I'm potentially not as stuck as you, because I don't require ssh access to the repos - they are just mirrors. I have one unix user that updates the repository, and the cgit and git https backends run as another suexec user exclusively for that task. However, I'm not going to compromise security by giving the web user effective write-access to the files it only needs read access to. > If more info is needed, let me know and I'm happy to privide it. If you have any solution, I'd be grateful to hear. I'm a bit puzzled to what's going on though.
