diff --git a/config.yml b/config.yml index 64e7d56..687a3fb 100644 --- a/config.yml +++ b/config.yml @@ -37,17 +37,11 @@ author: menu: main: - name: "Blog" - url: "" - weight: 1 + pageRef: "/" + weight: 10 - name: "Tags" - url: "tags/" - weight: 2 - - name: "About" - url: "about/" - weight: 3 - - name: "Talks" - url: "talks/" - weight: 4 + pageRef: "/tags" + weight: 20 languages: en: @@ -73,14 +67,8 @@ languages: menu: main: - name: "Articles" - url: "" - weight: 1 + pageRef: "/" + weight: 10 - name: "Tags" - url: "tags/" - weight: 2 - - name: "À propos" - url: "a-propos/" - weight: 3 - - name: "Conférences" - url: "conferences/" - weight: 4 + pageRef: "/tags" + weight: 20 diff --git a/content/en/about.md b/content/en/about.md index 3726126..8ce6ae7 100644 --- a/content/en/about.md +++ b/content/en/about.md @@ -2,6 +2,10 @@ title: "Who am I?" date: !!timestamp '2017-07-31T00:50:07+02:00' update: !!timestamp '2021-07-24T00:00:00+01:00' +menu: + main: + name: "About" + weight: 30 --- Hello! `nemunaire` here, aka Pierre-Olivier; I am an engineer (and passionate about [how things work](https://en.wikipedia.org/wiki/Wikipedia)), a teacher (and a pioneer of [gamification](https://en.wikipedia.org/wiki/Gamification) in my classes), a cook (and an advocate of [limiting the ecological footprint in our eating habits](https://en.wikipedia.org/wiki/Vegetarianism)) and I also fight against the hold of [GAFAM](https://en.wikipedia.org/wiki/GAFAM) on our time. Besides, I generally adhere to [stoicism](https://en.wikipedia.org/wiki/Stoicism). I love typography, challenges, chocolate (or vanilla?? the choice is too hard) and so many other things! diff --git a/static/post/kernel_configs/geb.config b/content/en/post/kernel_configs/geb.config similarity index 100% rename from static/post/kernel_configs/geb.config rename to content/en/post/kernel_configs/geb.config diff --git a/static/post/kernel_configs/hathor.config b/content/en/post/kernel_configs/hathor.config similarity index 100% rename from static/post/kernel_configs/hathor.config rename to content/en/post/kernel_configs/hathor.config diff --git a/content/en/post/kernel_configs.md b/content/en/post/kernel_configs/index.md similarity index 100% rename from content/en/post/kernel_configs.md rename to content/en/post/kernel_configs/index.md diff --git a/static/post/kernel_configs/nout.config b/content/en/post/kernel_configs/nout.config similarity index 100% rename from static/post/kernel_configs/nout.config rename to content/en/post/kernel_configs/nout.config diff --git a/static/post/kernel_configs/ouaset.config b/content/en/post/kernel_configs/ouaset.config similarity index 100% rename from static/post/kernel_configs/ouaset.config rename to content/en/post/kernel_configs/ouaset.config diff --git a/static/post/kernel_configs/oupaout.config b/content/en/post/kernel_configs/oupaout.config similarity index 100% rename from static/post/kernel_configs/oupaout.config rename to content/en/post/kernel_configs/oupaout.config diff --git a/static/post/kernel_configs/rhakotis.config b/content/en/post/kernel_configs/rhakotis.config similarity index 100% rename from static/post/kernel_configs/rhakotis.config rename to content/en/post/kernel_configs/rhakotis.config diff --git a/static/post/kernel_configs/satis.config b/content/en/post/kernel_configs/satis.config similarity index 100% rename from static/post/kernel_configs/satis.config rename to content/en/post/kernel_configs/satis.config diff --git a/content/en/post/rtl8153b-for-4.9.md b/content/en/post/rtl8153b-for-4.9/index.md similarity index 100% rename from content/en/post/rtl8153b-for-4.9.md rename to content/en/post/rtl8153b-for-4.9/index.md diff --git a/static/post/rtl8153b-for-4.9/r8152-for-4.9.patch b/content/en/post/rtl8153b-for-4.9/r8152-for-4.9.patch similarity index 100% rename from static/post/rtl8153b-for-4.9/r8152-for-4.9.patch rename to content/en/post/rtl8153b-for-4.9/r8152-for-4.9.patch diff --git a/static/post/self-hosting/gmail.png b/content/en/post/self-hosting/gmail.png similarity index 100% rename from static/post/self-hosting/gmail.png rename to content/en/post/self-hosting/gmail.png diff --git a/content/en/post/self-hosting.md b/content/en/post/self-hosting/index.md similarity index 99% rename from content/en/post/self-hosting.md rename to content/en/post/self-hosting/index.md index cb0cb39..fac7b49 100644 --- a/content/en/post/self-hosting.md +++ b/content/en/post/self-hosting/index.md @@ -28,7 +28,7 @@ In fact, for many years, one could almost think that for an advertising company, But one day, an advertising engineer had an idea: if we could know what kind of person is searching, we would be able to send them directly to the most appropriate site. A few developments later, here is what the biggest data vacuum cleaner you can imagine was: -![The GMail interface](/post/self-hosting/gmail.png) +![The GMail interface](gmail.png) Contacts, message contents, order forms, newsletters, ... This is how to subtly direct someone to one site rather than another. This is very good when we are in a hurry, but instead of opening us up to the world in general, it locks us into an information bubble. diff --git a/static/post/ssh_keys/aton_ed25519.pub b/content/en/post/ssh_keys/aton_ed25519.pub similarity index 100% rename from static/post/ssh_keys/aton_ed25519.pub rename to content/en/post/ssh_keys/aton_ed25519.pub diff --git a/static/post/ssh_keys/aton_rsa.pub b/content/en/post/ssh_keys/aton_rsa.pub similarity index 100% rename from static/post/ssh_keys/aton_rsa.pub rename to content/en/post/ssh_keys/aton_rsa.pub diff --git a/content/en/post/ssh_keys.md b/content/en/post/ssh_keys/index.md similarity index 100% rename from content/en/post/ssh_keys.md rename to content/en/post/ssh_keys/index.md diff --git a/static/post/ssh_keys/khonsou_ed25519.pub b/content/en/post/ssh_keys/khonsou_ed25519.pub similarity index 100% rename from static/post/ssh_keys/khonsou_ed25519.pub rename to content/en/post/ssh_keys/khonsou_ed25519.pub diff --git a/static/post/ssh_keys/ouaset.pub b/content/en/post/ssh_keys/ouaset.pub similarity index 100% rename from static/post/ssh_keys/ouaset.pub rename to content/en/post/ssh_keys/ouaset.pub diff --git a/static/post/ssh_keys/oupaout.pub b/content/en/post/ssh_keys/oupaout.pub similarity index 100% rename from static/post/ssh_keys/oupaout.pub rename to content/en/post/ssh_keys/oupaout.pub diff --git a/static/post/ssh_keys/rescue.pub b/content/en/post/ssh_keys/rescue.pub similarity index 100% rename from static/post/ssh_keys/rescue.pub rename to content/en/post/ssh_keys/rescue.pub diff --git a/static/post/ssh_keys/seth_ed25519.pub b/content/en/post/ssh_keys/seth_ed25519.pub similarity index 100% rename from static/post/ssh_keys/seth_ed25519.pub rename to content/en/post/ssh_keys/seth_ed25519.pub diff --git a/static/post/ssh_keys/seth_rsa.pub b/content/en/post/ssh_keys/seth_rsa.pub similarity index 100% rename from static/post/ssh_keys/seth_rsa.pub rename to content/en/post/ssh_keys/seth_rsa.pub diff --git a/content/en/post/use-additional-ipv6-blocks-from-isp.md b/content/en/post/use-additional-ipv6-blocks-from-isp/index.md similarity index 97% rename from content/en/post/use-additional-ipv6-blocks-from-isp.md rename to content/en/post/use-additional-ipv6-blocks-from-isp/index.md index ffa6118..b53d94b 100644 --- a/content/en/post/use-additional-ipv6-blocks-from-isp.md +++ b/content/en/post/use-additional-ipv6-blocks-from-isp/index.md @@ -24,7 +24,7 @@ This is possible because the router regularly transmits information about the su For our experiment, let's take the following lab: -![The basic infrastructure that we will use for our experiments](/post/use-additional-ipv6-blocks-from-isp/lab.png) +![The basic infrastructure that we will use for our experiments](lab.png) We have all our equipment connected to the box and a series of virtual machines hosted on one of the network machines. @@ -42,7 +42,7 @@ The main interest of this segmentation would be to avoid that all this little wo We could therefore want to segment our network like this: -![Example of segmentation by splitting the /64 block into two /65 blocks](/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png) +![Example of segmentation by splitting the /64 block into two /65 blocks](lab-segmente.png) We would reserve half of the /64 block for real network equipment and allocate the other half to our virtual machines located on a server/Raspberry Pi. diff --git a/static/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png b/content/en/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png similarity index 100% rename from static/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png rename to content/en/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png diff --git a/static/post/use-additional-ipv6-blocks-from-isp/lab.png b/content/en/post/use-additional-ipv6-blocks-from-isp/lab.png similarity index 100% rename from static/post/use-additional-ipv6-blocks-from-isp/lab.png rename to content/en/post/use-additional-ipv6-blocks-from-isp/lab.png diff --git a/static/post/use-ipv6-in-docker/common-network-with-docker.png b/content/en/post/use-ipv6-in-docker/common-network-with-docker.png similarity index 100% rename from static/post/use-ipv6-in-docker/common-network-with-docker.png rename to content/en/post/use-ipv6-in-docker/common-network-with-docker.png diff --git a/static/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png b/content/en/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png similarity index 100% rename from static/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png rename to content/en/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png diff --git a/static/post/use-ipv6-in-docker/freebox-ipv6-prefix-delegation.png b/content/en/post/use-ipv6-in-docker/freebox-ipv6-prefix-delegation.png similarity index 100% rename from static/post/use-ipv6-in-docker/freebox-ipv6-prefix-delegation.png rename to content/en/post/use-ipv6-in-docker/freebox-ipv6-prefix-delegation.png diff --git a/content/en/post/use-ipv6-in-docker.md b/content/en/post/use-ipv6-in-docker/index.md similarity index 94% rename from content/en/post/use-ipv6-in-docker.md rename to content/en/post/use-ipv6-in-docker/index.md index 0daf055..1341db8 100644 --- a/content/en/post/use-ipv6-in-docker.md +++ b/content/en/post/use-ipv6-in-docker/index.md @@ -15,7 +15,7 @@ In fact, for the same reason we saw in [the introductory article]({{< relref "us The same phenomenon can be observed with IPv4: each container has an IPv4 in a subnet separate from the one in which our host machine is located. -![Illustration of a classic IPv4 home network](/post/use-ipv6-in-docker/common-network-with-docker.png) +![Illustration of a classic IPv4 home network](common-network-with-docker.png) In order for the containers to have access to the Internet under these conditions, in IPv4 NAT is implemented: @@ -72,7 +72,7 @@ On the Freebox, the window for setting additional prefixes is in "Paramètres de It looks like this: -![Freebox IPv6 prefix delegation settings window](/post/use-ipv6-in-docker/freebox-ipv6-refix-delegation.png) +![Freebox IPv6 prefix delegation settings window](freebox-ipv6-refix-delegation.png) Always leave the first field empty, otherwise the box will not offer you IPv6 on the main network. @@ -85,7 +85,7 @@ That's all! The hardest part is over. Now let's see the Docker configuration. We will not use the range to which our machine is connected. We are going to use a whole /64 range, the one for which we have given the local IP of our machine to the box. -![Our prefix delegation correctly set up on the Freebox](/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png) +![Our prefix delegation correctly set up on the Freebox](freebox-ipv6-delegation-filled.png) According to the previous screenshot, our configuration file `/etc/docker/daemon.json` should look like: diff --git a/static/post/user-ns-for-grsecurity/grsec-enable-user-ns.patch b/content/en/post/user-ns-for-grsecurity/grsec-enable-user-ns.patch similarity index 100% rename from static/post/user-ns-for-grsecurity/grsec-enable-user-ns.patch rename to content/en/post/user-ns-for-grsecurity/grsec-enable-user-ns.patch diff --git a/content/en/post/user-ns-for-grsecurity.md b/content/en/post/user-ns-for-grsecurity/index.md similarity index 100% rename from content/en/post/user-ns-for-grsecurity.md rename to content/en/post/user-ns-for-grsecurity/index.md diff --git a/content/en/talks.md b/content/en/talks.md index 2353429..ef55739 100644 --- a/content/en/talks.md +++ b/content/en/talks.md @@ -1,6 +1,9 @@ --- title: "Talks" date: !!timestamp '2017-07-31T00:07:37+02:00' +menu: + main: + weight: 40 --- Here are slides I used as support to my presentations: diff --git a/content/fr/about.md b/content/fr/a-propos.md similarity index 97% rename from content/fr/about.md rename to content/fr/a-propos.md index fb0eb61..d54b615 100644 --- a/content/fr/about.md +++ b/content/fr/a-propos.md @@ -2,8 +2,12 @@ title: "Qui suis-je ?" date: !!timestamp '2017-07-31T00:50:07+02:00' update: !!timestamp '2021-07-24T00:00:00+01:00' +menu: + main: + name: "À propos" + weight: 30 aliases: - - a-propos + - about --- Bonjour ! ici `nemunaire`, alias Pierre-Olivier ; je suis ingénieur (et passionné par [le fonctionnement des choses](https://fr.wikipedia.org/wiki/Wikipédia)), enseignant (et pionnier de la [gamification](https://fr.wikipedia.org/wiki/Ludification) de mes cours), cuisinier (et partisan de [limiter l'empreinte écologique dans nos habitudes alimentaires](https://fr.wikipedia.org/wiki/V%C3%A9g%C3%A9tarisme)) et je lutte aussi contre l'emprise des [GAFAM](https://fr.wikipedia.org/wiki/GAFAM) sur notre temps. D'ailleurs j’adhère de manière générale au [stoïcisme](https://fr.wikipedia.org/wiki/Sto%C3%AFcisme). J'adore la typographie, les challenges, le chocolat (ou la vanille ?? le choix est trop difficile) et tant d'autres choses ! diff --git a/content/fr/talks.md b/content/fr/conferences.md similarity index 94% rename from content/fr/talks.md rename to content/fr/conferences.md index 5ece33f..6f36464 100644 --- a/content/fr/talks.md +++ b/content/fr/conferences.md @@ -1,8 +1,11 @@ --- -title: "Talks" +title: "Conférences" date: !!timestamp '2017-07-31T00:07:37+02:00' +menu: + main: + weight: 40 aliases: - - conferences + - talks --- Voici les supports des conférences que j'ai données : diff --git a/static/post/post-mortem-cryptominer-on-ci-infrastructure/abuse.png b/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/abuse.png similarity index 100% rename from static/post/post-mortem-cryptominer-on-ci-infrastructure/abuse.png rename to content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/abuse.png diff --git a/static/post/post-mortem-cryptominer-on-ci-infrastructure/base64.png b/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/base64.png similarity index 100% rename from static/post/post-mortem-cryptominer-on-ci-infrastructure/base64.png rename to content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/base64.png diff --git a/static/post/post-mortem-cryptominer-on-ci-infrastructure/blocked-users.png b/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/blocked-users.png similarity index 100% rename from static/post/post-mortem-cryptominer-on-ci-infrastructure/blocked-users.png rename to content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/blocked-users.png diff --git a/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure.md b/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/index.md similarity index 100% rename from content/fr/post/post-mortem-cryptominer-on-CI-infrastructure.md rename to content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/index.md diff --git a/static/post/post-mortem-cryptominer-on-ci-infrastructure/repository.png b/content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/repository.png similarity index 100% rename from static/post/post-mortem-cryptominer-on-ci-infrastructure/repository.png rename to content/fr/post/post-mortem-cryptominer-on-CI-infrastructure/repository.png diff --git a/content/fr/post/self-hosting.md b/content/fr/post/self-hosting/index.md similarity index 99% rename from content/fr/post/self-hosting.md rename to content/fr/post/self-hosting/index.md index e22cdc2..31c5d61 100644 --- a/content/fr/post/self-hosting.md +++ b/content/fr/post/self-hosting/index.md @@ -28,7 +28,7 @@ D'ailleurs, pendant de longues années, on aurait presque pu penser que pour une Mais un jour, un ingénieur publicitaire a eu une idée : si on pouvait savoir quel genre d'individu fait une recherche, on serait capable de l'envoyer directement vers le site le plus approprié. Quelques développements plus tard, voici ce que fût le plus grand aspirateur de données que l'on puisse imaginer : -![L'interface de GMail](/post/self-hosting/gmail.png) +![L'interface de GMail](gmail.png) Contacts, contenus des messages, bons de commandes, newsletters, ... Voilà comment orienter subtilement quelqu'un vers un site plutôt qu'un autre. C'est très bien lorsqu'on est pressé, mais au lieu de nous ouvrir sur le monde en général, cela nous enferme au contraire dans une bulle informative. diff --git a/content/fr/post/use-additional-ipv6-blocks-from-isp.md b/content/fr/post/use-additional-ipv6-blocks-from-isp/index.md similarity index 97% rename from content/fr/post/use-additional-ipv6-blocks-from-isp.md rename to content/fr/post/use-additional-ipv6-blocks-from-isp/index.md index 3081245..2ab2210 100644 --- a/content/fr/post/use-additional-ipv6-blocks-from-isp.md +++ b/content/fr/post/use-additional-ipv6-blocks-from-isp/index.md @@ -24,7 +24,7 @@ Cela est possible car le routeur émet régulièrement les informations du sous- Pour notre expérience, prenons le lab suivant : -![L´infrastructure de base qui va nous servir à faire nos expérimentations](/post/use-additional-ipv6-blocks-from-isp/lab.png) +![L´infrastructure de base qui va nous servir à faire nos expérimentations](lab.png) Nous avons tous nos équipements reliés à la box et une série de machines virtuelles hébergées sur l'une des machines du réseau. @@ -42,7 +42,7 @@ L'intérêt principal de cette segmentation serait d'éviter que tout ce petit m On pourrait donc vouloir segmenter son réseau comme cela : -![Exemple de segmentation par le partage du bloc /64 en deux blocs /65](/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png) +![Exemple de segmentation par le partage du bloc /64 en deux blocs /65](lab-segmente.png) On réserverait la moitié du bloc /64 aux équipements réels du réseau et on attribuerait l'autre moitié à nos machines virtuelles situées sur un serveur/Raspberry Pi. diff --git a/content/fr/post/use-ipv6-in-docker.md b/content/fr/post/use-ipv6-in-docker/index.md similarity index 96% rename from content/fr/post/use-ipv6-in-docker.md rename to content/fr/post/use-ipv6-in-docker/index.md index 70fd6cc..3e10eb8 100644 --- a/content/fr/post/use-ipv6-in-docker.md +++ b/content/fr/post/use-ipv6-in-docker/index.md @@ -15,7 +15,7 @@ En fait, pour la même raison que nous avons vu dans [l'article introductif]({{< On observe d'ailleurs le même phénomène avec l'IPv4 : chaque conteneur dispose d'une IPv4 dans un sous-réseau distinct de celui dans lequel se trouve notre machine hôte. -![Illustration d´un réseau domestique IPv4 classique](/post/use-ipv6-in-docker/common-network-with-docker.png) +![Illustration d´un réseau domestique IPv4 classique](common-network-with-docker.png) Pour que les conteneurs aient accès à Internet dans ces conditions, en IPv4 du NAT est mis en œuvre : @@ -72,7 +72,7 @@ Sur les Freebox, la fenêtre de paramétrage des préfixes supplémentaires se t Cela ressemble à ça : -![Fenêtre de paramétrage de la délégation de préfixe IPv6 de la Freebox](/post/use-ipv6-in-docker/freebox-ipv6-prefix-delegation.png) +![Fenêtre de paramétrage de la délégation de préfixe IPv6 de la Freebox](freebox-ipv6-prefix-delegation.png) Laissez toujours le 1ᵉʳ champ vide, sans quoi la box ne vous proposera plus d'IPv6 sur le réseau principal. @@ -85,7 +85,7 @@ C'est tout ! Le plus dur est passé. Voyons maintenant la configuration de Docke Nous n'allons pas utiliser la plage à laquelle notre machine est connectée. Nous allons utiliser toute une plage /64, celle pour laquelle on a donné l'IP locale de notre machine à la box. -![Notre délégation de préfixe correctement paramétrée sur la Freebox](/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png) +![Notre délégation de préfixe correctement paramétrée sur la Freebox](freebox-ipv6-delegation-filled.png) Selon la capture d'écran précédente, notre fichier de configuration `/etc/docker/daemon.json` devrait ressembler à :