Hi,
No. Only the write access was obviously a giant breach. Giving a read access
is totally normal and is what all open source projects do. When someone has
something to write, he can send you a patch against a known svn revision.
Then you can import the patch by yourself, and make contributors' work
visible, while retaining full control on your server.
Regards
Sebastien
On Fri, Jul 16, 2010 at 12:22 PM, 谢继雷 <x...@99jsj.com> wrote:
> On 2010-7-16 16:34, Sébastien Lorquet wrote:
> > hi,
> >
> > giving away a write enabled svn access on a worldwide public mailing
> > list is not exactly the right way to do it...
> > at least you could make it read only!
> >
> > Do you realize how fast your repository could be screwed with
> > gazillons of useless commits, eating up disk space with huge binary
> files?
> >
> > remove this access ASAP!
> >
> > seb
> Thanks, well though it's not happened, I removed the write permission.
>
> But, as I made the svn address public, there'll be someone hacks into
> the system all the same?
> Then, I should close the SVN and shutdown the server at all, and at last
> I can't do anything at all isn't it?
>
> Thanks for you advice.
>
> Lenik
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Sdcc-user mailing list
> Sdcc-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
