> This release contains security fixes. To give everyone time to upgrade, details will be added to this post in about a week.
Is this something that has been happening for a while or a new trend due to LLM concerns? I understand the reasoning, it just made me do a double take because I haven't really seen that before.
With Gitea specifically or in general? A lot of different software has silently included security fixes in updates combined with other changes and then later revealed what security fixes were made or stayed quiet about it all together, since long before LLMs could analyze changes.
Security researchers and malware authors would reverse engineer software updates of proprietary software, and scrutinise source code changes of open source projects to find secretly shipped security fixes.
(bias note: I am a project lead of Gitea) this approach is based on what peertube has been doing, and is being attempted as an alternative approach to what we've been doing previously due to feedback we've been receiving from the community.
The feedback was that we gave too many details too soon, and so we solicited feedback from the community and peertube's approach was given as a suggestion for us to try. But to be clear, this decision was discussed and made by the maintainers, including the elected leadership team. I'd say that this is a successful example of governance, as it isn't a unilateral decision, and everyone was involved in making.
Would you also argue that the technical quality, efficiency, capacity, performance etc. of a piece of machinery, too, is way less important than the social and political values of its manufacturer? Say, a piece of medical equipment used in a hospital to keep a patient alive.
I'm sure nobody will, but I disagree that it's an apples and oranges thing. But for you I'm willing to instead offer an example of a CNC machine making parts for... anything. The question and comparison is at its core still just as valid and relevant. Is the result way less important than "feeling good" about the solution?
Unfortunately, seems like this is Forgejo's best suggestion on how to compare the two: https://i.imgur.com/j1665QR.png. Not sure that page helps much if you're not already bought in to a free-software-absolutist mindset
I wish they had an actual feature comparison list. I've been trying to find anyone who can give me a list of non-trivial differences between the two; so far it's always either FUD about Gitea's governance and security structure or ForgeFed. The former has made me rather wary of the project[0] and the latter has been stagnate for years and I'm no longer convinced anything will come from it. Otherwise it's just silence.
Personally I thought Forgejo was doing better work on their actions runner for a while from casual changelog browsing but Gitea's been putting a lot of work into theirs. Otherwise it mostly still looks like a soft-fork in practice to me.
[0] Not that I'm thrilled with Gitea's semi-open-core setup and company but they make it seem like they're kicking puppies and dangling features over non-enterprise users head before snatching them away.
Remember, if all you need is a git remote to push to somewhere via ssh, `git init --bare` on your server should be available and is solid if you don't need a web interface. Now you've got something you can push to on a shared server.
Unless you really also want a web interface, issue tracking, et. al. Then, use any of these fine tools. Go wild!
I don't really need the web interface, but the actions are useful. Automatically building updated docker images and software packages is enough to accept the gitea complications, but gitlab is way too heavy IMHO
Actions support running on times. Sure, I could wire up a Rube Goldberg of systemd user timers and user units that trigger on hooks or I can store some yaml in the repo and it just works (tm)(r).
Sometimes the juice isn't worth the squeeze, and for me, doing it all custom isn't worth it for my home projects.
there's nothing wrong with it, just more work then I'd like. I'd have to setup a CI system or build my own to handle the dependency management of the jobs and, as I said, time based job runs (Rebuild this image monthly regardless of any code changes) add enough complexity that using the gitea container for the actions and ci is worth it compared to something marginally lighter weight.
I feel like this is one of those topics where compromise is futile. I use GitLab at work and use plain git on personal projects. I don't like spending time on tools that aren't either teaching me or paying me.
ThePinion | a day ago
Is this something that has been happening for a while or a new trend due to LLM concerns? I understand the reasoning, it just made me do a double take because I haven't really seen that before.
QuantumNomad_ | a day ago
Security researchers and malware authors would reverse engineer software updates of proprietary software, and scrutinise source code changes of open source projects to find secretly shipped security fixes.
stackghost | a day ago
IshKebab | a day ago
techknowlogick | a day ago
entrope | 22 hours ago
techknowlogick | 5 hours ago
e12e | 11 hours ago
Makes work harder for sys admins - little difference for black hats.
It's still a (<LLM> look at diffs in latest gitea release - find the patched security issues and write poc exploit for cve assessment) I guess?
MitPitt | a day ago
layer8 | a day ago
wasting_time | a day ago
https://forgejo.org/compare-to-gitea/
DASD | a day ago
GrayShade | a day ago
tjoff | a day ago
daneel_w | 23 hours ago
ulimn | 23 hours ago
DASD | 23 hours ago
daneel_w | 4 hours ago
yjftsjthsd-h | 22 hours ago
p-e-w | 21 hours ago
nightpool | a day ago
lloydatkinson | 5 hours ago
nightpool | 5 hours ago
thiht | 3 hours ago
stryan | a day ago
Personally I thought Forgejo was doing better work on their actions runner for a while from casual changelog browsing but Gitea's been putting a lot of work into theirs. Otherwise it mostly still looks like a soft-fork in practice to me.
[0] Not that I'm thrilled with Gitea's semi-open-core setup and company but they make it seem like they're kicking puppies and dangling features over non-enterprise users head before snatching them away.
_g0xr | 23 hours ago
kevincox | 22 hours ago
godbox | a day ago
LoganDark | a day ago
QuantumNomad_ | a day ago
ulimn | 23 hours ago
dogline | 23 hours ago
Unless you really also want a web interface, issue tracking, et. al. Then, use any of these fine tools. Go wild!
broodbucket | 22 hours ago
unsnap_biceps | 22 hours ago
SmasherEpilepti | 21 hours ago
Gitea or Forgejo with actions is almost certainly easier, but it's possible to do it with pure git.
unsnap_biceps | 21 hours ago
Sometimes the juice isn't worth the squeeze, and for me, doing it all custom isn't worth it for my home projects.
spwa4 | 8 hours ago
unsnap_biceps | 4 hours ago
sublinear | 18 hours ago
I feel like this is one of those topics where compromise is futile. I use GitLab at work and use plain git on personal projects. I don't like spending time on tools that aren't either teaching me or paying me.
sandreas | 16 hours ago
pjmlp | 10 hours ago
donbox | 21 hours ago
ChrisRR | 13 hours ago
https://github.com/go-gitea/gitea/issues/1029