There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Data from deleted GitHub repos may not really be deleted

Researchers at Truffle Security have found, or arguably rediscovered, that data from deleted GitHub repositories (public or private) and from deleted copies (forks) of repositories isn’t necessarily deleted.

Joe Leon, a security researcher with the outfit, said in an advisory on Wednesday that being able to access deleted repo data – such as APIs keys – represents a security risk. And he proposed a new term to describe the alleged vulnerability: Cross Fork Object Reference (CFOR).

“A CFOR vulnerability occurs when one repository fork can access sensitive data from another fork (including data from private and deleted forks),” Leon explained.

For example, the firm showed how one can fork a repository, commit data to it, delete the fork, and then access the supposedly deleted commit data via the original repository.

The researchers also created a repo, forked it, and showed how data not synced with the fork continues to be accessible through the fork after the original repo is deleted. You can watch that particular demo.

Fijxu ,

Classic microsoft. Use other git instances please. If you want actions you can use any public Forejo instance.

richieadler ,

You mean Forgejo?

Fijxu ,

Yes, forgejo. My hands are cold :s

sugar_in_your_tea ,

Fun fact, it comes from the Esperanto: forĝejo. Try typing that with cold fingers. :)

eager_eagle ,
@eager_eagle@lemmy.world avatar

that’s a direct cause of how forks work, it most likely predates microsoft’s acquisition

AdamEatsAss ,

Oh god. That means all the spaghetti code that I ever wrote is still out there.

radivojevic ,

Yup. Along with the code from huge organizations. I always thought it was funny that people put their code online, blindly trusting some random company that got gobbled up by Microsoft.

4am ,

Along with every private key that was accidentally committed.

radivojevic ,

Ha ha, way way back in the day when I didn’t understand how keys worked, I sent a private key to another developer when they asked for my public. They were kind enough to educate me.

sugar_in_your_tea ,

As a lifelong troll, I would’ve just generated a new pub key and made a bunch of commits as you. Then two days later, I would tell you what’s up once you had time to process the confusion.

Chocrates ,

Your point is valid, but many (most?) enterprises don’t use a forking worlflow, so I suspect open source projects will be hit harder, sadly

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •