Solene'%

# Introduction For the last seven months, I spent a good part of my (small amount of) free time rebuilding my self-hosting infrastructure at home. I wanted something secure, fully automated, that updates itself and that I can rebuild from scratch if something goes wrong. Most of the ideas come from my work on infrastructures following SecNumCloud (a French security standard for cloud providers) and, to a lesser extent, ISO 27001, I wanted to see how far I could apply the same principles at…

# Introduction I started playing with IPFS because I wanted a different way of publishing data over the Internet. My first experiments with IPFS and a private swarm showed that the technology is useful, but the user experience is bad. It is easy to get an IPFS node running, but hard to make it useful in real world. The issue was not only that the protocol itself is complicated: IPFS is not a file server, it is a content-addressed system where files are identified by a CID, which is a hash of…

# Introduction In this blog post, you will learn how to make a private IPFS network that will allow private peers to exchange data between each other. This is in opposition to the default setup in which you use the default configuration connecting to the whole IPFS network. The incentive to have your own network is mostly speed, because this does not have any extra access control, any peer can potentially access to any content you have in your IPFS network. If you do not know about IPFS, I…

# Introduction I have a lot of photos that I have been carrying since a long time, this is certainly my oldest files that I was able to not lost over 20 years. It has been stored as a hierarchy since then, and it had very poor metadata information, and poor ability to be browsed. It was time to improve on this. My goal was to fix metadata on my pictures, but also put geolocation metadata on them because I really enjoy see a map with thumbnails of memories (just make sure to trim this met...

# Introduction I really like containers, but they are something that is currently very bad from a security point of view: distribution We download container images from container registries, whether it is docker.io, quay.io or ghcr.io, but the upstream project do not sign them, so we can not verify a CI pipeline or the container registry did not mess with the image. There are actually a few upstream actors signing their images: Fedora, Red Hat and universial-blue based distros (Bluefin, A...