#security

GitHub now supports SSH commit signing, which is quite nice. I have been trying to use less and less GPG. I just tried pushing a commit signed this way and it works quite nicely.

GitHub now supports SSH commit signing, which is quite nice. I have been trying to use less and less GPG. I just tried pushing a commit signed this way and it works quite nicely.

Today I noticed my VPS did not have any firewall installed. Since I use Alpine, I decided to try out awall, which led to 15 minutes of down time for this website and all the remaining services. Besides, it seems that Docker messes with the IP tables by default, which can be troublesome with firewalls. In the end, I ended up using Hetzner’s own firewall which is completely decoupled from the OS and easier to manage.

Today I noticed my VPS did not have any firewall installed. Since I use Alpine, I decided to try out awall, which led to 15 minutes of down time for this website and all the remaining services. Besides, it seems that Docker messes with the IP tables by default, which can be troublesome with firewall…

I finally stopped using GPG keys for SSH authentication. Now I purely use SSH keys protected by 2FA via security keys. Now I have to get used to “touching” for authentication!

It also looks like Git allows to use SSH keys for signing. Unfortunately GitHub doesn’t support such signatures yet. Once they do, I may change to that method.

I finally stopped using GPG keys for SSH authentication. Now I purely use SSH keys protected by 2FA via security keys. Now I have to get used to "touching" for authentication! It also looks like Git allows to use SSH keys for signing. Unfortunately GitHub doesn't support such signatures yet. Once t…

In my last post, I mentioned that I was “investigating the possibility to use Tailscale to simply block the access from the “outside world” and make it more secure”. Well, it is now implemented and it works. Basically, my blog system can listen on two different ports: the regular one where you’re navigating, and the one inside a Tailscale network.

If I specify exclusiveDashboard: true on my Tailscale section of the configuration, the dashboard will only be added to the Tailscale router. This way, the dashboard won’t be available at hacdias.com, but only inside the Tailscale network. I’ve tried it and it works. However, it is not how it is not enabled on the live version yet!

I also mentioned that I was trying to “inject” and admin bar while logged in. I can say that it is working via some response writer wrapping magic. I have a few more plans to make Eagle more self-contained, but we’re not there yet!

Have a fantastic day!

In my last post, I mentioned that I was "investigating the possibility to use Tailscale to simply block the access from the “outside world” and make it more secure". Well, it is now implemented and it works. Basically, my blog system can listen on two different ports: the regular one where you're na…

jlelse’s Blog 20 Oct 2021 18:46

My home and code server now has 2 TB of SSD storage and 16 GB of RAM. While I’ll be using the storage for backups, etc., I’m not quite sure what I can use the 16 GB of RAM for yet. What else can I run besides Home Assistant, AdGuard Home, Drone and Tailscale? I still have my VPS running my websites,…

Weirdly enough, the name Tailscale caught my eye and I decided to investigate what it is. I checked their website and it seems that they use Wireguard to do the kind of configuration I explained some time ago. I’m curious: besides the easyness of use, what other advantages do you see on using Tailscale over a manually configured Wireguard network?

Replied to a post on jlelse.blog

A few days ago I saw a blog post by GitHub announcing their support for security keys in SSH operations. After a bit of search, I discovered that OpenSSL 8.2, released last year, lets us use our FIDO2 devices (such as Yubikeys) to “unlock” our SSH private keys. This way, we don’t need the cumbersome GPG <-> SSH relation.

I tried it, and it was nice. I don’t know if I’m going to start using it right away because not every place uses OpenSSL 8.2+ yet, but soon, very soon.

Some links:

A few days ago I saw a blog post by GitHub announcing their support for security keys in SSH operations. After a bit of search, I discovered that OpenSSL 8.2, released last year, lets us use our FIDO2 devices (such as Yubikeys) to "unlock" our SSH private keys. This way, we don't need the cumbersome…

Jan-Lukas Else 22 Jan 2020 10:28

I don’t show webmention content at all. 😅 Instead I just show a link to the “interaction”. That removes a lot of complexity with parsing, storing etc. but probably isn’t as intuitive: it requires opening the “interactions” section below the post and visiting the link.

I enjoy showing the webmention and the context (reply to what? repost of what? like of what?) because, as you know, the content on the Internet is ephemeral and if I don’t store it, I don’t have assurance that it will remain available. And that’s the main reason why I show the webmentions.

In any case, it’s not the webmentions that worry me, but the post contexts that I show on replies, likes and reposts… Need to decide on that: either remove the pictures, or store them.

Replied to a post on jlelse.blog