https://blog.kumiko.se/ Recent content on Kumiko: Blog Hugo -- gohugo.io en-us Tue, 20 Apr 2021 11:21:00 +0200 https://blog.kumiko.se/blog/2021/04/check-point-cli-administration-cheat-sheet.html Tue, 20 Apr 2021 11:21:00 +0200 https://blog.kumiko.se/blog/2021/04/check-point-cli-administration-cheat-sheet.html Activate Check Point CLI shell from expert mode Run clish from expert mode. This only works if you logged into expert mode directly via SSH. It doesn’t work if you first logged into clish and then switched to expert mode. Works: expert -> clish Does not work: clish -> expert -> clish In the latter case, just exit from expert mode to get back to the clish environment. Schedule a recurring task via cron Given that Check Point Gaia is running Linux, it’s running a normal cron scheduler like any other Linux distribution. https://blog.kumiko.se/blog/2021/03/create-a-certificate-bundle.html Sat, 20 Mar 2021 19:56:00 +0100 https://blog.kumiko.se/blog/2021/03/create-a-certificate-bundle.html This post mainly serves as a reminder for myself… When using certificates with web servers, like nginx or apache, it’s recommended to publish the entire certificate chain, since else tools like Google Chrome or curl will complain about invalid certificates, even if you bought or used Let’s Encrypt to get your certificate. To remediate this, you need to create a bundle which consists of your certificate, the certificate used to sign your certificate (Usually called the intermediate CA) and the certificate used to sign the intermediate certificate (Usually called the root CA), which in turn should already be present on your machine if you’re using a previously trusted vendor, like Let’s Encrypt. https://blog.kumiko.se/blog/2021/03/gitlab-asking-for-password-on-centos-8-or-stream.html Fri, 19 Mar 2021 12:22:16 +0100 https://blog.kumiko.se/blog/2021/03/gitlab-asking-for-password-on-centos-8-or-stream.html If you’re like me and have recently setup a Gitlab server running on CentOS 8 or CentOS Stream for your Git-needs, then you might have ran into the issue were Gitlab is asking you for the Git users password when pushing your code for the first time. This could be caused by SELinux being incorrectly configured for the SSH authorized keys file created by Gitlab. To test this, first disable SELinux by running sudo setenforce 0.