Elektrine
Log in Register

#gitea

20 posts · Last used Sep 27

Codeberg Status @codebergstatus@social.anoxinon.de
· 1mo ago
Boosted by @fedicat@pc.cafe
Replying to
This has been enabled again, please serve this as a reminder to migrate to Codeberg Pages v3! Documentation: https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/ For help & support, make a issue at https://codeberg.org/Codeberg/Community/ or join https://matrix.to/#/#gitea-pages-server:matrix.org
docs.codeberg.org

Migrating from Pages v2 | Codeberg Documentation

19
0
5
0
Patrick @ppb1701@ppb.social
· 3mo ago
Remember when I said my DR setup should have me back up in 20-30 minutes? Yeah. About that. Turns out a backup job can run clean every single night for months and still not actually be backing up what you think it is. So here's what I actually found out the hard way replacing nixos2's dying hardware. Feel free to cue the old "The more you know" clip. https://blog.ppb1701.com/best-laid-plans-replacing-nixos2s-failing-hardware-part-19-of-building-a-resilient-home-server-serie #blog #homeserver #nixos #disasterrecovery #selfhosting #gitea #tailscale
blog.ppb1701.com
2
0
3
0
JTI @jti42@infosec.exchange
· 3mo ago
Replying to
@Codeberg@social.anoxinon.de I did look at some of the initiators/sponsors of the original proposal and did find one of apparent more important maintainers of @forgejo@floss.social and formerly Gitea until it turned "commercial". I wonder if this will lead to yet another fork of what started out as Gogs some probably 10 years ago now. Vibegeo? Vibeforge? Vibedistrict? (Thanks the original author of Gogs back when btw. I was already pretty amazing back when!) Certainly I will refrain from trying to propose (with PRs) a set of extensions to the issue system as said extensions and their raison d'etre have the evil taint of the LLM and hence certainly wouldn't be accepted. 🤷 #gogs #gitea #forgejo
1
0
0
0
Ricard Torres 👨‍💻 @dev@ricard.social
· 3mo ago
Replying to
From a 100 repos to only 20 left on #GitHub for now. I shall continue the purge tomorrow. I was able to add a #Gitea runner with Docker. So now my several #Hugo repositories are already building in Gitea as I push changed, just like they did before on GitHub Actions (also using a shared workflow now). Feels good.
2
6
1
0
OffSequence @offseq@infosec.exchange
· 3mo ago
Gitea <1.27.0 CRITICAL vuln (CVE-2026-58443): Public-only write tokens can update private PR head branches, violating repo access controls. Patch pending — review token use & monitor vendor updates. https://radar.offseq.com/threat/gitea-public-only-repository-tokens-can-update-private-pr-head-branches-cve-2026-58443-d058444d84b9595a #OffSeq #Gitea #Vuln #CVE202658443
radar.offseq.com

Gitea: Public-only repository tokens can update private PR head branches (CVE-2026-58443) - Live Threat Intelligence - Threat Radar | OffSeq.com

Detailed information about Gitea: Public-only repository tokens can update private PR head branches (CVE-2026-58443) affecting null code.gitea.io/gitea. Get rea

0
0
0
0
Daily CyberSecurity @DailyCyberSecurity@infosec.exchange
· 3mo ago
Gitea vulnerability CVE-2026-58443 (CVSS 9.6) lets public-only tokens write to private repos. Details and PoC code are public. Update to v1.27.0. #Gitea #CVE202658443 #DevSecOps #PoC #InfoSec
CVE-2026-58443: Gitea Flaw (CVSS 9.6) Details and PoC Exploit Code Publicly Disclosed
securityonline.info

CVE-2026-58443: Gitea Flaw (CVSS 9.6) Details and PoC Exploit Code Publicly Disclosed

Gitea vulnerability CVE-2026-58443 (CVSS 9.6) lets public-only tokens write to private repos. Details and PoC code are public. Update to v1.27.0.

0
0
1
0
🏳️‍⚧️ Christin Löhner 🏳️‍🌈 @christin@lsbt.me
· 4mo ago
Ein Header genügt: Wie Gitea und Forgejo jedem Fremden die Admin-Rechte schenkten Ein gefälschter HTTP-Header genügte monatelang, um sich in Gitea und Forgejo zum Admin zu machen, ganz ohne Passwort. CVE-2026-20896 hat einen CVSS-Wert von 9.8. Gitea ist seit dem 21. Juni gepatcht, Forgejo hängt weiter in der Luft. Was du an deiner Konfiguration sofort prüfen musst. https://www.chrislo.de/blog/2026-07-14-20-42-24-ein-header-genuegt-wie-gitea-und-forgejo-jedem-fremden-die-admin-rechte-schenkten/ #chrislo #ITSicherheit #ServerInfrastruktur #Gitea #Forgejo #Docker #SelfHosting #CVE #ReverseProxy #OpenSource #Codeberg
chrislo.de
3
2
7
0
davidak @davidak@chaos.social
· 6mo ago
Boosted by @kkarhan@jorts.horse
The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub. https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192 At the same time, the community fork @forgejo@floss.social is self-hosted for a long time and is also powering the popular @Codeberg@social.anoxinon.de and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already. https://forgejo.org
github.com

Gitea hosted Gitea · Issue #1029 · go-gitea/gitea

For the first big stage, we would like Gitea's development could be based on a Gitea hosted and github will only a mirror. This will maybe completed in v1.x. So that this issue will list all the fe...

159
20
110
2