est.social

1 postitusega1 osalejaga0 postitust täna

Sébastien MaretMany universities and research institutes have their own <a href="https://scholar.social/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a> or <a href="https://scholar.social/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> instances, which is a good thing. But are there any plans for these instances to be federated ? It's a bit cumbersome to open a new account on a new instance every time I want to collaborate on a project. <a href="https://scholar.social/tags/openscience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openscience</a>

iverbpunktNachdem ich gerade zwei Issues in einem Github-Repositoryy aufgemacht habe:Wollen wir nicht einfach auch alle Projekte von <a href="https://norden.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> auf <a href="https://norden.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> oder zu <a href="https://norden.social/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a> umziehen?<a href="https://norden.social/tags/unplugtrump" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unplugtrump</a>

Kevin Karhan :verified:Anyone else having issues with <a href="https://infosec.space/tags/PyCharm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PyCharm</a> randomly "forgetting" / bricking <a href="https://infosec.space/tags/logins" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#logins</a> on <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UbuntuLTS</a> Desktop?<ul><li>And it's not just <a href="https://infosec.space/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> and <a href="https://infosec.space/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> but any <a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a>.</li></ul>The only workaround is to literally delete the configs and manually reenter the credentials, only for those to get fucked up with an update or at random.<ul><li>Seriously, why???</li></ul><a href="https://programming.dev/c/jetbrains" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jetbrains</a> , <a href="https://infosec.space/tags/plzfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#plzfix</a>!

Sune Stolborg VuorelaAfter mostly lurking in <a href="https://floss.social/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> administration channels of <a href="https://floss.social/tags/kde" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kde</a>, <a href="https://floss.social/tags/debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debian</a> and <a href="https://floss.social/tags/freedesktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freedesktop</a> I really want to bring them all into a room filled with snacks 1) to thank them for their work and 2) to hope that they would start chatting a bit with each other.And let's also invite the gitlab administrators from <a href="https://floss.social/tags/gnome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnome</a> and maybe others.

Rémi RampinIn their release notes, <a href="https://framapiaf.org/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> has started naming the specific third-party dependencies that cause their security issues... I don't know how I feel about this <a href="https://framapiaf.org/tags/floss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#floss</a> <a href="https://framapiaf.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

securityaffairs<a href="https://infosec.exchange/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> addressed critical auth bypass flaws in CE and EE <a href="https://securityaffairs.com/175370/security/gitlab-addressed-critical-flaws-in-ce-and-ee.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://securityaffairs.com/175370/security/gitlab-addressed-critical-flaws-in-ce-and-ee.html</a> <a href="https://infosec.exchange/tags/securityaffairs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#securityaffairs</a> <a href="https://infosec.exchange/tags/hacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hacking</a>

jomoCritical auth bypass in gitlab / ruby-saml <a href="https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released/#cve-2025-25291-and-cve-2025-25292-third-party-gem-ruby-saml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released/#cve-2025-25291-and-cve-2025-25292-third-party-gem-ruby-saml</a><a href="https://mstdn.io/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> <a href="https://mstdn.io/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a>

Viimatised otsingud

Otsimisvalikud

Administraator:

Serveri statistika:

#gitlab