6 ms·
Jesus the amount of remote-exploitable bugs in Gitlab the last months is astonishing. At this point it's madness to even consider running a publicly-reachable G
by mschuster91 5y ago
Jesus the amount of remote-exploitable bugs in Gitlab the last months is astonishing. At this point it's madness to even consider running a publicly-reachable Gitlab instance...
And that's actually pretty sad, because Gitlab is the only open-source alternative that can keep up with Github feature-wise.
- ModernMech 5y ago> only open-source alternative that can keep up with Github feature-wise. Imo they're still leading Github in some areas. My favorite Gitlab exclusive feature is a very simple one: folders inside of projects. Usually Github has followed a pattern of catching up to Gitlab, so I think it's probably only a matter of time before they add this feature (if they haven't already, it's been a while since I checked). Actually I take that back, my favorite feature is that I can host my own private instance. Gitlab gets even better if you have admin access to the system. And that's one feature Github will probably take a while to copy, if ever.
- Operyl 5y ago> And that's one feature Github will probably take a while to copy, if ever. Eh you can already self host GitHub, longer than GitLab has been around, it’s just not free to do so.
- ModernMech 5y ago> it’s just not free to do so. My general rule of thumb is that if a product lists its price as "Contact our sales team", then its effectively unavailable to me as an individual. So I guess if we're talking about what exactly the Github "feature" is that MS won't copy, it wouldn't be that there's an enterprise option, but that Gitlab is free and open source and practical for me as an individual to install. Obviously if you pay Microsoft enough money they'll do whatever you want (up to and including I guess buying Github itself as a company from them. Always has been an option, it's just not free to do so.)
- Operyl 5y agoPricing isn’t hidden: https://github.com/pricing https://github.com/pricing $21 per user per month.
- ModernMech 5y agoWell that confirms I can't afford it! Interestingly, this page isn't linked to from https://github.com/enterprise https://github.com/enterprise (except in the footer), where the calls to action are to either "start a free trial" or to "contact sales".
- granzymes 5y agoIt's also prominently displayed in the header.
- ModernMech 5y agoOnly if you're not logged in. If you're logged in it's not there at all. Why does this feel like people are trying to turn this into some sort of gotcha? It wasn't even my main point. The point is that GitHub enterprise is not an option for individuals.
- bastardoperator 5y agoHense the title "Enterprise"...
- ModernMech 5y agoExactly. But the original argument was "well ackshually, you can self host Github, you just have to pay for it". Technically true, practically not.
- Operyl 5y agoWhile not practical for you, it's not priced out for every single small team or individual user ever. If I recall correctly, there's no minimum seat requirement still. You're changing the position of the goal post on your original comment :). Original comment from you: > Actually I take that back, my favorite feature is that I can host my own private instance. Gitlab gets even better if you have admin access to the system. And that's one feature Github will probably take a while to copy, if ever.
- deleted 5y ago[deleted]
- colechristensen 5y ago>Gitlab is the only open-source alternative that can keep up with Github feature-wise. I think it's a bit the opposite, GitHub seems to have started adding most of these features as a response to competition with GitLab. Not that GitHub hasn't pulled ahead in some ways now.
- Schinken_ 5y agoI am not even sure if most people would need all the features. Nice to have yes, but I have been running Gogs for at least 2 years and never thought I need more. This is for personal usage though.
- Faaak 5y agoCIs + runners + embedded registry is a really nice add-on that I couldn't do without
- KronisLV 5y agoAgreed! However the amount of maintenance that you need to do because of the vulnerabilities is disappointing, especially due to how contrived the upgrade paths are: https://docs.gitlab.com/ee/update/#upgrade-paths https://docs.gitlab.com/ee/update/#upgrade-paths Thus, it might be a better idea to look into a less popular stack that's less likely to be targeted as much due to not being such a juicy target. For example: Code: Gitea/Gogs/GitBucket CI: Drone/Jenkins (okay there are probably better options than Jenkins, to be honest) Registry: Nexus/Artifactory (not just for containers, they support most formats and have better control over cleanup of old data so you don't have to schedule GitLab cleanup yourself) Of course, at the end of the day all of those still have an attacks surface, so i'm really leaning more and more into the camp of exposing nothing publicly since it's a losing battle.
- tenken 5y agoWhat maintenance?! I just bump the docker-compose.yml version numbers and Stop/Start the service. It's very painless... My cellphone has more frequent updates than Gitlab does.
- KronisLV 5y agoIf you do that with minor versions, you should generally be fine. When you need to upgrade across major versions, you'll most likely be met with the following in case you haven't followed the updates closely: > It seems you are upgrading from major version X to major version Y. > It is required to upgrade to the latest Y.0.x version first before proceeding. > Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-... In addition to that, you should NEVER just bump versions without having backups (which you've hopefully considered), so there is probably another step in there, either validating that your latest automatic backups work, or even just manually copying the current GitLab data directory into another folder, in the case of an Omnibus install, or doing the same manually for all components in the more distributed installation type. Disclaimer: this has little do to with GitLab in particular but is something you should consider with any and all software packages that you upgrade, especially the kind with non-trivial dependencies and data storage mechanisms, like PostgreSQL. Of course, you can always dump the DB but it's easier to back up everything else as well by taking the instances offline and making data copies of all container volumes/bind mounts.
- saxonww 5y agoWe've talked about this a lot internally. They make a big deal about releasing on the 22nd of every month, but they usually have to turn around and release a patch shortly thereafter. 14.8 is a bit of an extreme: 14.8.0 on the 22nd, 14.8.1 (bug fix) on the 23rd, then 14.8.2 (security) on the 25th. We'd personally prefer to see a better release when it's done, vs. them keeping this farce of a 'release streak' going and then asking customers to install another upgrade within days.
- 0xbadcafebee 5y agoSeems like you could just wait a few weeks until upgrading to a new release?
- lbotos 5y agoI've proposed to other customers who want less releases to track one minor version behind for the experience you are looking for. Still within security fix range, up-to-date and you will jump the the latest patch release (and none should follow unless it's a security release).
- blyry 5y agoI always ran 1 ( sometimes 2) point releases behind, never ever had an issue upgrading. Omnibus on Ubuntu.
- PragmaticPulp 5y agoI had to upgrade a slightly older, internal-only GitLab instance for a company a while ago. I was shocked by how many upgrade path dependency problems there were. Ended up having to roll back to a backup and do the upgrade in a stepwise fashion through various intermediate steps according to their long document on the process, including a fair number of manual commands and migrations and a lot of Googling for obscure error messages. I enjoy GitLab and it’s the real only option for open self-hosting, but it made me miss the days of having GitHub Enterprise.
- donmcronald 5y agoYeah. I just booted up an old VM to update it. It was on v13 and told me I needed to upgrade to 14.0 first, then 14.8. I did that. Now it's totally broken with crappy error messages and I'll get to waste a few hours today trying to fix it. I switched to Gitea a long time ago and have no regrets.
- cpitman 5y agoLiterally going through this right now. Performing the upgrade from 13 to 14, following the required upgrade path. In the past, you could go from current version -> latest z release -> X.0 release of the next major -> latest minor release of Z. As long as gitlab completed the db migrations and came up, you were (relatively) ok to continue to the next upgrade. Turns out 14 introduces a brand new upgrade failure case. Starting with 14, upgrades can include async db migrations that must complete before you continue upgrading. But once you start upgrading, it's too late, things are hosed, so now I'm falling back to a backup and starting over.
- bogwog 5y agoHow many people would even want to host a public Gitlab instance? Gitlab.com is free, works well, and even gives you some free CI minutes. I’ve been running a private instance for about a year and am absolutely in love with it. Gitlab CI is the killer feature IMO, and self hosting it means I never have to worry about usage limits. But if all you need is basic git hosting with an issue tracker, I don’t see a reason to use Gitlab over something like Gitea.
- jancsika 5y agoI run a Gitlab instance. It wouldn't be a pain except that user spam is nonstop. How does gitlab.com deal with this? Or do they just put up with rando users signing up and spamming the snippets/issues/etc.?
- boleary-gl 5y agoGitLab employee here. We have internal tooling that we're working on incorporating into GitLab itself to help with this: https://about.gitlab.com/blog/2021/08/19/introducing-spamcheck-data-driven-anti-abuse/ https://about.gitlab.com/blog/2021/08/19/introducing-spamche....
- jancsika 5y agoSounds like a potential solution. When will it ship?
- boleary-gl 5y agoLooks like it shipped in 14.8 (4 days ago) https://docs.gitlab.com/ee/user/admin_area/reporting/spamcheck.html https://docs.gitlab.com/ee/user/admin_area/reporting/spamche...
- jancsika 5y agoOh wow, thanks! I'll have a look.
- EnFinlay 5y agoI know Gitlab takes security seriously and I think part of why we hear so much about it is because they're so transparent.
- registeredcorn 5y agoThat's the rub, isn't it? I feel some of the least secure places are the ones which never mention (or realize) that they have a security problem. I don't have any particular opinion of Gitlab, but it does seem to be that acknowledging fault is more valuable than the alternative. If I were to attack a service, I'd probably tend to avoid the one that actively updates it's security regularly.
- Genbox 5y agoI feel some of the least secure places are the ones which never mention (or realize) that they have a security problem. It is an age old conundrum that people seem to struggle with a lot. As part of my previous profession, I've security reviewed hundreds of open source libraries. They fall into 3 categories: 1. The libraries/applications that have either had a really security conscious developer behind it or a very rocky past such that it was given an extraordinary amount of attention security wise. These account for about 1% of software 2. The "normal" libraries/applications that nobody care about with regards to security. As long as the code works everyone keeps using it. They are often insecure by default, but the lack of attention by SME means they wont be judged. They account for 80% of software. 3. The horrid ones. Built-in code execution as a feature. Authentication systems with more critical bugs that you can possibly image. We never talk about these because... well, we could spend months on polishing a turd. Nobody dares to publicly speak up and say "don't ever use X, Y and Z" for fear of the repercussions. They account for the rest of software. GitLab used to be in category 2, but got moved into 1 about two years ago when security professionals started to give it attention. As to your feeling, 99% of software have security issues, some worse than others. We rarely talk about them.
- 0xbadcafebee 5y ago> it's madness to even consider running a publicly-reachable Gitlab instance... why would you want it to be a public instance?
- thfuran 5y agoThat seems pretty reasonable for any open source project to want.