Autodidacta, TIC's, Software-Cultura Libre, copyleft-CC, privacidad y protección de datos personales, derecho a la información, todo título personal. @mozillamx
Joined April 2007
- Tweets27K
- Following2.8K
- Followers2.5K
- Likes4K
Pinned Tweet
¿Confías en los sitios web que visitas y a las cuales les proporcionas información? adslzone.net/2017/11/20/scri… varias registran lo que escribes, importante usar uBlock Origin addons.mozilla.org/es/firefo… y NoScript addons.mozilla.org/es/firefo… #ProtecciónDeDatos #culturadelaprivacidad
Mundial de mierda @FIFAcom @Argentina ya mejor que le den la copa y nos evitamos perder el tiempo.
Odin Mojica retweeted
🇦🇷🇪🇬 Everyone wanted to scream that Argentina vs Egypt was rigged.
Then the replay made it annoying.
Egypt’s first controversy came when the refs missed a foul, Egypt went coast to coast, scored, and appeared to go up 2-0.
But VAR stepped in, reviewed the buildup, and ruled no goal.
As much as people wanted to lose their minds, the foul was there.
And under VAR, if an offense leads into the buildup of a goal, exactly what happened on that play, they can review it and take the goal away.
Then came the extra detail nobody wants to hear:
The Egyptian player also appeared to remove his shirt, which is supposed to be a yellow card.
Fast-forward to the 97th minute.
Salah goes down for Egypt, Argentina go coast to coast, score, and take the lead.
But when the play is slowed down, the defender touches the ball first.
It becomes a loose ball, then the player gets tripped up.
So yes, everyone wanted the “rigged” version.
The problem is the refs may have actually gotten both calls right.
Source: @MikeDaddino on YT / Writer Sol
Odin Mojica retweeted
Epic Games got tired of Git. So they built their own version control system. Then gave it away for free.
This is Lore. Announced at State of Unreal 2026. Open source under MIT. Available right now.
Git was never built for game development. When you are working on a project like Unreal Engine or Fortnite you are mixing source code with massive binary files. 3D models. Textures. Audio. Build outputs. Files that are gigabytes in size.
Git handles large binary files through a bolted-on add-on called Git LFS. Perforce handles them better but it needs a live server connection for everything and nobody outside your company can build tools on top of it.
Epic said none of the existing systems solved all three problems together. Large binary handling, offline work and an open specification. So they spent years building one themselves.
Here is what Lore actually does differently:
→ Works completely offline. Commits, branches, switching — all happen on your machine without touching a server.
→ Every file gets a unique fingerprint. Identical data is never stored twice across files or branches.
→ Large files are broken into chunks. Edit one part of a multi-gigabyte file and only that chunk gets re-uploaded.
→ Your machine only holds files you are actually using. Everything else gets pulled down on demand.
→ Built in Rust. Core library, server and CLI all use the same interface. No special privileged commands.
→ Official SDKs for JavaScript, Python, C# and Go ship with it.
Perforce licenses cost tens of thousands of dollars a year. Git LFS is a workaround that was never meant to be a solution.
Lore is free. Written in Rust. MIT licensed. And Epic just put it on the internet for anyone to use.
Repo here:
github.com/EpicGames/lore
Odin Mojica retweeted
Linux users who uninstalled Windows to escape Microsoft and choose freedom with Linux may not have escaped yet.
Microsoft holds the cryptographic key that allows every major Linux distro to boot on modern hardware. Ubuntu. Fedora. Debian. All of them. Without Microsoft's signature your Linux machine does not start.
And that key expires in 4 days. June 27, 2026.
Here is what is actually happening.
When Secure Boot was introduced in 2012, Microsoft became the certificate authority for the entire PC boot ecosystem. Every Linux bootloader on the planet has to be signed by Microsoft to run on any UEFI machine with Secure Boot enabled.
Your existing Linux install will still boot after June 27. That is the good news.
The bad news is everything going forward.
→ Any new shim binary after June 27 cannot be signed with the old key anymore
→ If your firmware never gets the new 2023 Microsoft certificates, fresh distro installs will fail to boot
→ Older laptops, smaller vendor hardware and embedded devices that never receive firmware updates are now in permanent limbo
→ Dell, HP and Lenovo have pushed updates. Smaller vendors have not. Nobody knows how many devices fall through the cracks.
The fix for most people is one command: sudo fwupdmgr update
But the bigger story here is the one nobody is talking about.
The Linux community spent years arguing about freedom and independence from Microsoft. The entire time Microsoft had a key that every Linux machine on earth depended on to start.
That is not a conspiracy. That is just how Secure Boot was designed.
Run the update. Then think about what it means.
Full details here:
zdnet.com/article/aspirin-fo…
Odin Mojica retweeted
En México operan criminales y mafias del extranjero en las 32 entidades; provienen de al menos 13 países. Comparto un mapa que resume su presencia, incluido en mi artículo de hoy en @nexosmexico (link al artículo en el primer comentario).
Odin Mojica retweeted
Linux Security Fundamentals
1. Introduction
→ Linux security focuses on protecting the system, data, and services from unauthorized access, attacks, and misuse.
→ Linux is known for its strong security architecture, but proper configuration and management are essential.
→ Security involves controlling access, monitoring activities, and protecting system resources.
2. Core Security Principles
→ Confidentiality → Protect sensitive information from unauthorized access.
→ Integrity → Ensure data remains accurate and unchanged.
→ Availability → Ensure systems and services remain accessible when needed.
3. User and Permission Management
→ User Accounts
→ Each user has a unique User ID (UID).
→ Users belong to groups identified by Group IDs (GIDs).
→ Proper user management prevents unauthorized system access.
→ File Permissions
→ Linux uses three permission types:
→ Read (r) → Allows viewing file contents.
→ Write (w) → Allows modifying files.
→ Execute (x) → Allows running files as programs.
→ Permissions apply to:
→ Owner
→ Group
→ Others
→ Commands used:
→ chmod → change file permissions
→ chown → change file ownership
→ chgrp → change group ownership
4. Authentication Mechanisms
→ Linux authenticates users through several methods.
→ Password Authentication
→ Stored securely in /etc/shadow.
→ Passwords are hashed for security.
→ SSH Key Authentication
→ Uses public-private key pairs.
→ More secure than password authentication.
→ Multi-Factor Authentication (MFA)
→ Combines password with additional verification methods.
5. Access Control Systems
→ Discretionary Access Control (DAC)
→ Default Linux permission system.
→ File owners decide who can access their files.
→ Mandatory Access Control (MAC)
→ Enforces stricter security policies.
→ Examples:
→ SELinux
→ AppArmor
6. System Hardening
→ System hardening reduces attack surfaces.
→ Disable unnecessary services.
→ Update packages regularly.
→ Use strong password policies.
→ Restrict root login access.
→ Use SSH instead of insecure protocols.
7. Firewall Protection
→ Firewalls control network traffic entering or leaving the system.
→ Common Linux firewall tools:
→ iptables
→ nftables
→ UFW (Uncomplicated Firewall)
→ Firewalls protect against unauthorized network access.
8. Intrusion Detection
→ Detect suspicious activities in the system.
→ Tools include:
→ Fail2Ban → blocks repeated login attempts.
→ OSSEC → host-based intrusion detection.
→ AIDE → file integrity monitoring.
9. Software Updates and Patch Management
→ Regular updates fix vulnerabilities and bugs.
→ Commands used:
→ apt update && apt upgrade
→ yum update
→ dnf update
→ Keeping the system updated reduces security risks.
10. Logging and Monitoring
→ Monitor system logs to detect unusual activity.
→ Important log files:
→ /var/log/auth.log → authentication attempts
→ /var/log/syslog → system events
→ /var/log/kern.log → kernel messages
→ Tools like journalctl help analyze logs.
11. Security Best Practices
→ Use least privilege principle.
→ Enable firewall protection.
→ Monitor system logs regularly.
→ Use strong passwords and SSH keys.
→ Disable unused ports and services.
→ Backup important data.
12. Tip
→ Linux security relies on permissions, authentication, and monitoring.
→ Proper configuration significantly reduces vulnerabilities.
→ Combining system hardening, firewalls, and intrusion detection creates a strong defense.
→ Continuous monitoring and updates maintain system security.
📘 Linux Mastery Ebook
→ Master Linux internals, security, system monitoring, logging, process management, and architecture step-by-step.
🔗 Grab the Linux Mastery Ebook
codewithdhanian.gumroad.com/…
Odin Mojica retweeted
Docker & Containerization Roadmap
PHASE 1: FUNDAMENTALS & BASICS
├── Container Concepts
│ ├── What are containers vs VMs
│ ├── Containerization benefits
│ ├── Docker architecture
│ └── Container orchestration overview
├── Docker Installation
│ ├── Docker Desktop (Windows/Mac)
│ ├── Docker Engine (Linux)
│ └── Verify installation: `docker --version`
├── Basic Commands
│ ├── `docker run hello-world`
│ ├── `docker ps`, `docker images`
│ ├── `docker pull`, `docker rmi`
│ └── Container lifecycle commands
PHASE 2: DOCKER IMAGES
├── Dockerfile Fundamentals
│ ├── Base images (FROM)
│ ├── Copy files (COPY/ADD)
│ ├── Run commands (RUN)
│ ├── Expose ports (EXPOSE)
│ └── Default command (CMD vs ENTRYPOINT)
├── Building Images
│ ├── `docker build -t myapp:tag .`
│ ├── Multi-stage builds
│ └── Image layers and caching
├── Docker Hub & Registries
│ ├── Push/pull to Docker Hub
│ ├── Private registries
│ └── Image tagging best practices
PHASE 3: CONTAINER MANAGEMENT
├── Container Operations
│ ├── Interactive vs detached mode
│ ├── Port mapping (`-p 8080:80`)
│ ├── Volume mounts (`-v /host:/container`)
│ └── Environment variables (`-e`)
├── Docker Networking
│ ├── Default networks (bridge, host, none)
│ ├── Create custom networks
│ ├── Container-to-container communication
│ └── DNS resolution between containers
├── Docker Storage
│ ├── Volumes (`docker volume create`)
│ ├── Bind mounts
│ └── tmpfs mounts
PHASE 4: DOCKER COMPOSE
├── Compose Basics
│ ├── `docker-compose.yml` structure
│ ├── Services, networks, volumes
│ └── `docker-compose up/down`
├── Multi-Container Applications
│ ├── Web app + database setup
│ ├── Environment variables in Compose
│ └── Dependency management (depends_on)
├── Production Considerations
│ ├── Compose file versions
│ ├── Resource limits
│ └── Health checks
PHASE 5: PRODUCTION & BEST PRACTICES
├── Security
│ ├── Non-root users in containers
│ ├── Image scanning (Trivy, Grype)
│ ├── Secrets management
│ └── Reducing attack surface
├── Optimization
│ ├── Small base images (Alpine)
│ ├── Layer minimization
│ ├── `.dockerignore` file
│ └── Build context optimization
├── CI/CD Integration
│ ├── Docker in GitHub Actions
│ ├── Docker in GitLab CI
│ └── Build automation pipelines
PHASE 6: CONTAINER ORCHESTRATION (KUBERNETES)
├── Kubernetes Fundamentals
│ ├── Pods, Deployments, Services
│ ├── `kubectl` basic commands
│ ├── Minikube / Kind setup
│ └── YAML manifest files
├── Docker & Kubernetes
│ ├── Building images for Kubernetes
│ ├── Private registry integration
│ └── ConfigMaps and Secrets
├── Production Kubernetes
│ ├── Helm charts
│ ├── Ingress controllers
│ └── Monitoring (Prometheus, Grafana)
PHASE 7: ADVANCED TOPICS
├── Docker Swarm (Alternative to K8s)
│ ├── Swarm mode basics
│ ├── Services and stacks
│ └── Overlay networks
├── Cloud Container Services
│ ├── AWS ECS/EKS
│ ├── Azure AKS
│ ├── Google GKE
│ └── Managed container registries
├── Monitoring & Logging
│ ├── Docker logs management
│ ├── Centralized logging (ELK, Loki)
│ └── Monitoring (cAdvisor, Portainer)
PHASE 8: SPECIALIZED SCENARIOS
├── Development Workflows
│ ├── Development containers (Dev Containers)
│ ├── Live reload in containers
│ └── Debugging containers
├── Legacy Application Containerization
│ ├── Monolith to container migration
│ ├── Database in containers (stateful apps)
│ └── Backup strategies
├── Edge Cases
│ ├── Docker on ARM/Raspberry Pi
│ ├── GPU acceleration (NVIDIA Docker)
│ └── Windows containers
LEARNING RESOURCES
├── Official Documentation
│ ├── docs.docker.com
│ └── kubernetes.io/docs
├── Practice Platforms
│ ├── Play with Docker (labs.play-with-docker.com)
│ ├── Katacoda (free courses)
│ └── Docker's official tutorial
├── Certifications (Optional)
│ ├── Docker Certified Associate (DCA)
│ └── Certified Kubernetes Administrator (CKA)
PROJECTS TO BUILD
1. Simple static website container
2. Multi-container app (Node.js + Redis + PostgreSQL)
3. CI/CD pipeline with Docker
4. Deploy to Kubernetes cluster
5. Full-stack microservices application
Estimated Time: 3-6 months for comprehensive understanding
Prerequisites: Basic Linux/CLI, Git fundamentals
Progression Tips:
1. Start with Phase 1-2, build simple containers
2. Move to Phase 3-4 for multi-container apps
3. Skip to Phase 6 early for Kubernetes basics
4. Return to Phase 5 for production optimizations
5. Practice daily with real projects
Key Philosophy; Learn by doing - break things, fix them, understand why they broke.
Grab this Docker Handbook; codewithdhanian.gumroad.com/…
