this post was submitted on 24 Jul 2024
218 points (95.4% liked)

Open Source

31253 readers
221 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
218
Anyone can Access Deleted and Private Repository Data on GitHub (trufflesecurity.com)
submitted 3 months ago by [email protected] to c/[email protected]
41 comments fedilink hide all child comments
top 41 comments
sorted by: hot top controversial new old
[–] [email protected] 79 points 3 months ago* (last edited 3 months ago) (2 children)

Misleading title.

~~If my thing was public in the past, and I took it private, the old public code is still public.~~

That's... How the Internet works anyway.

Edit: See Eager Eagle's better explanation below.

TL;DR - be careful who you allow to fork your private repos. And if you need to take a public repo, which has forks, private, consider archiving the repo and doing all the new work in a new repo. Which is arguably the reasonable thing to do anyway.

Still a misleading title. This isn't a way to break into all or even most of your private repositories.

[–] [email protected] 29 points 3 months ago (1 children)

That is not exactly what they are saying. You could create a private fork of a public repo and the code in your private fork is publicly accessible.

[–] [email protected] 29 points 3 months ago

I don't think you can create private forks from public repos (the fork is public upon creation). This is more like the opposite:

If there's a private repo that is forked and the fork is made public, further changes to that original private repo become public too, despite the repo remaining private and the fork not being synced.

[–] [email protected] 12 points 3 months ago (1 children)

Misleading title.

The title literally spells out the concern, which is that code that is in a private or deleted repository is, in some circumstances, visible publicly.

What title would you propose?

If my thing was public in the past, and I took it private, the old public code is still public.

The “Accessing Private Repo Data” section covers a situation where code that has always been private becomes publicly visible.

[–] [email protected] 1 points 3 months ago

the title is dyslexic at best

[–] [email protected] 51 points 3 months ago* (last edited 3 months ago) (1 children)

While this is still a massive problem, it does require a public fork at some point. So if you have a private repo that has never had a public fork, you should be safe.

[–] [email protected] 11 points 3 months ago (1 children)

(unforked repos that are forks are also affected.)

[–] [email protected] 7 points 3 months ago (1 children)

Yes, but only in very limited circumstances. If you:

  1. fork a private repo with commit A into another private repo
  2. add commit B in your fork
  3. someone makes the original repo public
  4. You add commit C to the still private fork

then commits A and B are publicly visible, but commit C is not.

Per the linked Github docs:

If a public repository is made private, its public forks are split off into a new network.

Modifying the above situation to start with a public repo:

  1. fork a public repository that has commit A
  2. make commit B in your fork
  3. You delete your fork

Commit B remains visible.

A version of this where step 3 is to take the fork private isn’t feasible because you can’t take a fork private - you have to duplicate the repo. And duplicated repos aren’t part of the same repository network in the way that forks are, so the same situation wouldn’t apply.

[–] [email protected] 4 points 3 months ago

The second situation you listed is incredibly common, as the blog post explains.

[–] [email protected] 15 points 3 months ago (3 children)

Im thinking of self hosting Forgejo one day.

[–] [email protected] 13 points 3 months ago

I do and it is pretty easy with docker compose.

[–] [email protected] 5 points 3 months ago

Does it treat forks differently?

[–] [email protected] -1 points 3 months ago* (last edited 3 months ago) (2 children)

sourcehut is much better if you can pay

Edit: Only repo hosters need to pay. Everything else is free.

[–] [email protected] 15 points 3 months ago* (last edited 3 months ago) (1 children)

I want forgejo for its upcoming federation feature tbh.

[–] [email protected] -1 points 3 months ago (1 children)

Considering that git doesn’t need federation, and email is the grandfather of federation, sourcehut has a working version of it this very moment.

[–] [email protected] 3 points 3 months ago (2 children)

Why the downvotes?

[–] [email protected] 6 points 3 months ago (1 children)

I'd guess because the same argument could be made for the website you're on right now. Why use that when we could just use mailing lists instead?

More specifically: Sure, Git is decentral at its core, but all the tooling that has been built around it, like issue tracking, is not. Suggesting to go back to email, even if some projects still use it, isn't the way to go forward.

[–] [email protected] 3 points 3 months ago (1 children)
  1. Git has bundled tooling to support pushing MRs to mailing lists.
  2. Email is existing infrastructure. I’m the kind of guy who hates the powerbanks solar route and prefer selling excess solar power to the grid instead. This also has the benefit on allowing you to customize your notifications from subscribed repositories however you like.
  3. The reason we’re not on a mailing list is because we have an extra feature mailing lists can’t offer: reacting, be that upvoting, downvoting, or bookmarking/boosting. Meanwhile, you don’t need that on a development forum. You do have editing, though. Hopefully everyone’s using a client that supports undo.
  4. IMO, the slower speed of email makes people think more before they send.
[–] [email protected] 3 points 3 months ago* (last edited 3 months ago) (1 children)

I'm sorry to be blunt, but mailing lists just suck for group conversations and are a crutch that only gained popularity due to the lack of better alternatives at the time. While the current solutions also come with their own unique set of drawbacks, it's undeniable that the majority clearly prefers them and wouldn't want to go back. There's a reason why almost everyone switched over.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

Mailing lists offer everything needed for a discussion: sending words, threading discussion (that’s already better than every competitor!), and receiving words. All of this is done fast with modern email’s push syncing. Sure, it’s not instant messaging, but development discussions shouldn’t be chatty. Sure, it’s not good for voting, but one can and should just link to one of these online polling services that guarantee integrity instead.

[–] [email protected] 3 points 3 months ago* (last edited 3 months ago) (2 children)

Technically you can do everything through email, because everything online can be represented as text. Doesn't mean you should.

PRs also aren't just a simple back and forth anymore: Tagging, Assignees, inline reviews, CI with checks, progress tracking, and yes, reactions. Sure, you can kinda hack all of that into a mailing list but at that point it's becoming really clunky and abuses email even more for something it was never meant to handle. Having a purpose-built interface for that is just so much nicer.

[–] [email protected] 1 points 3 months ago

Why would you need to control these through a mailing list? The maintainers should have accounts (I don't see the point in federating maintainers instead of just discussion, especially when this is self-hostable), and only those with permissions should be setting up labels, assignees, inline reviews, and CI. And yes, sourcehut has a UI for this, though alternatives through email commands are also available.

And no, I do not see the point of reactions. If you really need a vote, use a voting service.

[–] [email protected] 1 points 3 months ago

If you meant receive CI results... just send these via email? Every major platform (Gerrit, GitLab, GitHub, Gitea...) already does that for notifications IIRC.

[–] [email protected] 4 points 3 months ago

In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.

[–] [email protected] 6 points 3 months ago (2 children)

What makes sourcehut better?

From a self-hosting perspective, it looks like much more of a pain to get it set up and to keep it updated. There aren’t even official Docker images or builds. (There’s this and the forks of it, but it’s unofficial and explicitly says it’s not recommended for prod use.)

[–] [email protected] 3 points 3 months ago

It also supports browsing without JavaScript, if that's your thing.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago)

Sourcehut has straightforward much better UI, UX, and features (more than gitea/forgejo but less than GitLab ig). I really dig the subdomain design.

Issues and PRs are conducted through email, essentially making that part federated and signup-less.

I’ve seen many pieces of software that claim to be beta/not used for prod but are actually bedrock solid.

[–] [email protected] 12 points 3 months ago

Damn that's a huge problem

[–] [email protected] 11 points 3 months ago (1 children)

The takeaway is to not use forks if there are changes you want to keep private.

[–] [email protected] 8 points 3 months ago (2 children)

After reviewing the documentation, it’s clear as day that GitHub designed repositories to work like this.

Sounds like they wanted to find a problem but it turned out to be a feature.

[–] [email protected] 9 points 3 months ago

Yeah, pretty much everyone agrees that once something goes to git it lasts forever.

The fact they call out that secret keys must be rotated if committed, makes me think they thought just deleting a commit was enough 🤦

[–] [email protected] 1 points 3 months ago

a problem that is documented is obviously a feature

[–] [email protected] 8 points 3 months ago* (last edited 3 months ago) (3 children)

Just this week I migrated all my repos from github to Gitlab. And only because I can't host my own gits just yet, but will do it soon enough.

[–] [email protected] 5 points 3 months ago (1 children)

I tried but they demanded a phone number and credit card for "verification" and fuck that.

[–] [email protected] 2 points 3 months ago (1 children)

Also endless verification of you have resistfingerprinting on.

[–] [email protected] 3 points 3 months ago

Thats probably what did it. Guess when given the options of let us track you or provide your real identity for us to track you. The option of fucking off is best.

[–] [email protected] 5 points 3 months ago (1 children)

Im using a raspberry pi with a binary installation of Forgejo. Pretty easy to set up if you are comfortable with the terminal.

[–] [email protected] 1 points 3 months ago

I've been migrating all my services hosted in UnRaid to ProxMox these last days, but Forgejo is absolutely on my list of new services to selfhosted. Thanks for the tip bud.

[–] [email protected] 4 points 3 months ago (1 children)

Codeberg is great too

[–] [email protected] 2 points 3 months ago

Yeah, I'm just getting started, and for the life of me, haven't found how to pull the Gitlab repos from it. But I will.