On 02/08/11 02:32, Joost 't Hart wrote: Hi!
> Ahum, > > It's been a while now, and I must admit I am beginning to get > this funny feeling of serious irritation. Indeed. > By way of recapping the original question: What the whack > is going on. From the blog: ---------------------------------------------------------------------- We appreciate your patience. All SourceForge services are operational at this time with the exception of ViewVC and CVS. Interactive shell service was restored today and we expect ViewVC to return today (Monday), barring complications. We intend to have CVS service online by the end of the week. Please note that, aside from CVS, our SCM platforms (Subversion, Git, Hg, Bazaar) have remained online. If you¿re encountering issues with these platforms, please confirm that you have reset your password. If problems persist, please contact our support team (sfnet_...@geek.net). CVS service restore has been time-consuming due to the design of that service. CVS data is housed on direct-attached storage on a small pool of servers. Data restore from backups is in-progress and reload of machines is in-progress as of today (Monday). We intend to have CVS service online by the end of the week. We have concluded our review of SCM data for the SourceForge Beta SCMs and traditional SCM offering (SVN, Git, Hg, Bzr; excepting CVS, whose data is being restored) and have found no indicator of data tampering. We will be providing further data to projects whose repositories were modified in the attack window (we believe legitimately by their project team) as that they may conduct further validation using the repository access provided through interactive shell service. Finally, with the rollout of interactive shell service today, we are completing preparations to start the mass rollout of our new Project Web service offering tomorrow (Tuesday). This work will commence with the migration of projects in the A-G unixname range in a Tuesday/Wednesday timeframe. If you have any questions or concerns, please contact our support team at sfnet_...@geek.net Thank you, The SourceForge Team ---------------------------------------------------------------------- So I think we'll make it till the end of the week. Hopefully. Concerning the move of the repository to some other service, I'm not conviced that this solves the problem. Acutally, sf has be very reliable till now, and tracking down root exploits is a time consuming issue. I don't know if any other service would have been up again that much faster. (At least not at our budget. ;) Call me conservative, but till now sf worked very well all the time, so I do not see why to switch to another hosting service. cu Alexander ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
