You Just Entered My Secret Cheatbox!

Debian sources.list - All releases.

2025-03-27T11:52:00+00:00

APT sources.list entries for every Debian release

Debian 7 (Wheezy)#

Archived:

deb http://archive.debian.org/debian/ wheezy main contrib non-free
deb http://archive.debian.org/debian-security wheezy/updates main contrib non-free

Debian 8 (Jessie)#

Original:

deb http://deb.debian.org/debian/ jessie main contrib non-free
deb http://ftp.debian.org/debian/ jessie-updates main contrib
deb http://security.debian.org/ jessie/updates main contrib non-free

Archived:

deb http://archive.debian.org/debian/ jessie main contrib non-free
deb http://archive.debian.org/debian-security jessie/updates main contrib non-free

Debian 9 (Stretch)#

Original:

deb http://deb.debian.org/debian/ stretch main contrib non-free
deb http://deb.debian.org/debian/ stretch-updates main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free

Archived:

deb http://archive.debian.org/debian/ stretch main contrib non-free
deb http://archive.debian.org/debian/ stretch-proposed-updates main contrib non-free
deb http://archive.debian.org/debian-security stretch/updates main contrib non-free

Debian 10 (Buster)#

Original:

deb http://deb.debian.org/debian/ buster main non-free contrib
deb http://deb.debian.org/debian/ buster-updates main non-free contrib
deb http://security.debian.org/ buster/updates main non-free contrib

Archived:

deb http://archive.debian.org/debian/ buster main non-free contrib
deb http://archive.debian.org/debian/ buster-updates main non-free contrib
deb http://archive.debian.org/debian/ buster-proposed-updates main non-free contrib
deb http://archive.debian.org/debian-security buster/updates main non-free contrib

Debian 11 (Bullseye)#

Original:

deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free

Debian 12 (Bookworm)#

Original:

deb http://deb.debian.org/debian bookworm main contrib non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware non-free

Debian 13 (Trixie)#

Original:

deb http://deb.debian.org/debian trixie main contrib non-free-firmware non-free
deb http://deb.debian.org/debian trixie-updates main contrib non-free-firmware non-free
deb http://security.debian.org/debian-security trixie-security main contrib non-free-firmware non-free

Terminating stuck namespaces using kubectl

2025-03-27T11:27:00+00:00

Description#

After installing a helm deployment or testing something and you removed everything, sometimes we faced a stuck namespace, so how to kill it?

Terminating stuck namespace#

Set the namespace name, then run the command below:

NAMESPACE=stuck-namespace

kubectl get namespace "$NAMESPACE" -o json \
  | tr -d "\n" | sed "s/\"finalizers\": \[[^]]\+\]/\"finalizers\": []/" \
  | kubectl replace --raw "/api/v1/namespaces/$NAMESPACE/finalize" -f -

Or, if you have jq installed:

kubectl get namespace "$NAMESPACE" -o json \
  | jq '.spec.finalizers = []' \
  | kubectl replace --raw "/api/v1/namespaces/$NAMESPACE/finalize" -f -

Tip: A namespace usually gets stuck because an API service or a custom resource inside it can no longer be cleaned up. kubectl get namespace "$NAMESPACE" -o yaml shows the reason under status.conditions.

Installing VMWare WorkStation Pro On Ubuntu/Debian and fix VMware kernel module.

2025-02-23T23:57:00+00:00

Downloading the software#

1- Login to the Broadcom Support Portal – https://support.broadcom.com . If you don’t have an account, create one to proceed.

2- After successful login, access the VMware Workstation Pro downloads using the link, Download VMware Workstation Pro

Installing the software#

Executing the below commands:

The kernel headers must be installed before building the VMware modules:

sudo apt update
sudo apt install -y build-essential linux-headers-$(uname -r)
sudo bash VMware-Workstation-Full-$version.bundle
sudo vmware-modconfig --console --install-all

Now application should installed successfully, But if your secure boot enabled you will face the below error when start any vm.

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

To solve this issue you need to disable the secure boot OR do the following secure trick (Sign the VMware modules)!

openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=VMware/"
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon)
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmnet)
sudo mokutil --import MOK.der   # asks you to set a one-time password

After running these commands, you'll need to:

Restart your system.

A blue screen will appear during boot (MOK management).

Choose "Enroll MOK".

Continue with the enrollment.

Enter the password you set with mokutil.

Confirm enrollment.

Your system will continue booting and vmware issue will be over.

Kubernetes Let’s Encrypt wildcard

2024-02-22T17:38:00+00:00

Note: The HTTP-01 solver used below issues a certificate per hostname. A true wildcard certificate (*.example.com) requires a DNS-01 solver.

1. Installing Cert-Manager#

There's 2 ways to install cert-manager, by kubectl from the cert-manager source and the other one is by using helm. Use only one from the 2 options.

Installing Cert-Manager by kubectl#

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.2/cert-manager.yaml

To check the latest cert-manager versions you can visit: Cert-manager kubectl Installation guide

Installing Cert-Manager by helm charts#

helm repo add jetstack https://charts.jetstack.io
helm repo update
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --set crds.enabled=true

2. Installing Nginx ingress controller#

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm install ingress-controller ingress-nginx/ingress-nginx

Or you can check this link for installation from kubectl: Nginx Ingress Controller Installation Guide

3. Configure The Let's Encrypt Certificate Issuer#

To finish this you need to create a file for ex. letsencrypt-production.yaml and put the below inside it:

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-production
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email: example@domain.com
    privateKeySecretRef:
      name: letsencrypt-production
    solvers:
      - http01:
          ingress:
            class: nginx

Then execute the following command:

kubectl create -f letsencrypt-production.yaml

And finally you need to create a file for ex. website.yaml and put the below inside it:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: mywebsite-ingress
  namespace: default
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-production
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - example.website.com
      secretName: mywebsite-tls
  rules:
    - host: example.website.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: wordpress # Or the name of the service that you need to put
                port:
                  number: 80

Apply it and watch cert-manager issue the certificate (it may take a minute):

kubectl apply -f website.yaml
kubectl get certificate -n default

"The project you were looking for could not be found or you don't have permission to view it."

2023-11-24T16:26:00+00:00

The most common errors occur when deploying a Go project from GitLab repositories.

"golang remote: The project you were looking for could not be found or you don't have permission to view it."

"fatal could not read username for 'https //gitlab.com' terminal prompts disabled"

The main reasons behind that are related to authentication and permissions. To solve that, we need to create the following files and fill them with the suitable credentials with the exact syntax:

1- .gitconfig

2- .git-credentials

3- .netrc

And, for sure, you need to place these files under the home directory of the user being used. Ex. moving the files to home directory:

mv .gitconfig ~/
mv .git-credentials ~/
mv .netrc ~/
chmod 600 ~/.git-credentials ~/.netrc

Now, lets start with the content of these files with the exact syntax and make sure editing them to your credentials:

1- .gitconfig

[credential]
        helper = store
[user]
        email = username@domain.com
        name = Your name
[http]
        # Only needed if your GitLab uses a self-signed certificate
        sslverify = false

2- .git-credentials

https://username:TheGeneratedTokenFromGitlab@domainForGitlab.com

3- .netrc

machine is the hostname of your GitLab server (e.g. gitlab.com), not the local machine:

machine domainForGitlab.com
login username
password TheGeneratedTokenFromGitlab

Finally, tell Go that modules on your GitLab are private so it fetches them directly instead of through the public proxy:

go env -w GOPRIVATE=domainForGitlab.com

Startup scripts using "/etc/rc.local"

2023-10-01T00:04:00+00:00

How to use /etc/rc.local at boot#

The file name rc refers to Run Control. To start, create the file /etc/rc.local using the editor you want and paste these values:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/bin/bash /somedirectory/test.sh &
exit 0

Then give execution to rc.local

chmod +x /etc/rc.local

Then create the file /etc/systemd/system/rc-local.service and paste these lines:

[Unit]
Description=/etc/rc.local
ConditionPathExists=/etc/rc.local

[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

After that we need to reload systemd and enable rc-local:

systemctl daemon-reload
systemctl enable rc-local
systemctl start rc-local

kubectl Copy directories and files.

2023-09-30T23:30:00+00:00

Copy local file to a specific pod in specific namespace#

kubectl cp /tmp/foo "namespace"/"pod_name":/tmp/bar

Copy file from specific pod in specific namespace to a local directory#

kubectl cp "namespace"/"pod_name":/tmp/foo /tmp/bar

HTTPS Secure Nginx with Let's Encrypt on Debian.

2023-09-30T23:18:00+00:00

The first step to using Let's Encrypt to obtain an SSL certificate is to install the Certbot software on your server.

Install Certbot and its Nginx plugin#

Open the terminal and run these commands:

apt update
apt install certbot python3-certbot-nginx

Confirming Nginx's Configuration:

nano /etc/nginx/sites-available/default

Find the existing server_name line. It should look like this:

...
server_name example.com www.example.com;
...

Then check the configuration and reload nginx:

nginx -t
systemctl reload nginx

start certbot progress to activate the website by:

certbot --nginx -d example.com -d www.example.com

Now, we are done! Your website is secured. Certbot also installs a timer that renews the certificate automatically; you can test it with:

certbot renew --dry-run

Enable Wireless (Wi-Fi) on Windows Server 2019.

2023-09-30T20:00:00+00:00

Enable Wi-Fi on windows server#

Open the PowerShell console as administrator and run these commands:

Get-WindowsFeature *Wireless*
Install-WindowsFeature -Name Wireless-Networking

After the installation is complete, reboot the host:

shutdown -f -r -t 0

After the restart, the Wireless LAN Service (WLAN AutoConfig) appears in Windows, but it is disabled by default. Start the service and change its startup type to automatic:

Set-Service WlanSvc -startuptype automatic -passthru
Start-Service WlanSvc -PassThru

FreeRadius Server with TP-link or any WPA Enterprise authentication.

2023-09-30T20:00:00+00:00

It's all about creating an authentication server for the wireless router.

Installing FreeRadius on debian server#

Open the terminal and run these commands:

apt update
apt install freeradius

After the installation is complete, we need to edit client file:

nano /etc/freeradius/3.0/clients.conf

Then add the block below, which has the TP-Link router IP address, a shared secret used for authentication between the server and the router, and a shortname (any name works).

client 192.168.0.1 {
    secret    = testing123
    shortname = homewifi
}

After that we need to edit users file:

nano /etc/freeradius/3.0/users

and add the needed user by pasting this block at the beginning of the users file (the second line must be indented):

testuser   Cleartext-Password := "password_complex"
           Reply-Message := "Hello, %{User-Name}"

Now, enable the freeradius service and restart it so it picks up the new configuration:

systemctl enable freeradius
systemctl restart freeradius

You can test the user locally before touching the router:

apt install freeradius-utils
radtest testuser password_complex 127.0.0.1 0 testing123

We are done with the installation and the configuration, now simply go to the TP-Link router, open Wireless Security and select WPA/WPA2-Enterprise. Under RADIUS Server IP put the IP of the RADIUS server, and under RADIUS Password put the secret configured inside clients.conf.

Users are unable to execute the script, even though it has the correct permissions.

2023-09-19T12:20:00+00:00

/etc/fstab#

If you are ever unable to execute a script even though it already has the right permissions and the execute bit is set, the filesystem is probably mounted with noexec.

$ mount | grep noexec
$ nano /etc/fstab
$ # remove no exec from the dir
$ mount -o remount /home