Git cvsserver serious issue

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Git cvsserver serious issue
Дата
Msg-id AANLkTikqQFpagRSQ4w+4UjW7W6Bcc3HD+55BLWK4tN=Q@mail.gmail.com
обсуждение исходный текст
Ответы Re: Git cvsserver serious issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Git cvsserver serious issue  (Peter Eisentraut <peter_e@gmx.net>)
Re: Git cvsserver serious issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
So, I found (with some helpful hints from Robert who caught the final
nail in the coffin) a good reason why we really can't run a
git-cvsserver globally.

Any user can point their cvs client at the repository. And check out
an arbitrary branch, tag *or individual commit*. Doing so will create
a 50Mb sqlite database on the server with cache information about that
head.

That basically means that git-cvsserver is completely useless in a
public scenario as it stands. An easier way to DOS our server is hard
to find, really.

Now, if we can limit this by IP address, that would be ok. I assume we
can do this for the NLS stuff - peter?

As for buildfarm members needing CVS - is it workable to require that
the maintainers of these set up their own git clone with git cvsserver
(over ssh or pserver) and restrict it locally to the IP(s) of their
machines?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Multi-branch committing in git, revisited
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Standby registration