More flaws foul security of open-source repository

TalkBack 26 of 55:

Next »

« Previous

• Thread View
• Flat View

RE: From the CVS Project web site

CVS does NOT make any of those remote protocals insecure. Only CVS itself running over those protocals is insecure. Meaning you STILL need access to their site via those protocols to even get close to the insecure CVS. So if those protocals are secure, then you have nothing to worry about. But if you need security against those people who have access via those protocals, THEN you have a problem.

So if you have CVS which only 2 people have access running over a company VPN to which 20 employees have access, then you only have to worry about securing the CVS against those other 18 people (which yes is indeed a problem). And of course if only those 2 people have access to the VPN, then there will be no security breach, unless there is a breach in VPN. But if you have a CVS running over the web, then you have potentially the whole world to secure against.

Posted by: Michael Kelly   Posted on: 06/10/04 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
• Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
• Building the Virtualized Enterprise with VMware Iinfrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now