social.anoxinon.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Die offizielle Mastodon Instanz des Vereins Anoxinon e.V.

Serverstatistik:

1,1 Tsd.
aktive Profile

Codeberg.org

If there was malicious code in a legitimate project hosted on , would we remove access to it, including for security researchers?

Short: No!

We are considering how to prevent fetching malicious code by accident, though.

In any case, we are open to collaborating with security researchers. Interested? Help us build a malware hunting team: codeberg.org/Codeberg/Contribu

Background: locked access to source code of xz, which was background of active investigation from the community.

Codeberg.org[Team] Malware hunting### About the team This is an idea in case someone is interested to get involved with this topic. Codeberg is abused for spreading malware, like many other places. It is certainly interesting, because a lot of malware we see is either new. We're somewhat close to the source. We have some s...

To people looking for an archive of the XZ code, you might want to check out tukaani.org/xz-backdoor/ which links to git.tukaani.org/. GitHub is not the only source of truth, although meta information about the Pull Requests is locked in to this silo.

tukaani.orgXZ Utils backdoor

@Codeberg Many thanks for your work on openess. It's another proof that git history is not sufficient and we cannot tolerate a locked silo like Github. PR, issues, comments and everything else are an essential part of the repository, the code is not enough.

@Codeberg One idea I have for preventing accidental fetches of malicious code would be to prevent access through the primary domain, and require the use of a seperate (sub)domain such as [caution.codeberg.org](caution.codeberg.org), or [codeberg-caution.org](codeberg-caution.org). Weither this is done throgh a seperate instance it is cloned to, or via special handeling in the forejo would be up to debate.

@Codeberg I think it makes sense to block vanilla git clone and the download buttons to prevent people from accidentally packaging or installing it.
I think what I would do is something like requiring the use of a special URL in order for clones to succeed.

@Codeberg
Good question... Maybe prevent direct git access for non-contributors and show a banner on the website (where you could still downlad the repo)? There shiuld also be a system to let the maintainers request to get out of this state to allow automated build systems to build the fixed version.

@Gusted @Codeberg so hand-wavy guesstimates are enough reason for deleting repositories under the guise of "we have to because THE LAW!!1" while malware, something which is illegal to host as well isn't?

😹

@bonifartius @Codeberg I wouldn't joke like that about the law considering why it was removed. For malware there's legitimate interest for a select group of people to have access to it and use it for research purposes. Which *going back to topic* is being asked here if that should be allowed or not and if so, how. If I understand you correctly, it shouldn't be possible to have any access to the malware just like with any other unlawful repositories on Codeberg.

@Gusted @Codeberg
the malware repository should of course be available. there is no "select group" with free software, no matter if it contains malware or not.

i'm just really not liking that codeberg now tries to do some quick advertising around this when they in other cases just delete repositories on a whim, without good reason, without process.

crimeflate was removed because of the thread of anti hate crime law alone. it was all proactively. a list of people _publicly supporting cloudflare_.

if supporting cloudflare is something so bad that appearing on a list is dangerous, they shouldn't do it. at least that's the logic when things like lists are targeting people on the wrong political side. _those_ lists are totally 👌 of course.

from what i see, these laws i shouldn't joke about _are_ the joke.

@bonifartius @Codeberg Okay thank you for the feedback on that matter. It's an interesting takeaway to see this is as advertisement as we've done this to collect feedback for when this does hit Codeberg, we see that what GIthub did is not the best way forward, hence asking what people think about the best way to handle such cases.

I am not that close with the details of the crimeflare to add or respond to what you've said.

@Gusted @Codeberg
> If there was malicious code in a legitimate project hosted on #codeberg, would we remove access to it, including for security researchers?
>
> Short: No!

this 💯 reads like written by a sales person leveraging the moment.

which in theory would be fine by me. even if i'm no fan of advertising.

i want consistency. deleting repositories because of vague legal problems maybe happening in one case and now advertising "we wouldn't delete malware" isn't, as malware clearly is illegal as well.

@Codeberg @necrosis If you don't want people to fetch malicious code by accident:

* create a branch for security researchers to work on (a tag would actually be sufficient, but branches are even easier in git)
* create a commit on the main branch removing everything except a README.md explaining the situation

@dentaku @Codeberg @necrosis or move the repo to a special user, thus saving all the data, not just specific branch.

@Codeberg Do you have a process to lock those projects from tampering?