@jamesread it does not help your security when you post a picture of your private API keys #secops #sysops #hacktheplanet
#Sysops
La #UE planea una nueva #ley de #monitoreo masivo con #almacenamiento de #datos de stock " backdoors forzados – ¡ahora todavía hay una contradicción!
Hey, chicos,
la UE está planeando una nueva ley Almacenamiento de datoseso podría estar muy mal. No es sólo un par de datos de conexión, se trata de para comprometer cualquier servicio de monitoreo en línea – también mensajeros, proveedores de alojamiento, sitios web, etc.
Todo está bajo el título:
#Retención de datos por #proveedores de servicios para procedimientos penales ’
Aquí puedes 18 de junio de 2025 Escribe tu opinión: Tu dices
¿Qué hay planeado?
Almacenamiento obligatorio de datos con vínculo de #identidad – así que todo lo que haces en línea debe ser rastreable para ti.
Sanciones para servicios que no incluyen #vigilancia del usuario – incluyendo #VPNs, cosas auto hospedadas o proyectos de código abierto.
Panificación: equipos y software – con fabricantes de hardware se trabajará juntos para permitir el “acceso legal”.
Pequeños proveedores afectados – no es sólo sobre Meta, Google & Co.
Todo el mundo se basa en recomendaciones de Grupo de Alto Nivel ’, cuyos miembros se mantienen completamente secretos. Patrick Breyer (Pirates/MEP) @echo_pbreyer preguntó – la UE le envió una lista debilitada.
Según EDRi, la #sociedadcivil explícitamente excluida. #Lobbyism deluxe.
¿Qué puedes hacer?
Sólo dale retroalimentación, ve en 2 minutos.
En resumen, escribes eso contra el almacenamiento y la vigilancia de datos de almacenamiento no resueltos. Es suficiente. Cada comentario cuenta.
Fecha límite: 18 de junio de 2025, medianoche (hora de Bruselas).
Sería bueno si no nos quedamos quietos de la escena #IT. Esto afecta realmente a todos: #desarrolladores, #administradores, #SysOps, #hosters, #sysops normales.
Blöd gelaufen. Rolle gerade #prometheus Kram via #puppet aus und hab einen #cron übersehen, der deaktiviert war und durch Puppet wieder aktiv wurde. War ein #rsync mit —delete 🙄 und nun fehlen über 400 Dateien .
Ein Mix aus „ist egal und kann neu erstellt werden“, „hmm, blöd aber ok“ und „Shit, da muss man vermutlich den Kunden um Hilfe bitte“. Na mal kucken was das Management da morgen macht.
Jetzt machen wir erstmal 2x täglich #backups
I finally figured out how to automate a certificate request on #Windows that also requires the csr to be signed by a user certificate. Man alive, it should not be that difficult.
As far as I can tell, certreq has no ability to do this natively, so I ended up using certreq to generate the initial csr, then leveraging the COM object to sign it, then back to certreq again for the actual submission/ acceptance.
If you know of a way to do this easier, please let me know!
El día que Anubis, una herramienta anti IA, salvó la web de ScummVM.
The Day Anubis Saved Our Websites From a DDoS Attack
https://fabulous.systems/posts/2025/05/anubis-saved-our-websites-from-a-ddos-attack/
#noAI #scummvm #sysops
What looked like a bit of background noise turned out to be a DDoS attack against the ScummVM website.
Anubis truly saved the day. Read the full story here:
https://fabulous.systems/posts/2025/05/anubis-saved-our-websites-from-a-ddos-attack/
God, I would love to have #terraform / #opentofu providers for #beszel and #uptimekuma
Been doing good shit lately - building clustered server stacks for some of the world's greatest corporations.
I've been doing Bash programming for over 20 years, long before Puppet and Ansible came along, so I never really got into those technologies. I gave them a chance, but I prefer having full control, access to sources, and flexibility in my work. That's why I'm not a fan of the previously mentioned tools - or things like Tailwind and Docker. I love building my own tools and frameworks.
Intel posts flat year-over-year earnings and bleak outlook, warns about macroeconomic pressures
#Intel #INTC #nasdaq #financial #revenue #loss #macroeconomic #spending #pullbacks #competition #AMD #ARM #server #tech #technology #cio #datacenter #compute #stocks #equities #markets #stockmarket #investors #trades #trading #investing #cash #bonds #treasuries #treasury #IT #sysops #economic #economy #finance #money #earnings #trump #tariffs #business #tax #consumer #retail #spending #taxes #electronics #computing
👂⛈️🙏 Help our new co-op with market research Please spare 20 minutes to tell us what problems do you see in your business or organization in switching away from American big tech platforms.
Got insights? DM me to arrange a video call or boost / forward to people who might help us.
We are more than 20 experienced professionals from EU and Canada. We can help. Tell us how?
#softwaredevelopment #freesoftware #sysops #cybersecurity #compliance #data #advocacy #ITeducation #digitalsovereignity
DevOps Engineer (8 month contract) | FreeBSD Foundation
https://freebsdfoundation.org/open-positions/devops-engineer-8-month-contract/
latest "monthly module monday" blog post :) https://cfengine.com/blog/2025/masterfiles-module/ (masterfiles(mfp) as the o.g. build module) #cfengine #configurationmanagement #unix #sysops
If it's code or executables, put it in the image. If it's persistent, put it in a volume. If it's configuration, put it in an environment variable or an environment variable file, or bind mount the configuration file if needed.
Don't bind mount Git directories with code or data into the container. It may be convenient during development, but it makes it very messy for whoever needs to deploy it later (they should ideally not even have to clone a repository).
Something in the Managed Cloud hosting has always bugged me as a DIY dedicated hardware sysop guy. However, times change and currently I'm looking for one or setting up one myself for a site that has insane amount of requests per second.
WP Engine, Pressidium, Pressable, Kinsta, WordPress VIP or custom AWS or what? What do you recommend, specifically for Enterprise WordPress?
#WordPress #SysOps #Hosting #WebHosting #Cloud #AWS #CloudHosting #CloudServices
A while back I was super tired and had too many command line windows open. I typed in the wrong command on the wrong server. This caused system being partly broken, because I accidentally upgraded a held-back package. Eventually got it fixed by recompiling that certain package, but it contained a module compiled by an external party, so had to wait and not restart any services for 24 hours.
Happens to all of us sometimes.
However, what I learned is I should finally really change the color of each prompt for every single server I have. I have dozens of them. I'm lazy that way, I just customize my local prompt but rarely do it on production servers, despite how easy it is.
For Mastodon my prompt is deep purple, like it should.
```bash
PS1="\[\e[38;5;141m\]\u@\h:\w\$ \[\e[0m\]"
```
Here are my other prompts, feel free to use these colors in your .bashrc:
```bash
PS1="\[\e[38;5;99m\]\u@\h:\w\$ \[\e[0m\]" # Light Purple
PS1="\[\e[38;5;141m\]\u@\h:\w\$ \[\e[0m\]" # Pastel Purple
PS1="\[\e[38;5;183m\]\u@\h:\w\$ \[\e[0m\]" # Lavender
PS1="\[\e[38;5;217m\]\u@\h:\w\$ \[\e[0m\]" # Light Pink
PS1="\[\e[38;5;216m\]\u@\h:\w\$ \[\e[0m\]" # Peach
PS1="\[\e[38;5;117m\]\u@\h:\w\$ \[\e[0m\]" # Sky Blue
PS1="\[\e[38;5;159m\]\u@\h:\w\$ \[\e[0m\]" # Soft Cyan
PS1="\[\e[38;5;121m\]\u@\h:\w\$ \[\e[0m\]" # Mint Green
PS1="\[\e[38;5;229m\]\u@\h:\w\$ \[\e[0m\]" # Soft Yellow
PS1="\[\e[38;5;210m\]\u@\h:\w\$ \[\e[0m\]" # Light Coral
```
Despite user growth being +1858% the database and media storage been very, very stable. I'm glad there are enterprise things like S3. I'm feeling more and more confident in my server stack skills.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst