TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Sourceforge Attack: Full Report

38 点作者 billiob超过 14 年前

4 条评论

lysium超过 14 年前
I don't see how this is a 'full report'. For example:<p>&#62; There was a root privilege escalation on one of our platforms which permitted exposure of credentials that were then used to access machines with externally-facing SSH.<p>How are the credentials exposed after escalation? What accounts on the externally-facing SSH machines were used? Why was it a problem that the externally-facing SSH machines could be accessed? Was the access through root accounts? Why do externally-facing SSH machines allow remote root-login?<p>Besides, why can I still download projects when the data validation is still ongoing?<p>Furthermore, the 'full report' does not say anything what SF.net plans about their ssh servers.<p>I understand the SF.net team does its best, but I am not so happy with that report.
评论 #2161117 未加载
评论 #2161357 未加载
nodata超过 14 年前
Sorry, but this is ridiculous:<p>"Our analysis uncovered (among other things) a hacked SSH daemon, which was modified to do password capture. We don’t have reason to [believe] the attacker was successful in collecting passwords."<p>You don't have reason to believe they weren't either. Why write this?
评论 #2161251 未加载
MindTwister超过 14 年前
Interesting read, both regarding the attack vector, actual damage and their current plans to get everything back up and running.
oomkiller超过 14 年前
The number of people whining about CVS support possibly being deprecated is amazing, get with the 21st century people.
评论 #2161669 未加载