david@xxxxxxx wrote: > > as a security person who doesn't like how ssh is used for everything, > let me list a couple of concerns. > > ssh is default allow (it lets you run any commands), you can lock it > down with effort. > > ssh defaults to establishing a tunnel between machines that other > network traffic can use to bypass your system. yes I know that with > enough effort and control of both systems you can tunnel over anything, > the point is that ssh is eager to do this for you (overly eager IMHO) > > ssh depends primarily on certificates that reside on untrusted machines. > it can be made to work with tokens or such, but it takes a fair bit of > effort. > > sshd runs as root on just about every system > > people trust ssh too much. they tend to think that anything is > acceptable if it's done over ssh (this isn't a technical issue, but it > is a social issue) > > > what would I like to see in an ideal world? > > something that runs as the git user, does not enable tunneling, and only > does the data transfer functions needed for a push. it should use > off-the-shelf libraries for certificate authentication and tie into PAM > for additional authentication. How about a git-specific deployment/configuration of ssh? You can certainly run multiple copies of SSH (on different ports), by providing a restricted configuration file you can disable tunneling and any other functionality that you don't like. And if you want it to run as a non-root user, simply choose a port>1024, but keep in mind that you won't be able to authenticate by password (IIRC, only key auth will work when running non-root), or setuid to those users when they log in. Nonetheless, this could be sufficient for gitosis, since everything runs as the specified user anyway, and IIRC, gitosis wants individual SSH pubkeys to allow access. > the authentication would not be any better than with SSH, but the rest > would be better. I was very pleased to watch the git-daemon development, > and the emphisis on it running with minimum privilages and provide just > the functionality that was needed, and appropriately assuming that any > connection from the outside is hostile until proven otherwise. In another mail, David wrote: > 1. if you are running multiple different applications that all want > to be exposed via port 22 (like git for 'git push') then you may need > to expose numerous machines. tools that use SSH don't tend to have the > ability to use a gateway box before they start executing commands, > they assume that you will SSH directly into the destination box. In many cases, especially if the tool is unix based, you can specify (in ~/.ssh/config) a Proxy command that is executed before the SSH protocol negotiation begins, which results in stdin and stdout being connected to the SSH daemon at the destination. The most common variations are the HTTP and Socks proxy connectors (e.g. corkscrew?), but the sky is really the limit in terms of what is possible. Rogan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
