From fab049022880aa9ecb5662cf8321364868d99cb3 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 08:48:25 +0200 Subject: [PATCH 01/26] README.md --- README.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index cf88c9a..2da77ac 100644 --- a/README.md +++ b/README.md @@ -2,15 +2,17 @@ ## Introduction -L'objectif de ce TP est de **sécuriser** et **automatiser** la configuration initiale d'un système Debian. - -Vous créerez un **script Bash** qui centralisera toutes les opérations de durcissement, en veillant à ce que le processus soit **automatisé** et **fiable**. - -Le script principal devra **sourcer des fonctions** spécifiques depuis d'autres fichiers pour maintenir un code clair et modulaire. De plus, vous devrez porter une attention particulière aux **inputs utilisateurs** et à la gestion des fichiers. - -N'oubliez pas d'**anticiper les erreurs** et de vérifier systématiquement que tous les fichiers et fonctions requis sont accessibles et fonctionnels avant de procéder. - -Exemple : https://sbnsec.fr/linux.sh +Nous avons mis en place des scripts d'automatisation pour permettre la sécurisation d'un système Debian. +Nous avons fait : +- La copie de la clé SSH (sur le serveur). +- Durcissement de la connexion via SSH. +- Installation et configuration d'un pare-feu. +- Mise a jour automatique des paquets de sécurité. +- Désactivation des services inutiles. +- Création d'alias pour des commandes fréquentes. +- Personnalisation du prompt Bash. +- 2FA (via google authenticator). +- Script qui éxecute tous les autres. ## Objectifs From 5e238ce914a2b8d86b6c8252f299577cff74164d Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 08:58:01 +0200 Subject: [PATCH 02/26] README.md --- README.md | 29 ++++++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2da77ac..8775076 100644 --- a/README.md +++ b/README.md @@ -14,12 +14,31 @@ Nous avons fait : - 2FA (via google authenticator). - Script qui éxecute tous les autres. -## Objectifs +## Copie de la clé SSH (copy_key_ssh.sh) -- **Automatiser** la configuration initiale de la sécurité. -- **Durcir** les configurations essentielles, comme SSH et les services. -- **Personnaliser** l’environnement de travail pour le rendre plus adapté à vos usages. -- **Proposer des idées** novatrices et utiles pour améliorer la sécurité et l’ergonomie de votre système. +#!/bin/bash + +# Vérification de l'existence de la clé SSH +if [ ! -f ~/.ssh/id_rsa ]; then + echo "Aucune clé SSH trouvée. Création d'une nouvelle paire de clés..." + ssh-keygen -t rsa -b 4096 -N "" -f ~/.ssh/id_rsa + echo "Clé SSH créée : ~/.ssh/id_rsa.pub" +else + echo "Une clé SSH existe déjà : ~/.ssh/id_rsa.pub" +fi + +# Afficher la clé publique et l'ajouter à authorized_keys +cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys + +# Fixer les permissions du fichier authorized_keys +chmod 600 ~/.ssh/authorized_keys + +# Assurer que le répertoire .ssh a les bonnes permissions +chmod 700 ~/.ssh + +echo "Clé SSH ajoutée avec succès au fichier authorized_keys." +echo "Clé publique :" +cat ~/.ssh/id_rsa.pub ## Étapes du TP From 41c865071ceceb3d582ef038566d83f587a6cb16 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:00:20 +0200 Subject: [PATCH 03/26] README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8775076..e70e50d 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,7 @@ Nous avons fait : ## Copie de la clé SSH (copy_key_ssh.sh) +```bash #!/bin/bash # Vérification de l'existence de la clé SSH @@ -38,7 +39,7 @@ chmod 700 ~/.ssh echo "Clé SSH ajoutée avec succès au fichier authorized_keys." echo "Clé publique :" -cat ~/.ssh/id_rsa.pub +cat ~/.ssh/id_rsa.pub ``` ## Étapes du TP From 94f0fcf181591f0af1941baf46916cbffbc5e567 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:01:11 +0200 Subject: [PATCH 04/26] README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e70e50d..ff7eb86 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,9 @@ chmod 700 ~/.ssh echo "Clé SSH ajoutée avec succès au fichier authorized_keys." echo "Clé publique :" -cat ~/.ssh/id_rsa.pub ``` +cat ~/.ssh/id_rsa.pub + +bash``` ## Étapes du TP From c59e0885bb56358de98943d7d6faaa276c0cda0d Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:02:45 +0200 Subject: [PATCH 05/26] README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ff7eb86..a29b279 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ echo "Clé SSH ajoutée avec succès au fichier authorized_keys." echo "Clé publique :" cat ~/.ssh/id_rsa.pub -bash``` +``` ## Étapes du TP From e6d4ffdcf9c0e25019aa1773c733729321b3c930 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:06:45 +0200 Subject: [PATCH 06/26] README.md --- README.md | 82 ++++++++++++++++++++++--------------------------------- 1 file changed, 33 insertions(+), 49 deletions(-) diff --git a/README.md b/README.md index a29b279..352139a 100644 --- a/README.md +++ b/README.md @@ -43,56 +43,40 @@ cat ~/.ssh/id_rsa.pub ``` -## Étapes du TP +## Durcissement SSH (durcissement_ssh.sh) -### 1. Copie de la Clé SSH - -Vous devrez automatiser la copie de votre clé SSH publique dans le fichier `~/.ssh/authorized_keys` de manière sécurisée. Assurez-vous de configurer les permissions du fichier de manière adéquate pour empêcher tout accès non autorisé. - -### 2. Durcissement de SSH - -L’objectif est de configurer votre service SSH pour le rendre plus sûr. Vous devrez : -- **Désactiver l'authentification par mot de passe** pour forcer l'utilisation des clés SSH. -- **Limiter l'accès SSH** à certains utilisateurs ou groupes. -- **Désactiver l'accès root** via SSH pour éviter des tentatives d'intrusion sur ce compte sensible. -- **Utilisation d’une Liste Blanche d’Adresses IP pour SSH** Pour une sécurité renforcée, autorisez uniquement des plages d'adresses IP spécifiques à se connecter via SSH. Cette liste blanche limite l'accès à des sources fiables. - -### 3. Installation et Configuration d’un Pare-feu (UFW) - -Installez un pare-feu (UFW) et configurez-le pour permettre uniquement les connexions nécessaires (comme SSH, HTTP, HTTPS). Vous devrez : -- **Installer et activer UFW**. -- **Configurer les règles par défaut** pour bloquer tout le trafic entrant sauf les services essentiels. -- **Autoriser** les connexions nécessaires, comme SSH ou les serveurs web si applicable. - - ### 4. Propositions de Durcissement Simples - -Voici des propositions pour renforcer la sécurité de votre système. Chaque proposition doit être documentée avec précision pour que vous compreniez comment elle renforce la sécurité et dans quel contexte elle est applicable. - -- **Mise en Place d’Authentification à Deux Facteurs (2FA)** - Ajoutez une deuxième couche de sécurité en configurant une authentification à deux facteurs pour SSH. Cela nécessite une confirmation supplémentaire pour accéder au système, généralement via une application d'authentification mobile. - -- **Mise à Jour Automatique des Paquets de Sécurité** - Configurez le système pour qu’il télécharge et installe automatiquement les mises à jour de sécurité afin de ne jamais manquer une correction importante. Cela garantit que votre système reste à jour sans intervention manuelle. - -- **Désactivation des Services Inutiles** - Tous les services réseau actifs doivent être absolument nécessaires. Identifiez et désactivez tous les services qui ne sont pas requis pour réduire les points d'attaque potentiels. - -- **Détection des Modifications dans les Fichiers Système** - Utilisez des outils comme `AIDE` ou `Tripwire` pour surveiller les fichiers critiques du système et être alerté en cas de modification non autorisée. Ces outils peuvent aider à identifier les intrusions et les altérations de fichiers. - -### 5. Personnalisation et Suggestions de Fonctionnalités - -En plus de sécuriser votre système, l’objectif est de personnaliser votre environnement de travail pour le rendre plus efficace et agréable à utiliser. Voici quelques idées à implémenter : - -- **Alias pour Commandes Fréquentes** : Créez des alias dans votre `.bashrc` pour les commandes que vous utilisez régulièrement. Par exemple, créer un alias pour une commande longue et répétitive permet de gagner du temps. - -- **Scripts d'Automatisation Personnalisés** : Développez des scripts pour automatiser des tâches récurrentes, comme la mise à jour des paquets, la surveillance de l’espace disque, ou l’archivage de logs. - -- **Prompt Bash Personnalisé** : Modifiez votre invite de commande (`PS1`) pour inclure des informations utiles, comme le répertoire courant, l’heure, ou l’état du dépôt Git sur lequel vous travaillez. Cela peut améliorer votre productivité en vous donnant des informations en un coup d'œil. - -- **Synchronisation Automatique de Répertoires** : Configurez des scripts pour synchroniser automatiquement vos dossiers de travail entre différentes machines à l'aide de `rsync`. Cela peut être utile si vous travaillez sur plusieurs environnements. - -- **Intégration de Notifications Système** : Intégrez des notifications système qui vous alertent lorsqu’une tâche longue est terminée (comme une compilation ou une sauvegarde). Cela vous permet de continuer à travailler sur autre chose sans avoir à vérifier constamment l’état de vos processus. +```bash +#!/bin/bash +set -x # Activer le mode debug + + +groupadd sshusers +usermod -aG sshusers azerty + +function harden_ssh { + SSH_CONFIG="/etc/ssh/sshd_config" + + # Désactiver l'authentification par mot de passe + sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/' $SSH_CONFIG + + # Désactiver l'accès root via SSH + sed -i 's/PermitRootLogin yes/PermitRootLogin no/' $SSH_CONFIG + + # Limiter l'accès SSH à un groupe spécifique (ex: sshusers) + echo "AllowGroups sshusers" >> $SSH_CONFIG + + # Ajouter une liste blanche d'adresses IP + echo "sshd : 192.168.38.1 : allow" >> /etc/hosts.allow + echo "sshd : ALL : deny" >> /etc/hosts.deny + + # Redémarrer SSH pour appliquer les modifications + systemctl restart ssh + + echo "SSH durci et redémarré." +} + +harden_ssh # Appel de la fonction +``` ### Suggestions d'Idées Supplémentaires From b24a898dd0cc0cbb62d1673992aa73932a3a7cc2 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:10:36 +0200 Subject: [PATCH 07/26] README.md --- README.md | 31 ++++++++++++++++++++++++++++--- 1 file changed, 28 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 352139a..b1b42fa 100644 --- a/README.md +++ b/README.md @@ -78,7 +78,32 @@ function harden_ssh { harden_ssh # Appel de la fonction ``` -### Suggestions d'Idées Supplémentaires +## Pare-feu (pare-feu_ufw.sh) -Poussez encore plus loin la personnalisation et la sécurisation en réfléchissant à d’autres fonctionnalités ou scripts qui pourraient améliorer votre système. -Réfléchissez aux tâches que vous effectuez souvent, aux aspects de la sécurité que vous pourriez renforcer, ou aux améliorations que vous aimeriez avoir dans votre environnement de travail. Soyez créatifs ! +```bash +#!/bin/bash + +# Installation de UFW +sudo apt update +sudo apt install ufw -y + +# Autoriser les connexions SSH +sudo ufw allow ssh + +# Demander l'autorisation pour HTTP et HTTPS si nécessaire +read -p "Autoriser HTTP et HTTPS (y/n) ? " response +if [[ "$response" =~ ^[Yy]$ ]]; then + sudo ufw allow http + sudo ufw allow https +fi + +# Bloquer tout le reste par défaut +sudo ufw default deny incoming +sudo ufw default allow outgoing + +# Activer UFW avec confirmation +echo "y" | sudo ufw enable + +# Vérifier le statut du pare-feu +sudo ufw status verbose +``` From 9c08d5c668c5435e00f5f3d6571f287bbd7d8a23 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:14:04 +0200 Subject: [PATCH 08/26] README.md --- README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/README.md b/README.md index b1b42fa..8e7ebf4 100644 --- a/README.md +++ b/README.md @@ -107,3 +107,28 @@ echo "y" | sudo ufw enable # Vérifier le statut du pare-feu sudo ufw status verbose ``` + +## Mise à jour automatiques (maj_automatique.sh) + +```bash +#!/bin/bash + +# Installation de unattended-upgrades +sudo apt update +sudo apt install unattended-upgrades -y + +# Configurer unattended-upgrades pour activer les mises à jour automatiques de sécurité +sudo dpkg-reconfigure --priority=low unattended-upgrades + +# Activer uniquement les mises à jour de sécurité avec redémarrage automatique +sudo bash -c 'cat > /etc/apt/apt.conf.d/50unattended-upgrades' << EOL +Unattended-Upgrade::Origins-Pattern { + "o=Debian,a=\${distro_codename}-security"; +}; + +Unattended-Upgrade::Automatic-Reboot "true"; +Unattended-Upgrade::Automatic-Reboot-Time "02:00"; +EOL + +echo "Mises à jour automatiques de sécurité activées sans notifications." +``` From 672ee5167390ade68e77cd227d2b319d794b3da8 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:16:52 +0200 Subject: [PATCH 09/26] README.md --- README.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README.md b/README.md index 8e7ebf4..8bb226a 100644 --- a/README.md +++ b/README.md @@ -132,3 +132,21 @@ EOL echo "Mises à jour automatiques de sécurité activées sans notifications." ``` + +## Désactivation des services inutiles (desactivation_services_inutiles.sh) + +```bash +#!/bin/bash + +# Lister les services actifs +echo "Services actifs :" +systemctl list-units --type=service --state=running + +# Demander à l'utilisateur quels services désactiver +read -p "avahi-daemon cups bluetooth ModemManager rpcbind nfs-server nfs-common" services +for service in $services; do + systemctl disable $service + systemctl stop $service + echo "Service $service désactivé." +done +``` From e94ecce7a5618065b1e610ad04f2d1af60d2be57 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:30:22 +0200 Subject: [PATCH 10/26] README.md --- README.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/README.md b/README.md index 8bb226a..861651f 100644 --- a/README.md +++ b/README.md @@ -150,3 +150,35 @@ for service in $services; do echo "Service $service désactivé." done ``` + +## Ajouts d'alias (creation_alias.sh) + +```bash +#!/bin/bash + +# Chemin vers le .bashrc de l'utilisateur +USER_BASHRC="$HOME/.bashrc" + +# Vérifier et créer des alias dans .bashrc de l'utilisateur s'ils n'existent pas déjà +if ! grep -q "alias la='ls -la'" "$USER_BASHRC"; then + echo "alias la='ls -la'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias sr='systemctl restart'" "$USER_BASHRC"; then + echo "alias sr='systemctl restart'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias se='systemctl enable'" "$USER_BASHRC"; then + echo "alias se='systemctl enable'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias update='sudo apt update && sudo apt upgrade -y'" "$USER_BASHRC"; then + echo "alias update='sudo apt update && sudo apt upgrade -y'" >> "$USER_BASHRC" +fi + +# Recharger le fichier de configuration +source ~/.bashrc + +echo "Alias créés et activés pour l'utilisateur $(whoami)." +``` + From bc717c86ff6433121196694b15494eb990ea3ef1 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:32:31 +0200 Subject: [PATCH 11/26] README.md --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 861651f..ab3361c 100644 --- a/README.md +++ b/README.md @@ -182,3 +182,24 @@ source ~/.bashrc echo "Alias créés et activés pour l'utilisateur $(whoami)." ``` +## Personnalisation du prompt Bash (personnalisation_prompt.sh) + +```bash +#!/bin/bash + +# Chemin vers le .bashrc de l'utilisateur +USER_BASHRC="$HOME/.bashrc" + +# Personnalisation du prompt Bash avec des couleurs si non déjà appliquée +if ! grep -q 'PS1="\\\[\\e[0;32m\\\]\\u@\\h \\\[\\e[0;34m\\\]\\w\\\[\\e[0m\\\] $ "' "$USER_BASHRC"; then + echo 'PS1="\[\e[0;32m\]\u@\h \[\e[0;34m\]\w\[\e[0m\] $ "' >> "$USER_BASHRC" + echo "Personnalisation du prompt Bash ajoutée à $USER_BASHRC." +else + echo "La personnalisation du prompt Bash est déjà présente." +fi + +# Recharger le fichier de configuration +source "$USER_BASHRC" + +echo "Prompt Bash personnalisé pour l'utilisateur $(whoami)." +``` From 16ef54cb927d0afd53544a4dd8201f5f00a32433 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:34:56 +0200 Subject: [PATCH 12/26] README.md --- README.md | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/README.md b/README.md index ab3361c..ca48bf5 100644 --- a/README.md +++ b/README.md @@ -203,3 +203,53 @@ source "$USER_BASHRC" echo "Prompt Bash personnalisé pour l'utilisateur $(whoami)." ``` +### Authentification à 2 facteurs (2FA.sh) + +```bash +#!/bin/bash +set -x # Activer le mode debug + +function setup_2fa { + # Vérifier si libpam-google-authenticator est déjà installé + if ! dpkg -l | grep -q libpam-google-authenticator; then + echo "Installation de libpam-google-authenticator..." + sudo apt-get update + sudo apt-get install libpam-google-authenticator -y + else + echo "libpam-google-authenticator est déjà installé." + fi + + # Configurer Google Authenticator pour l'utilisateur actuel + echo "Configuration de Google Authenticator pour l'utilisateur $(whoami)..." + google-authenticator -t -d -f -r 3 -R 30 -W + + # Modifier la configuration PAM pour SSH + echo "Modification de /etc/pam.d/sshd pour ajouter Google Authenticator..." + if ! grep -q "pam_google_authenticator.so" /etc/pam.d/sshd; then + sudo sed -i 's/@include common-auth/#@include common-auth/' /etc/pam.d/sshd + echo "auth required pam_google_authenticator.so" | sudo tee -a /etc/pam.d/sshd + else + echo "Google Authenticator est déjà configuré dans PAM." + fi + + # Activer KbdInteractiveAuthentication et définir AuthenticationMethods dans sshd_config + echo "Modification de /etc/ssh/sshd_config pour autoriser KbdInteractiveAuthentication et configurer AuthenticationMethods..." + sudo sed -i 's/^#*KbdInteractiveAuthentication no/KbdInteractiveAuthentication yes/' /etc/ssh/sshd_config + + # Ajouter AuthenticationMethods publickey,keyboard-interactive si absent + if ! grep -q "^AuthenticationMethods publickey,keyboard-interactive" /etc/ssh/sshd_config; then + echo "AuthenticationMethods publickey,keyboard-interactive" | sudo tee -a /etc/ssh/sshd_config + else + echo "AuthenticationMethods publickey,keyboard-interactive est déjà configuré." + fi + + # Redémarrer le service SSH + echo "Redémarrage du service SSH pour appliquer les modifications..." + sudo systemctl restart ssh + + echo "Authentification à deux facteurs activée pour SSH." +} + +# Appeler la fonction +setup_2fa +``` From d689251dde9bce281a54392add7af7c5974de086 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:38:52 +0200 Subject: [PATCH 13/26] copy_ssh_keys.sh --- Bonnes_Pratiques.md | 105 -------------------------------------------- copy_ssh_keys.sh | 25 +++++++++++ 2 files changed, 25 insertions(+), 105 deletions(-) delete mode 100644 Bonnes_Pratiques.md create mode 100644 copy_ssh_keys.sh diff --git a/Bonnes_Pratiques.md b/Bonnes_Pratiques.md deleted file mode 100644 index 8124f97..0000000 --- a/Bonnes_Pratiques.md +++ /dev/null @@ -1,105 +0,0 @@ -# Bonnes Pratiques pour les Scripts Bash - -Avant de commencer à automatiser la configuration, voici un rappel des **bonnes pratiques** à suivre lors de la création de scripts Bash : - -### 1. **Nommage des Variables et Fonctions** - - Utilisez des noms explicites et en majuscules pour les variables d'environnement (ex. `CONFIG_FILE`). - - Privilégiez les noms de fonctions qui décrivent clairement leur objectif (ex. `secure_ssh_config`). - - Evitez d’utiliser des noms réservés par le shell ou des noms ambigus. - -### 2. **Vérification des Entrées Utilisateur** - - Validez toutes les **entrées utilisateur** avant de les utiliser dans le script pour éviter les erreurs ou les vulnérabilités. - - Utilisez des messages d'erreur clairs et explicites si une entrée est incorrecte ou manquante. - -### 3. **Utilisation de Fichiers Sourcés** - - Placez les différentes fonctions dans des fichiers séparés pour maintenir une **modularité** et faciliter la maintenance du code. - - Utilisez des commentaires clairs pour décrire l’objectif de chaque fonction. - - Dans le script principal, **sourcez** les fichiers en vérifiant leur existence et leur accessibilité avant de les exécuter. - -### 4. **Gestion des Permissions** - - Assurez-vous que les fichiers et dossiers créés ont les **permissions appropriées**. Des permissions trop permissives peuvent être une faille de sécurité. - - Vérifiez et ajustez les permissions des fichiers sensibles comme les clés SSH, les fichiers de configuration ou les journaux. - -### 5. **Gestion des Erreurs** - - Utilisez `set -e` pour arrêter le script en cas d’erreur non gérée. - - Traitez les erreurs de manière explicite avec des messages clairs. - - Chaque fonction doit renvoyer un statut de succès ou d’échec (`0` pour succès, `1` pour échec) et documenter ses points de sortie. - -### 6. **Sécurisation du Script** - - Évitez l'exécution de commandes avec des **entrées non vérifiées**. - - Utilisez `$(...)` pour exécuter des commandes plutôt que des backticks `` `...` ``. - - Réduisez les privilèges **root** au strict minimum. Évitez d'exécuter tout le script avec des privilèges administrateur si ce n'est pas nécessaire. - -## Structure des Scripts : Sourcer des Fonctions - -Pour maintenir un code **organisé** et **facile à maintenir**, le script principal devra **sourcer** plusieurs fichiers qui contiendront les différentes fonctions de configuration. Voici un schéma conceptuel de la structure à adopter : - -### Schéma de la Gestion des Fichiers Sourcés - -``` -main_script.sh - ├── functions/ - │ ├── ssh_hardening.sh # Durcissement de SSH - │ ├── firewall_setup.sh # Installation et configuration du pare-feu UFW - │ ├── user_management.sh # Gestion des utilisateurs - │ └── log_management.sh # Configuration des logs de sécurité - └── config/ - └── config_file.sh # Fichier de configuration pour stocker les variables globales -``` - -### 1. **Script Principal** (`main_script.sh`) - - Ce script sera l’entrée principale du projet. Il devra **sourcer** les fonctions nécessaires à partir des fichiers placés dans le dossier `functions/`. - - Il vérifiera que tous les fichiers de configuration et de fonctions sont bien disponibles avant de les exécuter. - -### 2. **Gestion des Fichiers Sourcés** - - **Fonctions** : Chaque fichier dans le répertoire `functions/` contiendra une ou plusieurs fonctions spécifiques à une tâche précise (par exemple, durcir SSH, configurer UFW). - - **Configuration** : Un fichier dans le dossier `config/` stockera les variables globales que vous pourrez réutiliser dans les différentes fonctions (exemple : chemins des fichiers de logs, utilisateurs autorisés à utiliser SSH). - -### Exemple de Sourçage de Fichiers dans le Script Principal - -```bash -#!/bin/bash - -# Chargement des fonctions depuis les fichiers sourcés -source ./functions/ssh_hardening.sh || { echo "Erreur : Impossible de sourcer ssh_hardening.sh"; exit 1; } -source ./functions/firewall_setup.sh || { echo "Erreur : Impossible de sourcer firewall_setup.sh"; exit 1; } -source ./config/config_file.sh || { echo "Erreur : Impossible de charger le fichier de configuration"; exit 1; } - -# Fonction principale qui appelle les différentes fonctions de durcissement -main(){ - echo "Démarrage du processus d'automatisation et de durcissement..." - - secure_ssh - setup_firewall - manage_users - - echo "Processus terminé avec succès." -} - -# Appel de la fonction principale -main -``` - -### 3. **Gestion des Entrées Utilisateur** - Lors de la configuration, vous devrez souvent demander des informations à l'utilisateur, comme son adresse IP ou son nom d'utilisateur pour SSH. Voici comment vous devrez gérer ces entrées : - -- **Validation des entrées** : Assurez-vous que les informations fournies par l'utilisateur sont valides (par exemple, vérifier que l'adresse IP est bien formatée). -- **Valeurs par défaut** : Proposez des valeurs par défaut que l’utilisateur pourra accepter ou modifier. -- **Gestion des erreurs** : En cas d’erreur d’entrée, affichez un message d’aide expliquant comment corriger l’entrée. - -### Exemple de Gestion d'Entrées Utilisateur - -```bash -read -p "Entrez l'adresse IP autorisée pour SSH (ou laissez vide pour utiliser l'adresse par défaut) : " USER_IP -USER_IP=${USER_IP:-"192.168.0.1"} - -# Vérification de l'adresse IP -if [[ ! "$USER_IP" =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]]; then - echo "Erreur : Adresse IP non valide" - exit 1 -fi - -echo "Adresse IP $USER_IP autorisée pour SSH" -``` - - diff --git a/copy_ssh_keys.sh b/copy_ssh_keys.sh new file mode 100644 index 0000000..6687e0f --- /dev/null +++ b/copy_ssh_keys.sh @@ -0,0 +1,25 @@ +```bash +#!/bin/bash + +# Vérification de l'existence de la clé SSH +if [ ! -f ~/.ssh/id_rsa ]; then + echo "Aucune clé SSH trouvée. Création d'une nouvelle paire de clés..." + ssh-keygen -t rsa -b 4096 -N "" -f ~/.ssh/id_rsa + echo "Clé SSH créée : ~/.ssh/id_rsa.pub" +else + echo "Une clé SSH existe déjà : ~/.ssh/id_rsa.pub" +fi + +# Afficher la clé publique et l'ajouter à authorized_keys +cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys + +# Fixer les permissions du fichier authorized_keys +chmod 600 ~/.ssh/authorized_keys + +# Assurer que le répertoire .ssh a les bonnes permissions +chmod 700 ~/.ssh + +echo "Clé SSH ajoutée avec succès au fichier authorized_keys." +echo "Clé publique :" +cat ~/.ssh/id_rsa.pub +``` From 1a1abc6a8c59a6ef5bcbf4c59b11cc1bd740bb34 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:39:35 +0200 Subject: [PATCH 14/26] copy_ssh_keys.sh --- copy_ssh_keys.sh | 2 -- 1 file changed, 2 deletions(-) diff --git a/copy_ssh_keys.sh b/copy_ssh_keys.sh index 6687e0f..da8480e 100644 --- a/copy_ssh_keys.sh +++ b/copy_ssh_keys.sh @@ -1,4 +1,3 @@ -```bash #!/bin/bash # Vérification de l'existence de la clé SSH @@ -22,4 +21,3 @@ chmod 700 ~/.ssh echo "Clé SSH ajoutée avec succès au fichier authorized_keys." echo "Clé publique :" cat ~/.ssh/id_rsa.pub -``` From ece32e2980fda4aa534eac3983bbfbe5749e83fb Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:40:24 +0200 Subject: [PATCH 15/26] README.md --- README.md | 240 ------------------------------------------------------ 1 file changed, 240 deletions(-) diff --git a/README.md b/README.md index ca48bf5..44e9924 100644 --- a/README.md +++ b/README.md @@ -13,243 +13,3 @@ Nous avons fait : - Personnalisation du prompt Bash. - 2FA (via google authenticator). - Script qui éxecute tous les autres. - -## Copie de la clé SSH (copy_key_ssh.sh) - -```bash -#!/bin/bash - -# Vérification de l'existence de la clé SSH -if [ ! -f ~/.ssh/id_rsa ]; then - echo "Aucune clé SSH trouvée. Création d'une nouvelle paire de clés..." - ssh-keygen -t rsa -b 4096 -N "" -f ~/.ssh/id_rsa - echo "Clé SSH créée : ~/.ssh/id_rsa.pub" -else - echo "Une clé SSH existe déjà : ~/.ssh/id_rsa.pub" -fi - -# Afficher la clé publique et l'ajouter à authorized_keys -cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys - -# Fixer les permissions du fichier authorized_keys -chmod 600 ~/.ssh/authorized_keys - -# Assurer que le répertoire .ssh a les bonnes permissions -chmod 700 ~/.ssh - -echo "Clé SSH ajoutée avec succès au fichier authorized_keys." -echo "Clé publique :" -cat ~/.ssh/id_rsa.pub - -``` - -## Durcissement SSH (durcissement_ssh.sh) - -```bash -#!/bin/bash -set -x # Activer le mode debug - - -groupadd sshusers -usermod -aG sshusers azerty - -function harden_ssh { - SSH_CONFIG="/etc/ssh/sshd_config" - - # Désactiver l'authentification par mot de passe - sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/' $SSH_CONFIG - - # Désactiver l'accès root via SSH - sed -i 's/PermitRootLogin yes/PermitRootLogin no/' $SSH_CONFIG - - # Limiter l'accès SSH à un groupe spécifique (ex: sshusers) - echo "AllowGroups sshusers" >> $SSH_CONFIG - - # Ajouter une liste blanche d'adresses IP - echo "sshd : 192.168.38.1 : allow" >> /etc/hosts.allow - echo "sshd : ALL : deny" >> /etc/hosts.deny - - # Redémarrer SSH pour appliquer les modifications - systemctl restart ssh - - echo "SSH durci et redémarré." -} - -harden_ssh # Appel de la fonction -``` - -## Pare-feu (pare-feu_ufw.sh) - -```bash -#!/bin/bash - -# Installation de UFW -sudo apt update -sudo apt install ufw -y - -# Autoriser les connexions SSH -sudo ufw allow ssh - -# Demander l'autorisation pour HTTP et HTTPS si nécessaire -read -p "Autoriser HTTP et HTTPS (y/n) ? " response -if [[ "$response" =~ ^[Yy]$ ]]; then - sudo ufw allow http - sudo ufw allow https -fi - -# Bloquer tout le reste par défaut -sudo ufw default deny incoming -sudo ufw default allow outgoing - -# Activer UFW avec confirmation -echo "y" | sudo ufw enable - -# Vérifier le statut du pare-feu -sudo ufw status verbose -``` - -## Mise à jour automatiques (maj_automatique.sh) - -```bash -#!/bin/bash - -# Installation de unattended-upgrades -sudo apt update -sudo apt install unattended-upgrades -y - -# Configurer unattended-upgrades pour activer les mises à jour automatiques de sécurité -sudo dpkg-reconfigure --priority=low unattended-upgrades - -# Activer uniquement les mises à jour de sécurité avec redémarrage automatique -sudo bash -c 'cat > /etc/apt/apt.conf.d/50unattended-upgrades' << EOL -Unattended-Upgrade::Origins-Pattern { - "o=Debian,a=\${distro_codename}-security"; -}; - -Unattended-Upgrade::Automatic-Reboot "true"; -Unattended-Upgrade::Automatic-Reboot-Time "02:00"; -EOL - -echo "Mises à jour automatiques de sécurité activées sans notifications." -``` - -## Désactivation des services inutiles (desactivation_services_inutiles.sh) - -```bash -#!/bin/bash - -# Lister les services actifs -echo "Services actifs :" -systemctl list-units --type=service --state=running - -# Demander à l'utilisateur quels services désactiver -read -p "avahi-daemon cups bluetooth ModemManager rpcbind nfs-server nfs-common" services -for service in $services; do - systemctl disable $service - systemctl stop $service - echo "Service $service désactivé." -done -``` - -## Ajouts d'alias (creation_alias.sh) - -```bash -#!/bin/bash - -# Chemin vers le .bashrc de l'utilisateur -USER_BASHRC="$HOME/.bashrc" - -# Vérifier et créer des alias dans .bashrc de l'utilisateur s'ils n'existent pas déjà -if ! grep -q "alias la='ls -la'" "$USER_BASHRC"; then - echo "alias la='ls -la'" >> "$USER_BASHRC" -fi - -if ! grep -q "alias sr='systemctl restart'" "$USER_BASHRC"; then - echo "alias sr='systemctl restart'" >> "$USER_BASHRC" -fi - -if ! grep -q "alias se='systemctl enable'" "$USER_BASHRC"; then - echo "alias se='systemctl enable'" >> "$USER_BASHRC" -fi - -if ! grep -q "alias update='sudo apt update && sudo apt upgrade -y'" "$USER_BASHRC"; then - echo "alias update='sudo apt update && sudo apt upgrade -y'" >> "$USER_BASHRC" -fi - -# Recharger le fichier de configuration -source ~/.bashrc - -echo "Alias créés et activés pour l'utilisateur $(whoami)." -``` - -## Personnalisation du prompt Bash (personnalisation_prompt.sh) - -```bash -#!/bin/bash - -# Chemin vers le .bashrc de l'utilisateur -USER_BASHRC="$HOME/.bashrc" - -# Personnalisation du prompt Bash avec des couleurs si non déjà appliquée -if ! grep -q 'PS1="\\\[\\e[0;32m\\\]\\u@\\h \\\[\\e[0;34m\\\]\\w\\\[\\e[0m\\\] $ "' "$USER_BASHRC"; then - echo 'PS1="\[\e[0;32m\]\u@\h \[\e[0;34m\]\w\[\e[0m\] $ "' >> "$USER_BASHRC" - echo "Personnalisation du prompt Bash ajoutée à $USER_BASHRC." -else - echo "La personnalisation du prompt Bash est déjà présente." -fi - -# Recharger le fichier de configuration -source "$USER_BASHRC" - -echo "Prompt Bash personnalisé pour l'utilisateur $(whoami)." -``` -### Authentification à 2 facteurs (2FA.sh) - -```bash -#!/bin/bash -set -x # Activer le mode debug - -function setup_2fa { - # Vérifier si libpam-google-authenticator est déjà installé - if ! dpkg -l | grep -q libpam-google-authenticator; then - echo "Installation de libpam-google-authenticator..." - sudo apt-get update - sudo apt-get install libpam-google-authenticator -y - else - echo "libpam-google-authenticator est déjà installé." - fi - - # Configurer Google Authenticator pour l'utilisateur actuel - echo "Configuration de Google Authenticator pour l'utilisateur $(whoami)..." - google-authenticator -t -d -f -r 3 -R 30 -W - - # Modifier la configuration PAM pour SSH - echo "Modification de /etc/pam.d/sshd pour ajouter Google Authenticator..." - if ! grep -q "pam_google_authenticator.so" /etc/pam.d/sshd; then - sudo sed -i 's/@include common-auth/#@include common-auth/' /etc/pam.d/sshd - echo "auth required pam_google_authenticator.so" | sudo tee -a /etc/pam.d/sshd - else - echo "Google Authenticator est déjà configuré dans PAM." - fi - - # Activer KbdInteractiveAuthentication et définir AuthenticationMethods dans sshd_config - echo "Modification de /etc/ssh/sshd_config pour autoriser KbdInteractiveAuthentication et configurer AuthenticationMethods..." - sudo sed -i 's/^#*KbdInteractiveAuthentication no/KbdInteractiveAuthentication yes/' /etc/ssh/sshd_config - - # Ajouter AuthenticationMethods publickey,keyboard-interactive si absent - if ! grep -q "^AuthenticationMethods publickey,keyboard-interactive" /etc/ssh/sshd_config; then - echo "AuthenticationMethods publickey,keyboard-interactive" | sudo tee -a /etc/ssh/sshd_config - else - echo "AuthenticationMethods publickey,keyboard-interactive est déjà configuré." - fi - - # Redémarrer le service SSH - echo "Redémarrage du service SSH pour appliquer les modifications..." - sudo systemctl restart ssh - - echo "Authentification à deux facteurs activée pour SSH." -} - -# Appeler la fonction -setup_2fa -``` From 69822e44bbe05d6dde396c57c3eb195b66926cd1 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:41:19 +0200 Subject: [PATCH 16/26] durcissement_ssh.sh --- durcissement_ssh.sh | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 durcissement_ssh.sh diff --git a/durcissement_ssh.sh b/durcissement_ssh.sh new file mode 100644 index 0000000..b880074 --- /dev/null +++ b/durcissement_ssh.sh @@ -0,0 +1,30 @@ +#!/bin/bash +set -x # Activer le mode debug + + +groupadd sshusers +usermod -aG sshusers azerty + +function harden_ssh { + SSH_CONFIG="/etc/ssh/sshd_config" + + # Désactiver l'authentification par mot de passe + sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/' $SSH_CONFIG + + # Désactiver l'accès root via SSH + sed -i 's/PermitRootLogin yes/PermitRootLogin no/' $SSH_CONFIG + + # Limiter l'accès SSH à un groupe spécifique (ex: sshusers) + echo "AllowGroups sshusers" >> $SSH_CONFIG + + # Ajouter une liste blanche d'adresses IP + echo "sshd : 192.168.38.1 : allow" >> /etc/hosts.allow + echo "sshd : ALL : deny" >> /etc/hosts.deny + + # Redémarrer SSH pour appliquer les modifications + systemctl restart ssh + + echo "SSH durci et redémarré." +} + +harden_ssh # Appel de la fonction From f050524236ee6d619a29199fe2b52fb475757c54 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:43:40 +0200 Subject: [PATCH 17/26] pare-feu_ufw.sh --- pare-feu_ufw.sh | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 pare-feu_ufw.sh diff --git a/pare-feu_ufw.sh b/pare-feu_ufw.sh new file mode 100644 index 0000000..dafad0a --- /dev/null +++ b/pare-feu_ufw.sh @@ -0,0 +1,25 @@ +#!/bin/bash + +# Installation de UFW +sudo apt update +sudo apt install ufw -y + +# Autoriser les connexions SSH +sudo ufw allow ssh + +# Demander l'autorisation pour HTTP et HTTPS si nécessaire +read -p "Autoriser HTTP et HTTPS (y/n) ? " response +if [[ "$response" =~ ^[Yy]$ ]]; then + sudo ufw allow http + sudo ufw allow https +fi + +# Bloquer tout le reste par défaut +sudo ufw default deny incoming +sudo ufw default allow outgoing + +# Activer UFW avec confirmation +echo "y" | sudo ufw enable + +# Vérifier le statut du pare-feu +sudo ufw status verbose From 157820ba01fc79f53202962c0e138c1fa9be372f Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:45:51 +0200 Subject: [PATCH 18/26] maj_automatiques.sh --- maj_automatiques.sh | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 maj_automatiques.sh diff --git a/maj_automatiques.sh b/maj_automatiques.sh new file mode 100644 index 0000000..6f35f01 --- /dev/null +++ b/maj_automatiques.sh @@ -0,0 +1,20 @@ +#!/bin/bash + +# Installation de unattended-upgrades +sudo apt update +sudo apt install unattended-upgrades -y + +# Configurer unattended-upgrades pour activer les mises à jour automatiques de sécurité +sudo dpkg-reconfigure --priority=low unattended-upgrades + +# Activer uniquement les mises à jour de sécurité avec redémarrage automatique +sudo bash -c 'cat > /etc/apt/apt.conf.d/50unattended-upgrades' << EOL +Unattended-Upgrade::Origins-Pattern { + "o=Debian,a=\${distro_codename}-security"; +}; + +Unattended-Upgrade::Automatic-Reboot "true"; +Unattended-Upgrade::Automatic-Reboot-Time "02:00"; +EOL + +echo "Mises à jour automatiques de sécurité activées sans notifications." From 8538bc33d55d4112701cb036727e42d58fdf067e Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:47:09 +0200 Subject: [PATCH 19/26] desactivation_services_inutiles.sh --- desactivation_services_inutiles.sh | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 desactivation_services_inutiles.sh diff --git a/desactivation_services_inutiles.sh b/desactivation_services_inutiles.sh new file mode 100644 index 0000000..9b7b9f2 --- /dev/null +++ b/desactivation_services_inutiles.sh @@ -0,0 +1,24 @@ +#!/bin/bash + +# Lister les services actifs +echo "Services actifs :" +systemctl list-units --type=service --state=running + +# Liste des services potentiellement inutiles +services="avahi-daemon cups bluetooth ModemManager rpcbind nfs-server nfs-common" + +# Demander confirmation pour désactiver chaque service +for service in $services; do + if systemctl is-active --quiet "$service"; then + read -p "Voulez-vous désactiver le service $service ? (y/n) " response + if [[ "$response" =~ ^[Yy]$ ]]; then + sudo systemctl disable "$service" + sudo systemctl stop "$service" + echo "Service $service désactivé et arrêté." + else + echo "Service $service laissé actif." + fi + else + echo "Service $service n'est pas actif, aucune action nécessaire." + fi +done From b92abd0b097aee9cddc09b03e7160cc2482c5094 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:49:09 +0200 Subject: [PATCH 20/26] Create creation_alias.sh --- creation_alias.sh | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 creation_alias.sh diff --git a/creation_alias.sh b/creation_alias.sh new file mode 100644 index 0000000..27c4cb2 --- /dev/null +++ b/creation_alias.sh @@ -0,0 +1,26 @@ +#!/bin/bash + +# Chemin vers le .bashrc de l'utilisateur +USER_BASHRC="$HOME/.bashrc" + +# Vérifier et créer des alias dans .bashrc de l'utilisateur s'ils n'existent pas déjà +if ! grep -q "alias la='ls -la'" "$USER_BASHRC"; then + echo "alias la='ls -la'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias sr='systemctl restart'" "$USER_BASHRC"; then + echo "alias sr='systemctl restart'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias se='systemctl enable'" "$USER_BASHRC"; then + echo "alias se='systemctl enable'" >> "$USER_BASHRC" +fi + +if ! grep -q "alias update='sudo apt update && sudo apt upgrade -y'" "$USER_BASHRC"; then + echo "alias update='sudo apt update && sudo apt upgrade -y'" >> "$USER_BASHRC" +fi + +# Recharger le fichier de configuration +source ~/.bashrc + +echo "Alias créés et activés pour l'utilisateur $(whoami)." From 38cafb6f40e57eac12ca9a0c3a792c2b3fdf7f6c Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:50:38 +0200 Subject: [PATCH 21/26] Create personnalisation_prompt.sh --- personnalisation_prompt.sh | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 personnalisation_prompt.sh diff --git a/personnalisation_prompt.sh b/personnalisation_prompt.sh new file mode 100644 index 0000000..6bad92f --- /dev/null +++ b/personnalisation_prompt.sh @@ -0,0 +1,17 @@ +#!/bin/bash + +# Chemin vers le .bashrc de l'utilisateur +USER_BASHRC="$HOME/.bashrc" + +# Personnalisation du prompt Bash avec des couleurs si non déjà appliquée +if ! grep -q 'PS1="\\\[\\e[0;32m\\\]\\u@\\h \\\[\\e[0;34m\\\]\\w\\\[\\e[0m\\\] $ "' "$USER_BASHRC"; then + echo 'PS1="\[\e[0;32m\]\u@\h \[\e[0;34m\]\w\[\e[0m\] $ "' >> "$USER_BASHRC" + echo "Personnalisation du prompt Bash ajoutée à $USER_BASHRC." +else + echo "La personnalisation du prompt Bash est déjà présente." +fi + +# Recharger le fichier de configuration +source "$USER_BASHRC" + +echo "Prompt Bash personnalisé pour l'utilisateur $(whoami)." From d9032c3bb172d3ac1cdb5ebc5e54112f2649a3a4 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:51:52 +0200 Subject: [PATCH 22/26] Create 2FA.sh --- 2FA.sh | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 2FA.sh diff --git a/2FA.sh b/2FA.sh new file mode 100644 index 0000000..ee979df --- /dev/null +++ b/2FA.sh @@ -0,0 +1,31 @@ +#!/bin/bash +set -x # Activer le mode debug + +function setup_2fa { + # Vérifier si libpam-google-authenticator est déjà installé + if ! dpkg -l | grep -q libpam-google-authenticator; then + echo "Installation de libpam-google-authenticator..." + sudo apt-get update + sudo apt-get install libpam-google-authenticator -y + else + echo "libpam-google-authenticator est déjà installé." + fi + + # Configurer Google Authenticator pour l'utilisateur actuel + echo "Configuration de Google Authenticator pour l'utilisateur $(whoami)..." + google-authenticator -t -d -f -r 3 -R 30 -W + + # Modifier la configuration PAM pour SSH + echo "Modification de /etc/pam.d/sshd pour ajouter Google Authenticator..." + if ! grep -q "pam_google_authenticator.so" /etc/pam.d/sshd; then + sudo sed -i 's/@include common-auth/#@include common-auth/' /etc/pam.d/sshd + echo "auth required pam_google_authenticator.so" | sudo tee -a /etc/pam.d/sshd + else + echo "Google Authenticator est déjà configuré dans PAM." + fi + + # Activer KbdInteractiveAuthentication et définir AuthenticationMethods dans sshd_config + echo "Modification de /etc/ssh/sshd_config pour autoriser KbdInteractiveAuthentication et configurer AuthenticationMethods..." + sudo sed -i 's/^#*KbdInteractiveAuthentication no/KbdInteractiveAuthentication yes/' /etc/ssh/sshd_config + + # Ajouter AuthenticationMethods publickey,keyboard-interactive From c44df18de83f2812912f9f4ca131522c7a446805 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:52:37 +0200 Subject: [PATCH 23/26] Update 2FA.sh --- 2FA.sh | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/2FA.sh b/2FA.sh index ee979df..024a642 100644 --- a/2FA.sh +++ b/2FA.sh @@ -28,4 +28,19 @@ function setup_2fa { echo "Modification de /etc/ssh/sshd_config pour autoriser KbdInteractiveAuthentication et configurer AuthenticationMethods..." sudo sed -i 's/^#*KbdInteractiveAuthentication no/KbdInteractiveAuthentication yes/' /etc/ssh/sshd_config - # Ajouter AuthenticationMethods publickey,keyboard-interactive + # Ajouter AuthenticationMethods publickey,keyboard-interactive si absent + if ! grep -q "^AuthenticationMethods publickey,keyboard-interactive" /etc/ssh/sshd_config; then + echo "AuthenticationMethods publickey,keyboard-interactive" | sudo tee -a /etc/ssh/sshd_config + else + echo "AuthenticationMethods publickey,keyboard-interactive est déjà configuré." + fi + + # Redémarrer le service SSH + echo "Redémarrage du service SSH pour appliquer les modifications..." + sudo systemctl restart ssh + + echo "Authentification à deux facteurs activée pour SSH." +} + +# Appeler la fonction +setup_2fa From c11fd0aa0b555761e13cd43ae828722c82341085 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:53:22 +0200 Subject: [PATCH 24/26] Create run_all.sh --- run_all.sh | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 run_all.sh diff --git a/run_all.sh b/run_all.sh new file mode 100644 index 0000000..d4cc58d --- /dev/null +++ b/run_all.sh @@ -0,0 +1,48 @@ +#!/bin/bash + +# Fonction pour vérifier le statut d'une commande +check_status() { + if [ $? -ne 0 ]; then + echo "Échec à l'étape : $1" + exit 1 + else + echo "Succès à l'étape : $1" + fi +} + +# Étape 1 : Copie de la clé SSH +echo "Lancement de la copie de la clé SSH..." +./copy_ssh_key.sh +check_status "Copie de la clé SSH" + +# Étape 2 : Durcissement de SSH +echo "Lancement du durcissement de SSH..." +sudo ./durcissement_ssh.sh +check_status "Durcissement de SSH" + +# Étape 3 : Installation et configuration du pare-feu UFW +echo "Lancement de l'installation et configuration de UFW..." +sudo ./parefeu_ufw.sh +check_status "Installation et configuration du pare-feu UFW" + +# Étape 4 : Désactivation des services inutiles +echo "Désactivation des services inutiles..." +sudo ./desactivation_services_inutile.sh +check_status "Désactivation des services inutiles" + +echo "Lancement du script des maj auto..." +sudo ./maj_automatique.sh +check_status "Mise à jour automatiques activer" + +echo "Création d'alias..." +./creation_alias.sh +check_status "Création d'alias fréquents" + +echo "Personnalisation du prompt..." +./personnalisation_prompt.sh +check_status "Personnalisation du prompt Bash" + +echo "Création de l’authentification à 2 facteurs..." +./2FA.sh +check_status "Mise en place de google authenticator” +echo "Toutes les étapes ont été exécutées avec succès !" From 451b6ab0dd12feea29a2f7c2c003df0d75fb86dc Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:58:27 +0200 Subject: [PATCH 25/26] Delete LICENSE --- LICENSE | 674 -------------------------------------------------------- 1 file changed, 674 deletions(-) delete mode 100644 LICENSE diff --git a/LICENSE b/LICENSE deleted file mode 100644 index f288702..0000000 --- a/LICENSE +++ /dev/null @@ -1,674 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 3, 29 June 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU General Public License is a free, copyleft license for -software and other kinds of works. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -the GNU General Public License is intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. We, the Free Software Foundation, use the -GNU General Public License for most of our software; it applies also to -any other work released this way by its authors. You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - To protect your rights, we need to prevent others from denying you -these rights or asking you to surrender the rights. Therefore, you have -certain responsibilities if you distribute copies of the software, or if -you modify it: responsibilities to respect the freedom of others. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must pass on to the recipients the same -freedoms that you received. You must make sure that they, too, receive -or can get the source code. And you must show them these terms so they -know their rights. - - Developers that use the GNU GPL protect your rights with two steps: -(1) assert copyright on the software, and (2) offer you this License -giving you legal permission to copy, distribute and/or modify it. - - For the developers' and authors' protection, the GPL clearly explains -that there is no warranty for this free software. For both users' and -authors' sake, the GPL requires that modified versions be marked as -changed, so that their problems will not be attributed erroneously to -authors of previous versions. - - Some devices are designed to deny users access to install or run -modified versions of the software inside them, although the manufacturer -can do so. This is fundamentally incompatible with the aim of -protecting users' freedom to change the software. The systematic -pattern of such abuse occurs in the area of products for individuals to -use, which is precisely where it is most unacceptable. Therefore, we -have designed this version of the GPL to prohibit the practice for those -products. If such problems arise substantially in other domains, we -stand ready to extend this provision to those domains in future versions -of the GPL, as needed to protect the freedom of users. - - Finally, every program is threatened constantly by software patents. -States should not allow patents to restrict development and use of -software on general-purpose computers, but in those that do, we wish to -avoid the special danger that patents applied to a free program could -make it effectively proprietary. To prevent this, the GPL assures that -patents cannot be used to render the program non-free. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Use with the GNU Affero General Public License. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU Affero General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the special requirements of the GNU Affero General Public License, -section 13, concerning interaction through a network will apply to the -combination as such. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If the program does terminal interaction, make it output a short -notice like this when it starts in an interactive mode: - - Copyright (C) - This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, your program's commands -might be different; for a GUI interface, you would use an "about box". - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU GPL, see -. - - The GNU General Public License does not permit incorporating your program -into proprietary programs. If your program is a subroutine library, you -may consider it more useful to permit linking proprietary applications with -the library. If this is what you want to do, use the GNU Lesser General -Public License instead of this License. But first, please read -. From c7a3ba457815a5318389303241991bca4b6f5812 Mon Sep 17 00:00:00 2001 From: coudoupel Date: Fri, 25 Oct 2024 09:58:41 +0200 Subject: [PATCH 26/26] Delete Notation.md --- Notation.md | 56 ----------------------------------------------------- 1 file changed, 56 deletions(-) delete mode 100644 Notation.md diff --git a/Notation.md b/Notation.md deleted file mode 100644 index 7e666df..0000000 --- a/Notation.md +++ /dev/null @@ -1,56 +0,0 @@ -# Grille de Notation pour le TP : Automatisation et Durcissement d’un Système Debian - -## Obligatoire (Total : 15 points) - -### 1. **Copie de la Clé SSH** (5 points) -- Automatisation correcte et sécurisée de la copie de la clé SSH publique. -- Gestion appropriée des permissions des fichiers. -- Bonne gestion des erreurs en cas d’échec ou d’entrée utilisateur incorrecte. - -### 2. **Durcissement de SSH** (5 points) -- Désactivation de l'authentification par mot de passe. -- Limitation de l'accès SSH à des utilisateurs spécifiques. -- Désactivation de l'accès root via SSH. -- Utilisation d'une liste blanche d'adresses IP. - -### 3. **Installation et Configuration d’un Pare-feu (UFW)** (5 points) -- Installation correcte de UFW. -- Configuration des règles par défaut pour bloquer le trafic non autorisé. -- Autorisation des connexions nécessaires (SSH, HTTP, HTTPS si applicable). -- Gestion appropriée des erreurs et des permissions. - -## Au Choix (Total : 10 points - minimum un point à choisir) - -### 4. **Propositions de Durcissement Simples** (jusqu’à 10 points) -- Mise en place de l'authentification à deux facteurs (2FA). -- Mise à jour automatique des paquets de sécurité. -- Désactivation des services inutiles. -- Surveillance des fichiers critiques avec AIDE ou Tripwire. - -### 5. **Personnalisation et Suggestions de Fonctionnalités** (jusqu’à 10 points) -- Création d'alias pour des commandes fréquentes. -- Développement de scripts d'automatisation personnalisés. -- Personnalisation du prompt Bash. -- Synchronisation automatique des répertoires. -- Intégration de notifications système. - -## Bonus (jusqu’à 5 points) - -### **Suggestions d'Idées Supplémentaires** -- Implémentation d’idées créatives supplémentaires en lien avec la sécurité ou l’automatisation. -- Innovations qui montrent une réflexion personnelle et avancée dans la personnalisation ou la sécurité du système. - -## Critères de Réussite - -- **Respect des bonnes pratiques** : clarté du code, commentaires, modularité avec le sourçage des fonctions. -- **Gestion des erreurs** : traitement des erreurs d’exécution, gestion des entrées utilisateur. -- **Originalité et innovation** : capacité à proposer des solutions originales et adaptées aux besoins des utilisateurs. - -## Barème Total - -| Critère | Points Disponibles | -| ----------------------------------------- | ------------------ | -| Obligatoire (1, 2, 3) | 15 | -| Au choix (4, 5) | 10 | -| Bonus | 5 | -| **Total** | **30** |