You can clone with
HTTPS or Subversion.
Right now, anyone can register an account (without passing any kind of CAPTCHA or anything, so bots will overrun the place quickly on a live site) and upload new packages to their heart's content. This is a major risk for several reasons (package installation can do evil stuff with custom build types, easy to use up tons of disk space, etc.)
Of course, nothing can truly solve the security issue, but I suggest the following:
This should be a simple change to the code. The workflow for a package uploader would be:
This is basically the same as the Hackage1 registration process, but a bit easier for the maintainer.
<dcoutts> bgamari, cmccann, elliott: so the auth system in the new design copes ok with package
uploaders, what it does not cover well is casual users who might want to post reviews, vote etc,
but not upload packages
<dcoutts> since you probably want self-registration for those users
<dcoutts> but for uploaders it's sensible to have a human in the loop
<dcoutts> like we do in the current system
<dcoutts> so there's an admin user group who can edit other groups
<dcoutts> ie grant permissions
<dcoutts> elliott, cmccann: right, plus in the new system since there's a per-package uploader
group then unknown users cannot subvert well known names (ie packages)
<dcoutts> so in the new system malicious people can still upload *new* malicious packages
<dcoutts> but cannot subvert e.g. base
An ideal solution would be something like:
That would be nicer, but probably require a lot more coding than the simpler solution.
This is being tracked on the Cabal trac at http://hackage.haskell.org/trac/hackage/ticket/911