mastodon.online is one of the many independent Mastodon servers you can use to participate in the fediverse.
A newer server operated by the Mastodon gGmbH non-profit

Server stats:

11K
active users

#gitea

5 posts5 participants1 post today
Continued thread

This is, like my #SelfHosted #Gitea instance, publicly exposed through #Pangolin (github.com/fosrl/pangolin) using #Wireguard tunnels. Even though Pangolin is in its early stages, it's been very nice to use and having a graphical user interface to configure some of these bits and pieces has been quite convenient.
I know I'll be sacrificing some speed by not having things directly exposed, the security benefits and not having to worry about dynamic IPs and all more than makes up for it I think.

A short PSA: Gitea's newest Helm Chart, 11.0, switches from DockerHub to docker.gitea.com for the Gitea image. A good thing of course, but you might want to configure your internal cache to cache docker.gitea.com as well, to be a good neighbour and not hammer their infra too much.

For some reason I can't SSH from my laptop to my #Gitea server via its public interface. It just keeps timing out. It's only the laptop having this issue; my tablet and phone are doing this just fine. I was finally able to push my commits by sending them directly over the LAN instead. I've tried resetting the VPN on the laptop, but it's still not working normally.

I am officially confused.

Edit: Mystery solved. I forgot to pay my VPN provider... again.

Und wo ich gerade so im Release-Flow bin, habe ich auch gleich mein etwas eingestaubten #gitlab #github #gitea Vergleich aufpoliert und als Dataset in #OpenResearch & #OpenData manier mit einer #DOI ausgestattet. Und die beiden #gitea Abkömmlinge #codeberg und #forgejo sind auch mit von der Party.

Mit insgesamt 18 Attributen vergleich ich sie u.a. nach #dsgvo, #FOSS awareness.

y.lab.nrw/git

Freu mich auf Euer Feedback, ob sowas hilft?

\__
#OpenSource #100DaysOfCode

ZenodoCompare Gitlab, Github & GiteaCompare Gitlab, Github with Gitea like Codeberg or Forgejo with 18 Attribute. This should answer which Git-Solution are really FOSS.

If you run a #Drone CI server, set DRONE_REGISTRATION_CLOSED=true (and manually create users only when you really really trust someone).

The CPU on my CI/CD server suddenly spiked to 100% today.

A closer look found some users who had registered on git.platypush.tech and on the CI/CD server and created a repo with a .drone.yml, a .gitlab-ci.yml and some scripts with base64-encoded commands.

The repo also contains a deepCC.ipynb Jupyter notebook that downloads some training data from S3 and uses Tensorflow to train a model, and then uses the deepCC binary to do something with that model.

The repository also has a configure script with base64-encoded commands that seem to configure a miner (the wallet ID is R9WpFbvkb6dep6bfLdbpcyz3LpMeikUL6W and the coin is VRSC, if anyone is interested in investigating further).

The deepCC binary is itself quite big (~50 MB), and a look at the setup script reveals that it’s actually a .tar.gz archive with a larger binary inside.

A quick run of strings on the binary confirms that it’s actually a miner - it connects to eu1-etc.ethermine.org and it also has a bunch of CUDA bindings to run on GPUs.

I still don’t get what’s the point of the Jupyter notebook that trains a model and passes it to this miner, but if you feared the day of the arrival of the zombie Docker containers that exhaust system resources by mining cryptocrap AND training AI models, well, I’m afraid to inform you that that day has come.

If you are a #Gitea / #Forgejo admin, take a look at the users and repos created in the past couple of weeks. Check in particular if any recently registered users have created a repo named deepcc-v.

The most likely authors are users named farzanfarid16 and zurizoey0.

A quick search confirms that both these users are registered on #Gitea too and have already created the incriminated repo:

And if you are a Drone CI or #Gitlab admin, check if any of these users have also started CI/CD pipelines connected to that repo.

For now, disabling the execution of CI/CD pipelines unless a user has been explicitly authorized is the best idea that comes to my mind.

Platypush GitPlatypush GitForgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.
Replied in thread

@hjes @warmweb #Joplin hab ich mir von ein paar Tagen auch angeschaut und fand es gut.

Ich bin aber schließlich bei #GitJournal (als App) gelandet, da ich 1. gerne mein lokales #Gitea als Repo für meine Notes nutzen möchte und 2. weil mein Synology WebDav wohl nicht mit versteckten Files umgehen kann. :(

Gitjournal rendert die Markdown Files auf dem Mobile-Devices und erlaubt von dort auch das Erstellen/Ändern/Löschen.

Replied in thread

@arthurr

Oui on répond surtout mais aussi c'est le principal endroit où on informe nos utilisateur.ice.s de tout ce qui se passe chez Zaclys.

On a aussi la GaZette ( zaclys.com/la-gazette-de-zacly ) mais c'est sacrément moins dynamique que les messages ici sur notre instance :mastodon:

Par exemple hier on nous a interpelé une énième fois pour passer de #Gitea à #Forgejo et ce matin on l'a fait :blobcatcheer:

ZACLYSLa gazette de la mère Zaclys - ZACLYS