Blob

Date:
Message:
introduce gotd(8), a Git repository server reachable via ssh(1) This is an initial barebones implementation which provides the absolute minimum of functionality required to serve got(1) and git(1) clients. Basic fetch/send functionality has been tested and seems to work here, but this server is not yet expected to be stable. More testing is welcome. See the man pages for setup instructions. The current design uses one reader and one writer process per repository, which will have to be extended to N readers and N writers in the future. At startup, each process will chroot(2) into its assigned repository. This works because gotd(8) can only be started as root, and will then fork+exec, chroot, and privdrop. At present the parent process runs with the following pledge(2) promises: "stdio rpath wpath cpath proc getpw sendfd recvfd fattr flock unix unveil" The parent is the only process able to modify the repository in a way that becomes visible to Git clients. The parent uses unveil(2) to restrict its view of the filesystem to /tmp and the repositories listed in the configuration file gotd.conf(5). Per-repository chroot(2) processes use "stdio rpath sendfd recvfd". The writer defers to the parent for modifying references in the repository to point at newly uploaded commits. The reader is fine without such help, because Git repositories can be read without having to create any lock-files. gotd(8) requires a dedicated user ID, which should own repositories on the filesystem, and a separate secondary group, which should not have filesystem-level repository access, and must be allowed access to the gotd(8) socket. To obtain Git repository access, users must be members of this secondary group, and must have their login shell set to gotsh(1). gotsh(1) connects to the gotd(8) socket and speaks Git-protocol towards the client on the other end of the SSH connection. gotsh(1) is not an interactive command shell. At present, authenticated clients are granted read/write access to all repositories and all references (except for the "refs/got/" and the "refs/remotes/" namespaces, which are already being protected from modification). While complicated access control mechanism are not a design goal, making it possible to safely offer anonymous Git repository access over ssh(1) is on the road map.
Actions:
History | Blame | Raw File
1 .PATH:${.CURDIR}/../lib ${.CURDIR}/../gotd

3 .include "../got-version.mk"

5 PREFIX ?=	/usr/local

6 BINDIR ?=	${PREFIX}/bin

8 PROG=		gotsh

9 SRCS=		gotsh.c error.c pkt.c sha1.c serve.c path.c gitproto.c \

10 		imsg.c pollfd.c reference_parse.c

12 MAN =		${PROG}.1

14 CPPFLAGS = -I${.CURDIR}/../include -I${.CURDIR}/../lib -I${.CURDIR}/../gotd

16 .if defined(PROFILE)

17 LDADD = -lutil_p -lz_p -lm_p -lc_p -levent_p

18 .else

19 LDADD = -lutil -lz -lm -levent

20 .endif

21 DPADD = ${LIBZ} ${LIBUTIL}

23 .if ${GOT_RELEASE} != "Yes"

24 NOMAN = Yes

25 .endif

27 realinstall:

28 	${INSTALL} ${INSTALL_COPY} -o ${BINOWN} -g ${BINGRP} \

29 	-m ${BINMODE} ${PROG} ${BINDIR}/${PROG}

31 .include <bsd.prog.mk>